I made a patch for u-boot 2009.3 which enable nand write.yaffs2 command. On Mar 25, 2:15 pm, Ashwin Bihari <[email protected]> wrote: > Guys, > > A slightly related question, since you're playing with NAND and > YAFFS2. Do you guys have a procedure handy on how to generate a YAFFS2 > RFS image and flash it to the NAND using U-boot? Also on how you flash > and load the Kernel from NAND would be great. Appreciate the > pointers.. > > Regards > -- Ashwin > > On Thu, Mar 25, 2010 at 7:54 AM, Deva R <[email protected]> wrote: > > pls checkhttp://groups.google.com/group/android-porting/msg/d303260bc1dbb08a > > > can u cross check ur init.rc for proper MTD partition mounting sequence?? > > > mount yaffs2 m...@system /system > > mount yaffs2 m...@system /system ro remount > > mount yaffs2 m...@userdata /data nosuid nodev > > mount yaffs2 m...@cache /cache nosuid nodev > > > On Thu, Mar 25, 2010 at 8:32 AM, Elvis Dowson <[email protected]> > > wrote: > >> Hi, > >> I'm facing a problem, trying to run android-2.6.29 kernel and > >> android-1.5r3 off NAND on the gumstix Overo, where somehow, the > >> android binaries in the /system/bin folder are getting deleted, like > >> vold, etc, upon boot from NAND, with the following error messages. > >> These messages appear, and after I inspect the NAND filesystem, its > >> actually gone missing. > > >> init: Unable to open persistent property directory /data/property > >> errno: 2 > >> init: cannot find '/system/bin/servicemanager', disabling > >> 'servicemanager' > >> init: cannot find '/system/bin/vold', disabling 'vold' > >> init: cannot find '/system/bin/debuggerd', disabling 'debuggerd' > >> init: cannot find '/system/bin/app_process', disabling 'zygote' > >> init: cannot find '/system/bin/mediaserver', disabling 'media' > >> init: cannot find '/system/bin/installd', disabling 'installd' > >> /system/bin/sh: can't access tty; job control turned off > > >> Before I launched android, I inspected the /system/bin folder in NAND, > >> after flashing it, and the above binaries were present. After running > >> it from NAND, these binaries disappear. > > >> My NAND partitions are as follows > > >> reating 7 MTD partitions on "omap2-nand": > >> 0x000000000000-0x000000080000 : "xloader" > >> 0x000000080000-0x000000240000 : "uboot" > >> 0x000000240000-0x000000280000 : "uboot environment" > >> 0x000000280000-0x000000680000 : "linux" > >> 0x000000680000-0x00000a680000 : "system" > >> 0x00000a680000-0x00000c680000 : "userdata" > >> 0x00000c680000-0x00000e680000 : "cache" > > >> r...@overo:/# cat /proc/mtd > >> dev: size erasesize name > >> mtd0: 00080000 00020000 "xloader" > >> mtd1: 001c0000 00020000 "uboot" > >> mtd2: 00040000 00020000 "uboot environment" > >> mtd3: 00400000 00020000 "linux" > >> mtd4: 0a000000 00020000 "system" > >> mtd5: 02000000 00020000 "userdata" > >> mtd6: 02000000 00020000 "cache" > > >> Best regards, > > >> Elvis Dowson > > >> -- > >> unsubscribe: [email protected] > >> website:http://groups.google.com/group/android-porting > > >> To unsubscribe from this group, send email to > >> android-porting+unsubscribegooglegroups.com or reply to this email with > >> the words "REMOVE ME" as the subject. > > > -- > > unsubscribe: [email protected] > > website:http://groups.google.com/group/android-porting > > > To unsubscribe from this group, send email to > > android-porting+unsubscribegooglegroups.com or reply to this email with the > > words "REMOVE ME" as the subject.
-- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting To unsubscribe from this group, send email to android-porting+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
