[E3-Hacking] V2 release - Handling bad NAND blocks

Matt Callow mc-lists at tesco.net
Fri Sep 29 11:27:34 BST 2006


I thought I'd give the release a try (up to now I've always copied the 
kernel over serial and used nfs root) but it appears that I have some 
bad blocks in the NAND on my device:

Found ldr.img
   Erasing /dev/mtd3
Erasing 16 Kibyte @ 0 --  0 % complete.
Skipping bad block at 0x00004000

Skipping bad block at 0x00008000
Erasing 16 Kibyte @ c000 -- 18 % complete.Erasing 16 Kibyte @ 10000 -- 
25 % complete.Erasing 16 Kibyte @ 14000 -- 31 % complete.Erasing 16 
Kibyte @ 18000 -- 37 % complete.Erasing 16 Kibyte @ 1c000 -- 43 % 
complete.Erasing 16 Kibyte @ 20000 -- 50 % complete.Erasing 16 Kibyte @ 
24000 -- 56 % complete.Erasing 16 Kibyte @ 28000 -- 62 % 
complete.Erasing 16 Kibyte @ 2c000 -- 68 % complete.Erasing 16 Kibyte @ 
30000 -- 75 % complete.Erasing 16 Kibyte @ 34000 -- 81 % 
complete.Erasing 16 Kibyte @ 38000 -- 87 % complete.Erasing 16 Kibyte @ 
3c000 -- 93 % complete.
   Writing ldr.img to /dev/mtd3
end_request: I/O error, dev mtdblock3, sector 32
dd: /dev/mtdblock3: Input/output error

Is it possible to move ldr further down in /dev/mtd3 ? I tried this using

dd if=/media/sda1/ldr.img of=/dev/mtdblock3 bs=16384 seek=3

that seemed to write OK, but the e3 wont boot of the nand yet. I get an 
error about missing kernel params, which repeats continuously.

Anyone got any ideas?

Matt






More information about the e3-hacking mailing list