![]() |
Re: Editing n900's rootfs.jffs2
writing to mtd with dd is prone to fail, as dd doesn't know about bad block management in mtd, and mtd is a *raw* device where you eventually will run into an occasional bad block.
There are tools that are specifically built to deal with bad blocks on mtd, e.g mtd_debug is one of them I'd assume, available in fremantle. /j |
Re: Editing n900's rootfs.jffs2
Correct way how to erase/flash rootfs partition (on which is ubi) is to use ubiformat utility.
Before using ubiformat utility, first any mounted ubifs volume must be umounted and ubi device deattached from mtd partition. Code:
$ umount ubi:rootfsCode:
$ ubiformat /dev/<mtd_rootfs>Code:
$ ubiformat /dev/<mtd_rootfs> -s 512 -O 512 -f <image.ubi>Code:
$ ubiattach /dev/ubi_ctrl -p /dev/<mtd_rootfs>Code:
$ mount ubi:rootfs </mountpoint> -t ubifs |
Re: Editing n900's rootfs.jffs2
So correct way how to mount N900 rootfs on computer using nandsim is:
(this will use ubiformat instead mtdblock and dd as in #3rd post) 1. Load nandsim module (which emulate nand mtd device) with same layout as has N900: Code:
$ modprobe nandsim first_id_byte=0x20 second_id_byte=0xaa third_id_byte=0x00 fourth_id_byte=0x15 parts=1,3,2,16,16,2010Code:
$ modprobe ubiCode:
$ ubiformat /dev/mtd5 -s 512 -O 512 -f <rootfs_image>Code:
$ ubiattach /dev/ubi_ctrl -p /dev/mtd5Code:
$ mkdir -p /mnt/n900Umounting & cleaning: Code:
$ umount /mnt/n900 |
| All times are GMT. The time now is 11:08. |
vBulletin® Version 3.8.8