>
> The problem is?
> The problem is, as long as the boot data might be damaged, I think I'll
have to get
> YAFFS managing the boot image. So I guess storing raw data on the chip
would not
> be appropriate. :D
>
I am unclear where you fear damage (power fail or bad blocks?) and what
"boot data" refers to. Is this an executable bootloader required for system
maintainance or a kernel image? A yaffs image is simply a list of 512+16
byte data that is stored in non-broken blocks of nand within a partition.
This can be derived either from mkyaffsimage directly or made on the fly by
adding yaffs support to the bootloader and writing the file - I do both. Bad
blocks are uncommon and are allegedly caused only by writes not reads. If
you just have one big chunk of data (eg kernel image) you could easily write
out raw data and skip any bad blocks found (marking the block as bad of
course) at write time. Reading is then a simple reversal of this.
Nick
---------------------------------------------------------------------------------------
This mailing list is hosted by Toby Churchill open software (
www.toby-churchill.org).
If mailing list membership is no longer wanted you can remove yourself from the list by
sending an email to
yaffs-request@toby-churchill.org with the text "unsubscribe"
(without the quotes) as the subject.
(text/plain)