Re: Cubox-i with Debian Stock Kernel

[Rainer Dorsch <ml@bokomoko.de>]

On Friday 30 May 2014 09:53:09 Vagrant Cascadian wrote:
> On Fri, May 30, 2014 at 05:33:14PM +0200, Rainer Dorsch wrote:
> > I did not have Debian's u-boot. I tested it now, but does not work at all
> > for me.
> > 
> > 
> > I dd ed SPL and u-boot.img from /usr/lib/u-boot/mx6_cubox-i/.
> > 
> > But that did not change anything for bootz, still it does not detect the
> > ramdisk
> 
> ...
> 
> > CuBox-i U-Boot > ext4load mmc 0:2 0x12800000 initrd.img
> > 10909053 bytes read in 722 ms (14.4 MiB/s)
> > CuBox-i U-Boot > bootz 0x10800000 0x12800000 0x18000000
> > Kernel image @ 0x10800000 [ 0x000000 - 0x2b8978 ]
> > Wrong Ramdisk Image Format
> > Ramdisk image is corrupt or invalid
> > CuBox-i U-Boot >
> 
> You need to specify the ramdisk size when using bootz. the following works
> for me with u-boot 2014.04-2 from Debian Sid:
> 
> CuBox-i U-Boot > printenv loadaddr kernel ramdiskaddr initrd fdt_addr
> fdt_file loadkernel loadinitrd loadfdt bootargs bootcmd loadaddr=0x10800000
> kernel=vmlinuz
> ramdiskaddr=0x11800000
> initrd=initrd.img
> fdt_addr=0x18000000
> fdt_file=imx6q-cubox-i.dtb
> loadkernel=load mmc 0:2 ${loadaddr} ${kernel}
> loadinitrd=load mmc 0:2 ${ramdiskaddr} ${initrd} ; setenv initrdsize
> ${filesize} loadfdt=load mmc 0:2 ${fdt_addr} ${fdt_file}
> bootargs=console=ttymxc0,115200 root=/dev/mmcblk0p2
> bootcmd=run loadkernel ; run loadinitrd ; run loadfdt ; bootz ${loadaddr}
> ${ramdiskaddr}:${initrdsize} ${fdt_addr} CuBox-i U-Boot > run bootcmd
> 

I read that cubox-i checks only the first partition for a boot.scr script.

I just realized that you have your root partition in the second partition. Do 
you need to type "run bootcmd" everytime you boot or did you find a workaround 
for that restriction?

Rainer






-- 
Rainer Dorsch
http://bokomoko.de/