u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Tom Rini <trini@konsulko.com>,
	Leo Yu-Chi Liang <ycliang@andestech.com>,
	 Rick Chen <rick@andestech.com>,
	Alexandre Ghiti <alexandre.ghiti@canonical.com>,
	 Pragnesh Patel <pragnesh.patel@sifive.com>,
	 Dimitri John Ledkov <dimitri.ledkov@canonical.com>,
	Zong Li <zong.li@sifive.com>,  Green Wan <green.wan@sifive.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/1] board: sifive: unmatched: enlarge CONFIG_SYS_SPL_MALLOC_SIZE
Date: Fri, 1 Oct 2021 23:35:45 +0800	[thread overview]
Message-ID: <CAEUhbmVdJD781V-gNHt1czEoDCm-=3dDNbM5D1-B5YqD9HfShA@mail.gmail.com> (raw)
In-Reply-To: <20211001113745.52797-1-heinrich.schuchardt@canonical.com>

Hi Heinrich,

On Fri, Oct 1, 2021 at 7:37 PM Heinrich Schuchardt
<heinrich.schuchardt@canonical.com> wrote:
>
> Avoid an error like
>
>     Could not get FIT buffer of 1725952 bytes
>             check CONFIG_SYS_SPL_MALLOC_SIZE
>     No device tree specified in SPL image
>     ### ERROR ### Please RESET the board ###
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
>  include/configs/sifive-unmatched.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/configs/sifive-unmatched.h b/include/configs/sifive-unmatched.h
> index f8ad2cce1f..8d3deabdd3 100644
> --- a/include/configs/sifive-unmatched.h
> +++ b/include/configs/sifive-unmatched.h
> @@ -18,7 +18,7 @@
>  #define CONFIG_SPL_BSS_MAX_SIZE                0x00100000
>  #define CONFIG_SYS_SPL_MALLOC_START    (CONFIG_SPL_BSS_START_ADDR + \
>                                          CONFIG_SPL_BSS_MAX_SIZE)
> -#define CONFIG_SYS_SPL_MALLOC_SIZE     0x00100000
> +#define CONFIG_SYS_SPL_MALLOC_SIZE     0x00200000
>
>  #define CONFIG_SPL_STACK       (0x08000000 + 0x001D0000 - \
>                                  GENERATED_GBL_DATA_SIZE)

What caused this?

Last time this was seen on Ax25-AE350, CONFIG_SPL_SYS_MALLOC_F_LEN was
increased, instead of CONFIG_SYS_SPL_MALLOC_SIZE which the error
messages point to

https://lists.denx.de/pipermail/u-boot/2021-May/449447.html

Regards,
Bin

  reply	other threads:[~2021-10-01 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 11:37 [PATCH 1/1] board: sifive: unmatched: enlarge CONFIG_SYS_SPL_MALLOC_SIZE Heinrich Schuchardt
2021-10-01 15:35 ` Bin Meng [this message]
2021-10-19  8:32   ` Alexandre Ghiti
2021-10-19  8:54     ` Bin Meng
2021-10-19  9:21       ` Alexandre Ghiti
     [not found]       ` <HK0PR03MB2994F5C472842C9C4B0B62BBC1839@HK0PR03MB2994.apcprd03.prod.outlook.com>
2021-10-25  1:49         ` Rick Chen
2021-10-25  1:58           ` Bin Meng
2021-10-25  2:24             ` Rick Chen
2021-11-01  8:52               ` Bin Meng
2021-11-04  2:38                 ` Rick Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEUhbmVdJD781V-gNHt1czEoDCm-=3dDNbM5D1-B5YqD9HfShA@mail.gmail.com' \
    --to=bmeng.cn@gmail.com \
    --cc=alexandre.ghiti@canonical.com \
    --cc=dimitri.ledkov@canonical.com \
    --cc=green.wan@sifive.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=pragnesh.patel@sifive.com \
    --cc=rick@andestech.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=ycliang@andestech.com \
    --cc=zong.li@sifive.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).