s5pv210平台，加载android系统的怪异问题

[armeasy]

在210平台上加载android系统时，如果将映像全放在SD卡里，没有任何问题，但是如果
编译出基于nand flash的映像后，将映像文件system.img烧写到nand flash中，则提示
如下错误信息：
[ 4.046332] yaffs: dev is 32505860 name is "mtdblock4" rw
[ 4.046383] yaffs: passed flags ""
[ 6.989726] yaffs: dev is 32505862 name is "mtdblock6" rw
[ 6.989776] yaffs: passed flags ""
[ 7.012065] yaffs: dev is 32505861 name is "mtdblock5" rw
[ 7.012113] yaffs: passed flags ""
[ 7.354978] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 7.365863] enabling adb
[ 7.366472] Enabled => usb_mass_storage
[ 7.366510] Enabled => adb
[ 7.434825] adb_open
[ 7.516211] request_suspend_state: wakeup (3->0) at 7019008377 (2010-01-01 12:31:06.221482709 UTC)
[ 7.517071] init: untracked pid 64 exited
[ 7.528860] init: untracked pid 60 exited
[ 7.538232] request_suspend_state: wakeup (0->0) at 7041031878 (2010-01-01 12:31:06.243507209 UTC)
[ 7.539010] init: untracked pid 75 exited
[ 7.548167] init: untracked pid 77 exited
link_image[1962]: 69 could not load needed library 'libc.so' for '/system/bin/sh' (load_library[1104]: Library 'libc.so' not found)CANNOT LINK EXECUTABLE
[ 7.762338] init: untracked pid 74 exited
[ 7.821526] android_usb gadget: high speed config #1: Android Composite
link_image[1962]: 80 could not load needed library 'libc.so' for '/system/bin/sh' (load_library[1104]: Library 'libc.so' not found)[ 11.775039] request_suspend_state: wake)
[ 11.776798] init: untracked pid 89 exited
CANNOT LINK EXECUTABLE
[ 16.813831] request_suspend_state: wakeup (0->0) at 16316631003 (2010-01-01 12:31:15.519106502 UTC)
[ 16.815630] init: untracked pid 101 exited
[ 16.823109] init: untracked pid 105 exited
[ 16.827579] request_suspend_state: wakeup (0->0) at 16330380086 (2010-01-01 12:31:15.532855210 UTC)
link_image[1962]: 94 could not load needed library 'libc.so' for '/system/bin/sh' (load_library[1104]: Library 'libc.so' not found)CANNOT LINK EXECUTABLE
[ 21.871057] request_suspend_state: wakeup (0->0) at 21373857170 (2010-01-01 12:31:20.576332460 UTC)
[ 21.872906] init: untracked pid 118 exited
[ 21.880421] init: untracked pid 122 exited
[ 21.883657] request_suspend_state: wakeup (0->0) at 21386458336 (2010-01-01 12:31:20.588933334 UTC)
[ 21.885518] init: untracked pid 125 exited
link_image[1962]: 111 could not load needed library 'libc.so' for '/system/bin/sh' (load_library[1104]: Library 'libc.so' not found)CANNOT LINK EXECUTABLE
[ 26.930963] request_suspend_state: wakeup (0->0) at 26433763920 (2010-01-01 12:31:25.636239335 UTC)
[ 26.932766] init: untracked pid 135 exited
[ 26.938465] init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting into recovery mode
link_image[1962]: 128 could not load needed library 'libc.so' for '/system/bin/sh' (load_library[1104]: Library 'libc.so' not found)CANNOT LINK EXECUTABLE
[ 26.975967] Restarting system with command 'recoveryOK

U-Boot 1.3.4-dirty (Jan 5 2012 - 14:33:47) for SMDKV210


CPU: S5PV210@1000MHz(OK)

使用三星官方做好的映像文件则没有问题，用三星官方的BSP包编译出来后烧写，就会有上面问题；
使用unyaffs工具将OK的system.img解压到system目录，再使用如下指令打包：
mkyaffs2image -f ./system system.img
再将打包的system.img烧进nand，同样出现上面的问题，mkyaffs2image工具为三星BSP包生成。
将映像烧到SD卡中是不会出现上面问题的，就是放在nand中就有错，不知是何原因？

[yyhzpk]

那就肯定是mkyaffs2image的问题了，你可以用你自己解压再打包的image与OK的image
比较一下，然后两者解压再比较一下，如果解压后文件致，则有可能是system.img里面
包含有image起始地址等信息，
给你看一下三星6410打包ramdisk的命令:
mkimage -A arm -O linux -T ramdisk -C none -a 0x50800000 -n "ramdisk" -d ramdisk.img ramdisk-uboot.img

[yyhzpk]

从打包看，好像是你文件不对呀，要么就是打包后没有访问权限，你把两者解压后仔细比较一下
看有什么不同吧