I don't mind dumb questions because I'm feeling pretty clueless about this issue. Yes, I believe that the system.img has been flashed correctly to the NAND. For both the development kit and our board, I use the following fastboot commands to write all the images to NAND through USB. I notice that userdata.img is not included (I'm not sure why). But as I mentioned the development kit works using these commands, so I do not think that userdata.img is needed. - "fastboot flash bootloader u-boot.bin" - "fastboot flash kernel zImage" - "fastboot flash ramdisk ramdisk-uboot.img" - "fastboot flash system system.img" - "fastboot erase userdata" - "fastboot erase cache" Thanks -Barry > Date: Tue, 1 Mar 2011 17:59:47 -0500 > Subject: Re: [android-porting] android fails to mount nand yaffs2 system image > From: [email protected] > To: [email protected] > CC: [email protected] > > Barry, > > A quick dumb question..but did you flash the system.img and > userdata.img files to the NAND? Looks like the partitions were > properly mounted..and it's possible that the partitions are indeed > empty.. > > Regards > -- Ashwin > > > > On Tue, Mar 1, 2011 at 3:46 PM, Barry <[email protected]> wrote: > > Hi All, > > > > I am bringing up a new board which is based on the Samsung SMDKV210 > > development kit. The kernel is 2.6.32 and it is Android Froyo. I > > have fixed some bootloader issues and modified the kernel to match our > > board. > > > > During the boot up, I get to the point where the yaffs system image is > > mounted, and it appears to complete correctly. However, after the > > system is mounted, I get errors that binaries in /system/bin/ cannot > > be found. > > > > I've searched the forums and have found others with similar issues > > which turned out to be permission issues. I've tried all of their > > suggestions and have not been able to solve the issue. > > > > The unusual part of this issue is that I can build the system for the > > development kit without any issue, and the modifications between the > > development kit build and our board build are minimal. So I do not > > see how any of the changes that were made for our board would effect > > the file system and it's ability to be mounted. Also I do not see how > > this could be a hardware issue since we are reading the images from > > the NAND. > > > > Any suggestions would be greatly appreciated. > > > > Here is the part of the log where I am getting stuck: > > > > --- joe, LINE: 291, name: ro.hardware > > -yaffs: dev is 32505860 name is "mtdblock4" > > yaffs: passed flags "" > > yaffs: Attempting MTD mount on 31.4, "mtdblock4" > > -- joe, LINE: 291, name: ro.revision > > --- joe, property set > > yaffs_read_super: isCheckpointed 0 > > yaffs: dev is 32505862 name is "mtdblock6" > > yaffs: passed flags "" > > yaffs: Attempting MTD mount on 31.6, "mtdblock6" > > yaffs_read_super: isCheckpointed 0 > > yaffs: dev is 32505861 name is "mtdblock5" > > yaffs: passed flags "" > > yaffs: Attempting MTD mount on 31.5, "mtdblock5" > > yaffs_read_super: isCheckpointed 0 > > --- joe, drain action queue > > --- joe, in load_properties_from_file, file read > > --- init: cannot find '/system/bin/sh', disabling 'console' > > init: cannot find '/system/bin/pvrsrvinit', disabling 'pvrsrvinit' > > init: cannot find '/system/bin/servicemanager', disabling > > 'servicemanager' > > init: cannot find '/system/bin/vold', disabling 'vold' > > init: cannot find '/system/bin/netd', disabling 'netd' > > init: cannot find '/system/bin/debuggerd', disabling 'debuggerd' > > init: cannot find '/system/bin/rild', disabling 'ril-daemon' > > init: cannot find '/system/bin/app_process', disabling 'zygote' > > init: cannot find '/system/bin/mediaserver', disabling 'media' > > init: cannot find '/system/bin/dbus-daemon', disabling 'dbus' > > init: cannot find '/system/bin/installd', disabling 'installd' > > init: cannot find '/system/etc/install-recovery.sh', disabling > > 'flash_recovery' > > init: cannot find '/system/bin/keystore', disabling 'keystore' > > joe, in load_properties_from_file, file read > > --- joe, in load_properties_from_file, file read > > F:system/core/init/init.c, main():984 device_fd: 4 > > > > > > -- > > unsubscribe: [email protected] > > website: http://groups.google.com/group/android-porting > >
-- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
