Hi Ian, > I don't have a cubox but I was under the impression that the default > u-boot environment (at least for the u-boot packaged in Debian) would Do > The Right Thing.
I still have issues to boot a cubox-i with the u-boot supplied by Debian, but maybe I install it the wrong way. u-boot contains for the cubox-i 4 files: root@bokocube:/usr/lib/u-boot/mx6_cubox-i# ls -l total 700 -rw-r--r-- 1 root root 39936 May 27 00:40 SPL -rw-r--r-- 1 root root 34393 May 27 00:39 u-boot-spl.bin -rw-r--r-- 1 root root 300384 May 27 00:38 u-boot.img -rw-r--r-- 1 root root 334240 May 27 00:40 uboot.elf root@bokocube:/usr/lib/u-boot/mx6_cubox-i# When I follow in https://wiki.debian.org/ArmHardFloatPort/CuBox-i the link http://imx.solid-run.com/wiki/index.php?title=Building_the_kernel_and_u-boot_for_the_CuBox-i_and_the_HummingBoard#U-Boot_Upstream there is listed / Flashing SPL - / / sudo dd if=SPL of=/dev/sdX bs=1K seek=1/ / Flashing u-boot.img as raw to the micro SD - / / sudo dd if=u-boot.img of=/dev/sdX bs=1K seek=42/ I assume that applies to the Debian u-boot as well: root@bokocube:/usr/lib/u-boot/mx6_cubox-i# dd if=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=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# # 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:/usr/lib/u-boot/mx6_cubox-i# What are the other two files -rw-r--r-- 1 root root 34393 May 27 00:39 u-boot-spl.bin -rw-r--r-- 1 root root 334240 May 27 00:40 uboot.elf used for? E.g. I do not see the environment overwritten to define a default bootcmd reading the boot.scr. Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/
