From: "Jürgen Kilb" <J.Kilb@phytec.de>
To: barebox@lists.infradead.org
Subject: NAND defect Block handling
Date: Fri, 25 May 2012 21:35:54 +0200 [thread overview]
Message-ID: <OFFE55D117.F033B5DE-ONC1257A09.006BA85C-C1257A09.006BA869@phytec.de> (raw)
In-Reply-To:
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
next reply other threads:[~2012-05-25 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 19:35 Jürgen Kilb [this message]
2012-05-25 19:58 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OFFE55D117.F033B5DE-ONC1257A09.006BA85C-C1257A09.006BA869@phytec.de \
--to=j.kilb@phytec.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox