On Thu, May 26, 2016 at 10:40:29AM -0600, Aaron Bieber wrote:
> 
> 
> On Mon, May 23, 2016, at 07:41 PM, Jonathan Gray wrote:
> > On Mon, May 23, 2016 at 01:58:44PM -0600, Aaron Bieber wrote:
> > > Simply flashing the miniroot image onto an SD card and booting will
> > > result in:
> > > 
> > > reading uEnv.txt
> > > 162 bytes read in 3 ms (52.7 KiB/s)
> > > Importing environment from mmc0 ...
> > > Running uenvcmd ...
> > > reading bsdrd.umg
> > > 10883512 bytes read in 507 ms (20.5 MiB/s)
> > > ## Booting kernel from Legacy Image at 82800000 ...
> > >    Image Name:   boot
> > >    Image Type:   ARM Linux Kernel Image (uncompressed)
> > >    Data Size:    10883448 Bytes = 10.4 MiB
> > >    Load Address: 80300000
> > >    Entry Point:  80300000
> > >    Verifying Checksum ... OK
> > >    Loading Kernel Image ... Image too large: increase
> > >    CONFIG_SYS_BOOTM_LEN
> > > Must RESET board to recover
> > > resetting ...
> > > 
> > > U-Boot SPL 2015.10 (Feb 01 2016 - 13:59:48)
> > > OMAP4460 ES1.1
> > 
> > The miniroots are built with u-boot 2016.05 why do you have
> > this version?  There is no uEnv.txt only a boot.scr
> 
> I built a version of u-boot with CONFIG_SYS_BOOTM_LEN bumped, to get
> past this initial error.
> 
> > 
> > Can you send the output of printenv and try
> > 
> > setenv loadaddr 0x82800000 ;
> > run findfdt ;
> > load mmc ${mmcdev}:1 ${loadaddr} bsd.umg ;
> > load mmc ${mmcdev}:1 ${fdt_addr_r} ${fdtfile} ;
> > bootm ${loadaddr} - ${fdt_addr_r} ;
> > 
> 
> Net:   No ethernet found.
> Hit any key to stop autoboot:  0 
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> reading boot.scr
> 213 bytes read in 3 ms (69.3 KiB/s)
> Running bootscript from mmc0 ...
> ## Executing script at 82000000
> reading bsd.umg
> 10883556 bytes read in 480 ms (21.6 MiB/s)
> reading omap4-panda-es.dtb
> 57353 bytes read in 6 ms (9.1 MiB/s)
> ## Booting kernel from Legacy Image at 82000000 ...
>    Image Name:   boot
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    10883492 Bytes = 10.4 MiB
>    Load Address: 80300000
>    Entry Point:  80300000
>    Verifying Checksum ... OK
> ## Flattened Device Tree blob at 88000000
>    Booting using the fdt blob at 0x88000000
>    Loading Kernel Image ... Image too large: increase
>    CONFIG_SYS_BOOTM_LEN
> Must RESET board to recover
> resetting ...
> 
> U-Boot SPL 2016.05 (May 17 2016 - 17:10:59)
> OMAP4460 ES1.1
> Trying to boot from MMC1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
> 
> 
> U-Boot 2016.05 (May 17 2016 - 17:10:59 +1000)
> 
> CPU  : OMAP4460 ES1.1
> Board: OMAP4 Panda
> I2C:   ready
> DRAM:  1 GiB
> MMC:   OMAP SD/MMC: 0
> reading uboot.env
> 
> ** Unable to read "uboot.env" from mmc0:1 **
> Using default environment
> 
> Net:   No ethernet found.
> Hit any key to stop autoboot:  0 
> => setenv loadaddr 0x82800000 ;
> => run findfdt ;
> => load mmc ${mmcdev}:1 ${loadaddr} bsd.umg ;
> reading bsd.umg
> 10883556 bytes read in 480 ms (21.6 MiB/s)
> => load mmc ${mmcdev}:1 ${fdt_addr_r} ${fdtfile} ;
> reading omap4-panda-es.dtb
> 57353 bytes read in 7 ms (7.8 MiB/s)
> => bootm ${loadaddr} - ${fdt_addr_r} ;
> ## Booting kernel from Legacy Image at 82800000 ...
>    Image Name:   boot
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    10883492 Bytes = 10.4 MiB
>    Load Address: 80300000
>    Entry Point:  80300000
>    Verifying Checksum ... OK
> ## Flattened Device Tree blob at 88000000
>    Booting using the fdt blob at 0x88000000
>    Loading Kernel Image ... Image too large: increase
>    CONFIG_SYS_BOOTM_LEN
> Must RESET board to recover
> resetting ...

The latest snapshot has the miniroots switched to use efiboot as
well, which at only 64KB is quite a bit smaller than a kernel image.

Reply via email to