Hi,

Le 07/10/2014 14:58, Paolo Pisati a écrit :
Hi,

i've been trying to update the u-boot on my board (sd booting), from the Linaro
one (2012.10) to a v2014.X, but so far had no luck:

make arndale_config
export CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf-
make

...

dd if=arndale-bl1.bin of=/dev/sdc bs=512 skip=1
dd if=arndale-spl.bin of=/dev/sdc bs=512 skip=17
dd if=./u-boot-dtb.bin of=/dev/sdc bs=512 skip=49

...

u-boot 3.10rc3 (same happens with v2014.07 or 2014.04):

U-Boot 2014.10-rc3 (Oct 07 2014 - 13:26:48) for ARNDALE

CPU:    Exynos5250@1000MHz

Board: Arndale
I2C:   i2c_init: failed to init bus 0 for speed = 100000
ready
DRAM:  2 GiB
trace: copying 00086db4 bytes of early data from 50000000 to beff0000
trace: enabled
WARNING: Caches not enabled
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
dwmci_send_cmd: DATA ERROR!
i2c_init: failed to init bus 0 for speed = 100000
In:    serial
Out:   serial
Err:   serial
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0
ARNDALE # printenv
baudrate=115200
bootargs=console=ttySAC2,115200n8 root=/dev/mmcblk1p1 rw rootwait debug 
earlyprintk
bootcmd=run bootcmd_ubuntu
bootcmd_ubuntu=run loadk; run loadf; run loadr; bootm ${kernel_addr_r} 
${ramdisk_addr_r}:${filesize} ${fdt_addr_r}
bootdelay=3
fdt_addr_r=0x41000000
filesize=5b9902
kernel_addr_r=0x40007000
loadf=ext2load mmc 1:1 ${fdt_addr_r} /boot/exynos5250-arndale.dtb
loadk=ext2load mmc 1:1 ${kernel_addr_r} /boot/uImage
loadr=ext2load mmc 1:1 ${ramdisk_addr_r} /boot/uInitrd
ramdisk_addr_r=0x42000000
stderr=serial
stdin=serial
stdout=serial

Environment size: 589/16380 bytes
ARNDALE # run loadk
6002946 bytes read in 1117 ms (5.1 MiB/s)
ARNDALE # bootm ${kernel_addr_r}
## Booting kernel from Legacy Image at 40007000 ...
    Image Name:   kernel 3.16.0-20-generic
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    6002882 Bytes = 5.7 MiB
    Load Address: 40008000
    Entry Point:  40008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK

Starting kernel ...(fake run for tracing)

Starting kernel ...

[stuck here]

I faced this problem some times ago. Try to modify kernel, initrd and fdt 
addresses.


Guillaume

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to