Also if flashed 3.12_zImage (same kernel, same sources, just zImage) i see this
reading kernel..device 0 Start 1063, Count 16384 MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Count 17447, Start 2048 MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK completed Boot with zImage Wrong Ramdisk Image Format Starting kernel ... And it's stucked at "Starting kernel ..." 2014/1/17 Alexander Khryukin <[email protected]> > Thanks. > I changed env to > > baudrate=115200 > *bootcmd=movi read kernel 0 40800000;movi read rootfs 0 41000000 > 100000;bootm 40800000 41000000* > bootdelay=3 > emmcbootrecovery=mmc erase boot 1 0 0;emmc open 1;movi read fwbl1 0 > 40000000;movi write zero fwbl1 1 40000000;movi read bl2 0 40004000;movi > write zero bl2 1 40004000;movi read u-boot 0 42000000;movi write zero > u-boot 1 42000000;movi read tzsw 0 42100000;movi write zero tzsw 1 > 42100000;emmc close 1 > ethact=smc911x-0 > ethaddr=00:40:5c:26:0a:5b > gatewayip=192.168.0.1 > ipaddr=192.168.0.28 > netmask=255.255.255.0 > rootfslen= 100000 > serverip=192.168.0.13 > > > > And now trying to boot > U-Boot 2012.12-00000-g503cd8d-dirty (Jan 15 2014 - 12:58:49) for YICSYSTEM > YSE5250-scp > > > CPU: S5PC520 Rev1.0 [Samsung SOC on SMP Platform Base on ARM CortexA15] > APLL = 800MHz, MPLL = 800MHz > Board: YSE5250-scp > DRAM: 2047 MiB > > TrustZone Enabled BSP > BL1 version: 20130404 > PMIC: S5M8767 > > > Checking Boot Mode ... SDMMC > REVISION: 1.0 > REVISION: 1.0 > MMC Device 0: 3839 MB > NAME: S5P_MSHC0 > MMC Device 1: 7348 MB > MMC Device 2 not found > Net: smc911x-0 > > Hit any key to stop autoboot: 0 > reading kernel..device 0 Start 1063, Count 16384 > MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK > completed > reading RFS..device 0 Count 17447, Start 2048 > MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK > completed > ## Booting kernel from Legacy Image at 40800000 ... > Image Name: Linux-3.13.0-rc8 > > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 4754992 Bytes = 4643 KiB > > Load Address: 40008000 > Entry Point: 40008000 > Verifying Checksum ... OK > Wrong Ramdisk Image Format > Loading Kernel Image ... OK > OK > > *ERROR: booting os 'Unknown OS' (1) is not supported* > > > No changes. > But XIP is gone. > > > > 2014/1/17 Detlev Zundel <[email protected]> > >> Hello Alexander, >> >> > Thanks for your answer! >> > >> >>So again, try loading the image somewhere else in RAM and let U-Boot do >> >>the copying to the correct place. >> > >> > It's not obvious for me how to do it. >> > Might you have any guide or faq? >> >> [...] >> >> >> > ### main_loop: bootcmd="movi read kernel 0 40008000;movi read rootfs >> 0 >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> > 41000000 100000;bootm 40008000 41000000" >> ^^^^^^^^^^^^^^ >> >> Your bootmcd reads the kernel to 40008000 and then calls bootm to that >> address. Simple change those two places to, say, 40800000 by editing >> bootcmd. (Not knowing your system, I presume RAM starts at 4000,0000 >> and 4080,0000 then would be 8MiB after the beginning. U-Boot will copy >> the kernel to 4008000 so the kernel should not be bigger than 7.5MiB but >> the other snippets from your log say the kernel is ~3.2MiB, so this >> should be fine. >> >> Cheers >> Detlev >> >> -- >> The only thing that interferes with my learning is my education. >> -- Albert Einstein >> -- >> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel >> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany >> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: [email protected] >> > >
_______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
