[PATCH 3/3] imx8qm_mek: Increase CONFIG_SYS_BOOTM_LEN to 64MB
Marcel Ziswiler
marcel.ziswiler at toradex.com
Mon Aug 30 18:34:47 CEST 2021
On Mon, 2021-08-30 at 17:10 +0200, Marek Vasut wrote:
> On 8/30/21 5:05 PM, Marcel Ziswiler wrote:
> > On Mon, 2021-08-30 at 14:18 +0200, Marek Vasut wrote:
> > > On 8/30/21 1:11 PM, Oleksandr Suvorov wrote:
> > > > On Sun, Aug 29, 2021 at 10:55 PM Marek Vasut <marex at denx.de> wrote:
> > > > >
> > > > > On 8/29/21 9:39 PM, Oleksandr Suvorov wrote:
> > > > > > The BSP platform LmP supports the board NXP iMX8QM MEK. The
> > > > > > kernel size in LmP exceeds 32Mb. Increase the maximum size
> > > > > > of an uncompressed kernel to fix the following error:
> > > > > > Uncompressing Kernel Image
> > > > > > Error: inflate() returned -5
> > > > > > Image too large: increase CONFIG_SYS_BOOTM_LEN
> > > > > > Must RESET board to recover
> > > > > >
> > > > >
> > > > > Maybe we should increase the default for arm64 instead ? 8 MiB is too small.
> > > >
> > > > I completely agree if NXP doesn't have objections.
> > > > @Peng Fan Do you mind?
> > >
> > > Increase it for all of arm64 , or all of U-Boot even. This has nothing
> > > to do with NXP.
> >
> > In general, I agree. However, in practice this can have devastating effects on stuff as discussed here:
> >
> > https://marc.info/?l=u-boot&m=162999598824381
>
> I suspect the correct solution for that is to use bootm_size and let
> U-Boot figure out where to place the kernel / DT / etc.
Sure, but how would that work with FIT images e.g. containing kernel binary, device tree(s) and an initrd?
More information about the U-Boot
mailing list