You are using HDD terms here. Forget them.
Spare area is part of the page, or other parts that are not DATA. It can contain page, block, sector numbers, test bytes, padding, other bytes that indicate things like versions of the page.
Also the context matters.
If you are talking about reading the NAND for a complete dump, then really you are interested in getting a complete copy of the chip, then parsing it using info from Spare Area. You break it down into blocks and pages, reverse whatever manipulations the controller did to start to rebuild the DATA .. it could be a disk image, raw custom file system etc.. this is where you start to talk about system / firmware etc.
Of course like everything, the terms can get used flippantly, but as long as you know the context, you should be ok.
Also, the actual schemes that vendors use vary a LOT. So you will see pretty much anything you can think of. It is Rule 34 for NAND basically!
Flash don't use the term G-List.
If you break it down like when reading a chip and talking about dumps:
chip / crystal / plane / bank / block / page / (DATA / Spare Area / pad) / byte / bit
you should be ok, then pickup all the nuanced cases as they arise.
|