Hi, Perhaps you can instead try to build a recovery image and then install the `otapackage` zip (sometimes called `update.zip`) from the recovery, which writes every single file directly to the filesystem mounted instead of flashing an image. Back then when I ported Android to my device I also had difficulty writing the yaffs2 image, and I found that flashing from recovery is the simplest method if you can get the recovery working.
Try to `make otapackage` and see if it compiles. Regards, Alvin Wong bill_tn於 2013年10月22日星期二UTC+8下午9時22分28秒寫道： > > Hi all, > I am trying to enable booting using android bootimages in my board based > on ti am335x. > This is a general question not tightely linked to this specific board. > I am booting my kernel using the boot.img file. But I have problem in > mounting the system partition. > I generated the system.img with the flag TARGET_USERIMAGES_USE_EXT4 > ommited. So I am supposing that the system.img fs type is yaffs2 that's why > I am flashing it in uboot with nand write.yaffs command. > > int init.rc file I added : > on fs > mount yaffs2 mtd@system /system > > this commands returns : "init: command 'mount' r=-1". > > Am I missing anything ? > can anyone help me with links or with explaining me how to add a partition > and mounting it in linux/android ? > > Thank you ! > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
