mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* NAND defect Block handling
@ 2012-05-25 19:35 Jürgen Kilb
  2012-05-25 19:58 ` Sascha Hauer
  0 siblings, 1 reply; 2+ messages in thread
From: Jürgen Kilb @ 2012-05-25 19:35 UTC (permalink / raw)
  To: barebox

Hi,
I discovered a problem which I thought would be handled in a different way..
During "tftp 250Mbyte_Testimage.bin /dev/nand0.rootfs.bb" an I/O error occurred
and tftp stopped downloading/writing the file to the nand0.rootfs.bb partition.

===
...###################################write: I/O error

tftp failed: error -5
===

As far as I debugged the problem, a block erase error occurred. I thought the
normal behavior should be, mark the defect block as bad and continue with 
the next block.

What is the best way to handle such problems?

- implement such a behavior if the destination is a *.bb device
- add a nand_write command
- add a global option to mark a bad nand block


greetings,
Jürgen

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-05-25 19:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-25 19:35 NAND defect Block handling Jürgen Kilb
2012-05-25 19:58 ` Sascha Hauer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox