On DM355, I'm noticing that U-Boot (1.2.0 supplied with EVM) doesn't
correctly deal with bad blocks when reading the kernel image, my
understanding is that "nboot" isn't aware of them and just reads bad
data.
Having a look at the latest U-Boot sources on the project's gitweb, it's
not clear if this is fixed yet; looks like there are some new .jffs2
variants of nand commands that claim to skip bad blocks, but
common/cmd_nand.c:546 in nand_load_image() is the less-than-reassuring
comment:
/* FIXME: skip bad blocks */
If anyone has been here before and has any clues, they would be welcome.
So far in production we've seen about 2% NAND chips with bad blocks
where we want to put kernel images, so it looks like I might be learning
a lot more about U-Boot than I care to.
Thanks,
--
Jon Povey, Design Engineer
[email protected] | +44(0)1280 825983
Racelogic is a limited company registered in England. Registered number 2743719
.
Registered Office Unit 10, Swan Business Centre, Osier Way, Buckingham, Bucks,
MK18 1TB .
The information contained in this electronic mail transmission is intended by
Racelogic Ltd for the use of the named individual or entity to which it is
directed and may contain information that is confidential or privileged. If you
have received this electronic mail transmission in error, please delete it from
your system without copying or forwarding it, and notify the sender of the
error by reply email so that the sender's address records can be corrected. The
views expressed by the sender of this communication do not necessarily
represent those of Racelogic Ltd. Please note that Racelogic reserves the right
to monitor e-mail communications passing through its network
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
