Other Parts Discussed in Thread: 4460
Hi,
I am currently porting android from 4AI.1.7 to 4AJ.2.2 on a 4460 blaze based design. I am done with xloader and uboot, and currently working on Kernel. I am able to access the file system through command line (no UI yet), and am facing with the read-only file system problem when I try to replace /system/vender/firmware/ducati-m3.bin.
I have commented out some lines in init.rc, as suggested from most google search results, here is the relevant fragment:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 mtd@system /system
#mount yaffs2 mtd@system /system ro remount
mount yaffs2 mtd@userdata /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev
on post-fs
# once everything is setup, no need to modify /
#mount rootfs rootfs / ro remount
mount rootfs rootfs / rw remount
# We chown/chmod /cache again so because mount is run as root + defaults
chown system cache /cache
chmod 0770 /cache
# This may have been created by the recovery system with odd permissions
chown system cache /cache/recovery
chmod 0770 /cache/recovery
After I modify this file, I perform instructions from 4AJ.2.2 release notes:
cd ${MYDROID}
find out/target/product/${BOARD_TYPE} -name *.img -exec rm -f {} \;
make
cp -f ${MYDROID}/out/target/product/${BOARD_TYPE}/*.img ${YOUR_PATH}/omap4_emmc_files_${BOARD_TYPE}
cd ${YOUR_PATH}/omap4_emmc_files_${BOARD_TYPE}
./mkbootimg --kernel zImage --ramdisk ramdisk.img --base 0x80000000 --board omap4 -o boot.img
cd ${YOUR_PATH}/omap4_emmc_files_${BOARD_TYPE}
dd if=/dev/zero of=./cache.img bs=1048510 count=128
mkfs.ext4 -F cache.img -L cache
sudo ./fastboot.sh
For some reason this does not work, when I swap out ducati, an error occurs:
henry@ubuntu:~/projects/4AJ2.2.SVN/trunk/mydroid$ adb push ducati-m3.bin /system/vendor/firmware/
failed to copy 'ducati-m3.bin' to '/system/vendor/firmware/ducati-m3.bin': Read-only file system
Any ideas?
Thanks!
PS: If I use prebuilt ducati binaries from http://omappedia.org/wiki/Android:_Working_with_pre-built_binaries (8.9MB) or mydroid/out/target/product/blaze/system/vendor/firmware/ducati-m3.bin (6.8MB) , kernel will not start. Log message repeats IPU related error forever. However if I use the ducati binary from mydroid/hardware/ti/domx/Ducati_binary/etc/firmware/ducati-m3.bin(1.4MB), kernel will boot and I can access the file system shortly (150seconds exactly) before it restarts again. Does this phenomenon sound familiar to anyone?
