NAND bad blocks
NAND memory apparently gets shipped with blocks that are already bad. The vendor just marks those blocks as bad, thus resulting in higher yield and lower per-unit cost.
There is some number of blocks at the beginning which are guaranteed to be good. That number is currently unknown for our NAND chip.
The solution is split into various pieces
The boot loader itself contains a small first-stage boot loader for the Steppingstone.
This code (which Harald wrote in ARM assembly) needs to be altered to detect and skip bad blocks. At this time, the bootloader could itself extend over bad blocks. However, how do we first flash the bootloader into NAND? The JTAG flashing program has no support for detecting bad blocks.
The kernel is contained in its own partiton QT2410#NAND. We have to flash it using the
command, and read it later again via
command. Those two variants (as opposed to their non-".e"-postfixed versions) simply skip bad blocks
The root filesystem uses JFFS2, which is already bad block tolerant. It, too, has to be written using the
command in u-boot