Re: [UPDATE] DOCBoot support for NFTL-based DOC2000

Zeri Virgo
2005-04-06T14:46:21Z

> 1) The image didn't get written properly (using nandwrite without the
> -o option would certainly have this effect, but you indicated that you
> did use -o).
Yes, I definitely used the -o option to nandwrite.

> I'm not sure where to go next. Can you please run "mtd_debug info
> /dev/mtd0" and tell me the result, just as a sanity check?
mtd.type = MTD_NANDFLASH
mtd.flags = MTD_CLEAR_BITS | MTD_ERASEABLE | MTD_OOB | MTD_ECC
mtd.size = 67108864 (64M)
mtd.erasesize = 16384 (16K)
mtd.oobblock = 512
mtd.oobsize = 16
mtd.ecctype = (unknown ECC type - new MTD API maybe?)
regions = 0

This may be useless, but I did a nanddump of the first 0x208000 bytes.
0x00 to 0xff -> data

Then each of the following chunks of data (ie, not chunks of ff) are
preceeded by OOB Data
(eg,
OOB Data: 36 7f eb 1f 3b aa ff ff ff ff ff ff ff ff ff ff
0x000000200: 0e cd...)

0x200 to 0x2ff -> data
0x400 to 0x43a -> data
0x600 to 0x629 -> data
0x800 to 0x8ff -> data
0xa00 to 0xa75 -> data

Then a large chunk (1144949 bytes)
0xc00 to 0x119075 -> data

Some mysterious OOB Data before 0x119200, though no normal data
following it.

Then the rest is blank.

- Zeri