Honored Contributor
Honored ContributorI've several days work invested in this jffs2 thing, but I'm not quite there yet. Below is a summary of what I've got so far. I'm diving into the mtd-utils stuff now...
# cat /proc/partitions major minor # blocks name 31 0 4064 mtdblock0 31 1 2048 mtdblock1 31 2 512 mtdblock2 31 3 8192 mtdblock3# cat /proc/mtd dev: size erasesize name mtd0: 003f8000 00010000 "ROMfs" mtd1: 00200000 00010000 "kernel" mtd2: 00080000 00010000 "Flash FS" mtd3: 00800000 00010000 "FPGA Cores"# ls -la /dev/mtdblock2 brw------- 1 root root 31, 2 Jan 1 1970 /dev/mtdblock2 [note I created the /dev entry in my ROMfs project as "@mtdblock2,b,31,2"] # cat /proc/partitions major minor # blocks name 31 0 4064 mtdblock0 31 1 2048 mtdblock1 31 2 512 mtdblock2 31 3 8192 mtdblock3# cat /proc/mtd dev: size erasesize name mtd0: 003f8000 00010000 "ROMfs" mtd1: 00200000 00010000 "kernel" mtd2: 00080000 00010000 "Flash FS" mtd3: 00800000 00010000 "FPGA Cores"# ls -la /var/flash drwxrwxrwx 2 root root 1024 Nov 30 18:57 . drwxr-xr-x 4 root root 1024 Nov 30 18:57 ..# mount -t jffs2 /dev/mtdblock2 /var/flash can't create lock file /etc/mtab~41: Read-only file system (use -n flag to overr ide)# mount -t jffs2 /dev/mtdblock2 /mnt -n Eep. No valid nodes for ino# 1 [the system locks up at this point...] I've created a file system image on a different machine and tried to cp it into /dev/mtdblock2, but it locks the system up as well. I compiled the mtd-tools erase program, and it's having issues as well:# cat /proc/mtd dev: size erasesize name mtd0: 003f8000 00010000 "ROMfs" mtd1: 00200000 00010000 "kernel" mtd2: 00080000 00010000 "Flash FS" mtd3: 00800000 00010000 "FPGA Cores"# cat /proc/partitions major minor # blocks name 31 0 4064 mtdblock0 31 1 2048 mtdblock1 31 2 512 mtdblock2 31 3 8192 mtdblock3# ./erase.exe /dev/mtd2 MTD_open File open error Any suggestions would be appreciated.
