El 2014-01-01 23:24, Oscar escribió:
Hi!
After some tweaks I successfully build an image for Cubieboard2
board. Although everything works, after the first boot the u-boot
script tries to load the kernel from a missing file (I suspect that
during the initial setup, the kernel is renamed). This is how the
/boot directory and /boot/boot.script looks __after__ the first boot:
linux:~ # ll /boot
total 15915
-rw-r--r-- 1 root root 0 Jan 1 2014 0x27259817
-rw-r--r-- 1 root root 1697039 Dec 31 00:13
System.map-3.4.75-86-sunxi
lrwxrwxrwx 1 root root 1 Jan 1 01:00 boot -> .
-rw-r--r-- 1 root root 1484 Feb 26 2013 boot.readme
-rw-r--r-- 1 root root 1704 Jan 1 01:02 boot.scr
-rw-r--r-- 1 root root 1632 Jan 1 2014 boot.script
-rw-r--r-- 1 root root 95879 Dec 30 23:16 config-3.4.75-86-sunxi
-rw-r--r-- 1 root root 45384 Dec 14 12:10 cubieboard2.bin
lrwxrwxrwx 1 root root 22 Jan 1 2014 initrd ->
initrd-3.4.75-86-sunxi
-rw-r--r-- 1 root root 4191724 Jan 1 01:02 initrd-3.4.75-86-sunxi
drwx------ 2 root root 12288 Jan 1 2014 lost+found
-rw-r--r-- 1 root root 11 Jan 1 01:02 mbrid
-rwxr-xr-x 1 root root 18432 Dec 10 21:52 sunxi-spl.bin
-rw-r--r-- 1 root root 83294 Dec 31 00:20
symvers-3.4.75-86-sunxi.gz
-rw-r--r-- 1 root root 239 Dec 31 00:20
sysctl.conf-3.4.75-86-sunxi
-rw-r--r-- 1 root root 224780 Dec 10 21:52 u-boot.img
lrwxrwxrwx 1 root root 22 Jan 1 2014 uImage ->
uImage-3.4.75-86-sunxi
-rw-r--r-- 1 root root 4446424 Dec 31 00:20 uImage-3.4.75-86-sunxi
-rw-r--r-- 1 root root 5306522 Dec 31 00:14
vmlinux-3.4.75-86-sunxi.gz
linux:~ #
linux:~ # cat /boot/boot.script
setenv ramdisk boot/initrd.uboot
setenv kernel boot/linux.vmx
setenv initrd_high "0xffffffff"
setenv fdt_high "0xffffffff"
setenv bootargs loader=uboot plymouth.enable=0
console=ttyS0,115200n8 showopts ${append}
setenv kernel 'boot/linux.vmx'
setenv initrd 'boot/initrd.uboot'
setenv fdt 'cubieboard2.bin'
setenv flavor 'cubieboard2'
setenv target 'firstboot'
setenv bootdevs 'mmc'
setenv bootparts '${unit}:1'
setenv initrd_high '0xffffffff'
setenv fdt_high '0xffffffff'
setenv boottype 'bootm'
[..]
Since there is no file named "linux.vmx", u-boot fails with the
following error:
Jumping to boot.scr
## Executing script at 44000000
kerneladdr=0x48000000
ramdiskaddr=0x43100000
mmc0 is current device
** File not found boot/linux.vmx **
Of course, the first boot works because the original image contains a
file named linux.vmx and all the necessary files. u-boot script gets
updated on the first boot? How is done in other boards?
Thanks!
Nevermind, there was a problem with one of the scripts (it had DOS
end-of-line instead of UNIX). Now it works!
--
Oscar
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
