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 53CCEC76196 for ; Sat, 1 Apr 2023 06:34:14 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id EE94385FE0; Sat, 1 Apr 2023 08:33:11 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=chromium.org header.i=@chromium.org header.b="Up3F6rf5"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 9889B85FF9; Sat, 1 Apr 2023 08:32:25 +0200 (CEST) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 3950A86006 for ; Sat, 1 Apr 2023 08:32:20 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=sjg@google.com Received: by mail-ed1-x52a.google.com with SMTP id eh3so98052721edb.11 for ; Fri, 31 Mar 2023 23:32:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1680330740; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uK12vWHOjjmp+UgCt/Eve8kuzn7uXypXVL3c+gwA33s=; b=Up3F6rf5jdpovaUFQBYvMtSIJInHCQTY8e+IKC8NeQIx0UwoixU+FIJVoabo8qd4nO c8Wh4QtzzUmjCYKN8Eg0NAnRytGjv8YonFDWJftlBYgjA/rZIJnYwBj1BUlxsA1mw7mD pBF3DuiBawP2qIFDEN5SS+OC1sQmWSPFiosmQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680330740; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uK12vWHOjjmp+UgCt/Eve8kuzn7uXypXVL3c+gwA33s=; b=XBSa2qEhR8NiPtWosRvYRY3eUZFvigkZZ6IVw4UZB+v/RjLYCVikLbyZrgUyh3nNbW lP/bUCnlcp2Ne8BSSpxtkQcNx62nbr5GEdLIbv+ZbGS1whrK3BRcnQi9W5EkR4iecFJF UijfPiiIJ/OH/SSsatrgBfGYBVNfzSduBhYPz9oBlaSHtKwGFzpiW9Vk2SoOADny6gXu FjlQg6Mh8e4C4MrBzzoEvMxFH0HAMXySNN7jbXorPM22RKze9Iv40/lddsI49S9+61u9 twcchArhiKmIo4fp6pFPdFjF9xr00VlpRcAdcm6R4xvk9k+cc/YYohFO0rsSASXN2jtn CsHg== X-Gm-Message-State: AAQBX9cS7M90zk4/D62+tOaLdkkr8lphEQoy1f6IjNKXy0JBFZ0/25IR Dqfh6fxDRbMZfGpQB0+9tMF337Mcx7k+O6XUneUSQc9P+taAOE8nBhQ= X-Google-Smtp-Source: AKy350YRWAMNmcq68rgl7Y0c22QuIrHKDa9PbUX6OWyzhBymnVwGg/4WIZT36MG6ew1MlMuOB+bSflxzHk+z2iWRC0M= X-Received: by 2002:a17:907:c284:b0:948:1d55:dec2 with SMTP id tk4-20020a170907c28400b009481d55dec2mr178722ejc.14.1680330739635; Fri, 31 Mar 2023 23:32:19 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Simon Glass Date: Sat, 1 Apr 2023 19:32:04 +1300 Message-ID: Subject: Re: Newer U-Boot version throwing "Bootstage space exhasuted" with FIT image To: deffo@gmx.de Cc: u-boot@lists.denx.de Content-Type: text/plain; charset="UTF-8" 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 Hi, On Sat, 1 Apr 2023 at 02:57, wrote: > > Hi, > > I changed from v2020.10 to v2022.10 and suddenly I get a bunch of "Bootstage space exhasuted" messages during bootm. > > reloc pc : [] is memcpy() > > It evens triggers a reset. Older version works just fine: > > Sign value: unavailable > Timestamp: unavailable > Verifying Hash Integrity ... sha256+ OK > Bootstage space exhasuted > Bootstage space exhasuted > Bootstage space exhasuted > Bootstage space exhasuted > Loading fdt from 0xc272de94 to 0xc4000000 > Bootstage space exhasuted > Booting using the fdt blob at 0xc4000000 > Loading Kernel Image > kernel loaded at 0xc0008000, end = 0xc0735c80 > Bootstage space exhasuted > Bootstage space exhasuted > Loading Ramdisk to cfd23000, end cffff105 ... OK > Loading Device Tree to cfd10000, end cfd22375 ... OK > Bootstage space exhasuted > Bootstage space exhasuted > > Starting kernel ... > > data abort > pc : [] lr : [<00000000>] > reloc pc : [] lr : [] > sp : fbf2786c ip : 00000000 fp : 00000001 > r10: c20000d8 r9 : fbf37eb0 r8 : 00000000 > r7 : 00000000 r6 : 00000000 r5 : e28ff010 r4 : 00000000 > r3 : 00000000 r2 : 00000a10 r1 : fdfabb14 r0 : 2ffc0020 > Flags: nzCv IRQs off FIQs off Mode SVC_32 (T) > Code: f891 f03c f891 f05c (f891) f07c > Resetting CPU ... > > resetting ... Do you know which board it is? It would help to produce a full console trace. Regards, Simon