Re: flash-kernel and dtb

[Rainer Dorsch <ml@bokomoko.de>]

Hi Vagrant,

On Sunday 15 June 2014 00:23:07 Vagrant Cascadian wrote:
> On Sun, Jun 15, 2014 at 08:36:33AM +0200, Rainer Dorsch wrote:
> > On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
> > > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > I use your original boot.scr with an adapted bootargs:
> ...
> 
> > Variables set as you did, but the kernel is still not booting
> > 
> > CuBox-i U-Boot > printenv loadaddr fdt_addr ramdiskaddr
> > loadaddr=0x10800000
> 
> ...
> 
> > CuBox-i U-Boot > load mmc 0:2 0x19000000 /boot/boot.scr
> > 702 bytes read in 95 ms (6.8 KiB/s)
> > CuBox-i U-Boot > source 0x19000000
> 
> My hunch is loading your bootscript to an alternate address is somehow
> causing an issue...
> 
> instead of specifying a different address to load the script, try:
> 
>   load mmc 0:2 ${loadaddr} /boot/boot.scr
>   source ${loadaddr}

Hmm....is loadaddr a special variable for u-boot?

If not, would you not overwrite the script file with the zImage?

> 
> > Just for reference my entire environment
> > 
> > CuBox-i U-Boot > printenv
> 
> ...
> 
> > bootcmd=run loadkernel ; run loadramdisk ; bootm ${loadaddr}
> > ${ramdiskaddr}
> 
> Looks like you're using a modifed environment, or a different u-boot build:
> 
> CuBox-i U-Boot > env default -a
> ## Resetting to default environment
> CuBox-i U-Boot > printenv bootcmd bootscript loadbootscript
> bootcmd=mmc dev ${mmcdev}; if mmc rescan; then for prefix in
> ${boot_prefixes}; do setenv file_prefix ${prefix}; if run loadbootscript;
> then run bootscript; else run autodetectfdt; if run loadbootenv; then run
> importbootenv; fi; if test ${bootfile} = auto; then setenv origbootfile
> auto; setenv bootfile zImage; if run loadbootfile; then run loadramdisk;
> run mmcboot; else setenv bootfile uImage; fi; fi; if run loadbootfile; then
> run loadramdisk; run mmcboot; else setenv bootfile ${origbootfile}; fi; fi;
> done; fi; run netboot; bootscript=echo Running bootscript from mmc ...;
> source;
> loadbootscript=load mmc ${mmcdev}:${mmcpart} ${loadaddr}
> ${file_prefix}${script};
> 

Most likely, there is something wrong with my u-boot installation. 

Is there some documentation on how to get the Debian u-boot properly installed 
on Cubox-i (or other devices)?

What I did is, I started with

http://gwolf.org/content/cubox-i4pro (Search for Install the bootloader)

then I updated u-boot with the Debian u-boot package

root@bokocube:/usr/lib/u-boot/mx6_cubox-i# dd if=/usr/lib/u-boot/mx6_cubox-
i/SPL of=/dev/mmcblk0 bs=1K 
seek=1
39+0 records in
39+0 records out
39936 bytes (40 kB) copied, 0.0141093 s, 2.8 MB/s
root@bokocube:/usr/lib/u-boot/mx6_cubox-i# dd if=/usr/lib/u-boot/mx6_cubox-
i/u-boot.img of=/dev/mmcblk0 
bs=1K seek=42
293+1 records in
293+1 records out
300384 bytes (300 kB) copied, 0.0539846 s, 5.6 MB/s
root@bokocube:/usr/lib/u-boot/mx6_cubox-i#

from

root@bokocube:~# apt-cache policy u-boot
u-boot:
  Installed: 2014.04-2
  Candidate: 2014.04-2
  Version table:
 *** 2014.04-2 0
        500 http://ftp-stud.fht-esslingen.de/debian/ sid/main armhf Packages
        100 /var/lib/dpkg/status
root@bokocube:~# 

Is there anything else you recommend to do to get u-boot properly installed?

Thanks,
Rainer

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