|
On Saturday 14 June 2014 14:23:33 you wrote: > On Sat, 2014-06-14 at 14:42 +0200, Rainer Dorsch wrote: > > On Saturday 14 June 2014 13:35:40 Ian Campbell wrote: > > > Your boot command should load and then source the boot.scr which > > > flash-kernel has created, it contains the right things and is > > > automatically updated when the kernel/initramfs/etc changes. > > > > Wow, that is a nice solution. Is there somewhere the boot.cmd out of which > > mkimage generates the boot.scr ? > > I don't think it is preserved anywhere. You can extract it with > dd if=/boot/boot.scr bs=64 skip=1 of=/tmp/boot.cmd >
Weired, I think I managed once to get the system booted, but after that I am always stuck when starting the kernel.
I adapted the boot.cmd file to
root@bokocube:~# cat boot.cmd # boot script for CuBox-i
setenv device mmc setenv mmcdev 0 setenv mmcpart 2 setenv partition ${mmcdev}:${mmcpart} setenv bootargs 'quiet'
#image_locations='/boot/ /' kvers='3.15-rc8-armmp'
#for pathprefix in ${image_locations} #do
setenv loadaddr 0x10800000 setenv ramdiskaddr 0x11800000 setenv fdt_addr 0x18000000 setenv pathprefix /boot/
load ${device} ${partition} ${loadaddr} ${pathprefix}vmlinuz-${kvers} load ${device} ${partition} ${fdt_addr} ${pathprefix}dtb-${kvers} load ${device} ${partition} ${ramdiskaddr} ${pathprefix}initrd.img-${kvers} echo "Booting Debian ${kvers} from ${device} ${partition}..." bootz ${loadaddr} ${ramdiskaddr}:${filesize} ${fdt_addr}
root@bokocube:~#
and load it with
# mkimage -A arm -O linux -T script -C none -n "U-Boot commands" -d /root/boot.cmd /boothelper.scr
Then on u-boot: ext4load mmc 0:2 0x19000000 /boothelper.scr source 0x19000000
and get
CuBox-i U-Boot > run boottest 753 bytes read in 232 ms (2.9 KiB/s) ## Executing script at 19000000 2857680 bytes read in 247 ms (11 MiB/s) 28603 bytes read in 126 ms (221.7 KiB/s) 10934444 bytes read in 621 ms (16.8 MiB/s) Booting Debian 3.15-rc8-armmp from mmc 0:2... Kernel image @ 0x10800000 [ 0x000000 - 0x2b9ad0 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Loading Ramdisk to 8ecf1000, end 8f75e8ac ... OK Using Device Tree in place at 18000000, end 18009fba
Starting kernel ...
Any idea why I the boot process is stuck and what I may miss? The system is really not coming up, e.g. ssh server is also not reachable.
Is anybody able to boot the compressed image with the Debian u-boot files? (booting an uncompressed image works flawless, fortunately).
Thanks, Rainer
-- Rainer Dorsch http://bokomoko.de/ |