[E3-hacking] Understanding the E3s Partitions

Ralph Corderoy ralph at inputplus.co.uk
Sun Apr 14 09:43:00 BST 2019


Hi Nick,

> mtd0
> Block Size 16384,Page Size 512, 00B Size 16
> Dumping data starting at 0x00000000 and ending at 0x00380000...*
> mtd1
> Block Size 16384,Page Size 512, 00B Size 16
> Dumping data starting at 0x00000000 and ending at 0x00040000...*
> mtd2
> Block Size 16384,Page Size 512, 00B Size 16
> Dumping data starting at 0x00000000 and ending at 0x00040000...
> mtd3
> Block Size 16384,Page Size 512, 00B Size 16
> Dumping data starting at 0x00000000 and ending at 0x00040000...*
> mtd4
> Block Size 16384,Page Size 512, 00B Size 16
> Dumping data starting at 0x00000000 and ending at 0x01b00000...*
> mtd5
> Block Size 16384,Page Size 512, 00B Size 16
> Dumping data starting at 0x00000000 and ending at 0x000c0000...
>
> Why are there saying all the same block size..?

Because they are all the same block size.  It looks like that flash has
pages and blocks.  Reading/writing is a page at a time, 256 B, whilst
erasing is a block at a time, 16 KiB, and erases all the pages in the
block.  Only an erased page can be written.  Erasing tends to be slow.
See http://www.linux-mtd.infradead.org/doc/nand.html, especially the
`NAND technical view'.

-- 
Cheers, Ralph.



More information about the e3-hacking mailing list