From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C1EE2E77180 for ; Mon, 16 Dec 2024 19:30:02 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id F3A5A800D7; Mon, 16 Dec 2024 20:30:00 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=dolcini.it Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=dolcini.it header.i=@dolcini.it header.b="HmR2FP9x"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id AC59C80104; Mon, 16 Dec 2024 20:29:59 +0100 (CET) Received: from mail11.truemail.it (mail11.truemail.it [217.194.8.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id B7F00800D2 for ; Mon, 16 Dec 2024 20:29:55 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=dolcini.it Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=francesco@dolcini.it Received: from gaggiata.pivistrello.it (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id 42E98224F5; Mon, 16 Dec 2024 20:29:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolcini.it; s=default; t=1734377395; bh=RhsXdEFL6X45oRaPf1P2zjxMraoFhOMvQrP4b3iqBFA=; h=Received:From:To:Subject; b=HmR2FP9xvfqOgb59saNbWn4yC60CrrLZB2lwsGTI0AE6ZghjfUPdsogVOgUBxIc9L DGc+Fuxt90ol1wCWkYvlFL2g6Z13THXJuWGDuYeoRdbsz5rSLL+CAFVDRcBveP83FD 4qeLMVropX6cuV2AlvPyYHnd92mloZdUfrPwic/njwyyMFgoqCb14CWvkMZ+HlgJ62 zNbcKPinxCbaLCcu1kbaCsm9Gf0iODFJBjwkHEXZ5zhGspnnN7I28IDWUYAlZP38bi 7t0eFXVU4EFloGtHA5/3EGj54Gvd/Y1pQxzI412f+RVSXaCag9oYCA2OkEhrVJ99y5 +Jr/DOGPIS5SQ== Received: by gaggiata.pivistrello.it (Postfix, from userid 1000) id F3EFB7FF38; Mon, 16 Dec 2024 20:29:54 +0100 (CET) Date: Mon, 16 Dec 2024 20:29:54 +0100 From: Francesco Dolcini To: Sughosh Ganu Cc: Francesco Dolcini , =?iso-8859-1?Q?Jo=E3o_Paulo_Gon=E7alves?= , Ilias Apalodimas , Tom Rini , Francesco Dolcini , =?iso-8859-1?Q?Jo=E3o_Paulo_Gon=E7alves?= , u-boot@lists.denx.de Subject: Re: [REGRESSION] Out of memory error: unable to boot on imx8mp/imx8mm Message-ID: References: <20241216114231.qpfwug3zfqkxn3d5@joaog-nb.corp.toradex.com> <20241216142842.p5j4otcinwpszt5l@joaog-nb.corp.toradex.com> <20241216190255.GA55577@francesco-nb> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean On Tue, Dec 17, 2024 at 12:37:38AM +0530, Sughosh Ganu wrote: > On Tue, 17 Dec 2024 at 00:33, Francesco Dolcini wrote: > > > > Hello, > > > > On Mon, Dec 16, 2024 at 11:28:42AM -0300, João Paulo Gonçalves wrote: > > > Hi Sughosh, > > > > > > > Can you show the output of bdinfo. And also print the value of ram_top > > > > while booting the board. > > > > > > > > > > Below are ram_top and bdinfo: > > > > We briefly discussed this off list, what is likely happen is that our > > heap is after 0xFFFFFFFF, or said in a simpler way in the 64-bit address > > space, while ram top is at the 4GB boundary. > > > > The solution seems to either move the heap down or move ram top up. > > I am not sure I understand. Isn't the heap memory part of the U-Boot > image, meaning it will always be below the ram_top? How do you have > this configuration where the heap is above ram_top? Can you point me > to the code where the heap is getting set above ram_top. I just guessed this, I might be plain wrong. I assume some malloc is failing, maybe Joao can confirm. Francesco