Problems with DOC Millennium Plus

Problems with DOC Millennium Plus

[Roy Lauer]

> 
> The DiskOnChip Millennium Plus uses INFTL not NFTL.
You should be very
> careful using the current INFTL code -- it does not
observe the Bad Block Table.

What does it mean?
Does it mean that practically the current INFTL code
is unusable with the DiskOnChip Millennium Plus?

The DOC is recognized correctly but I keep getting
"corrupt block" errors (please see the log below).

It is because of the Bad Block Table, or is there
another reason?

Please help.

Roy Lauer
Commil Ltd.


INFTL: inftlcore.c $Revision: 1.14 $, inftlmount.c
$Revision: 1.12 $
Using configured DiskOnChip probe address 0xf0400000
DiskOnChip Millennium Plus found at address 0xF0400000
Flash chip found: Manufacturer ID: 98, Chip ID: 75
(Toshiba:NAND 32MiB 3,3V)
Flash chip found: Manufacturer ID: 98, Chip ID: 75
(Toshiba:NAND 32MiB 3,3V)
2 flash chips found. Total DiskOnChip size: 64 MiB
mtd: Giving out device 0 to DiskOnChip Millennium Plus
INFTL: Media Header ->
    bootRecordID          = BNAND
    NoOfBootImageBlocks   = -1
    NoOfBinaryPartitions  = 1
    NoOfBDTLPartitions    = 1
    BlockMultiplerBits    = 0
    FormatFlgs            = 1
    OsakVersion           = 0x35313430
    PercentUsed           = 98
    PARTITION[0] ->
        virtualUnits    = 32
        firstUnit       = 4
        lastUnit        = 35
        flags           = 0x20000000
        spareUnits      = 0
    PARTITION[1] ->
        virtualUnits    = 1969
        firstUnit       = 37
        lastUnit        = 2047
        flags           = 0xc0000000
        spareUnits      = 2
INFTL: corrupt block 1024 in chain 1024, chain length
0, erase mark 0xbf?
INFTL: formatting chain at block 1024
INFTL: formatting block 1024
MTD: Error 0xffffffa5 erasing at 0x2000000
INFTL: error while formatting block 1024
INFTL: corrupt block 1025 in chain 1025, chain length
0, erase mark 0xbf?
INFTL: formatting chain at block 1025
INFTL: formatting block 1025
MTD: Error 0xffffffa5 erasing at 0x2008000
INFTL: error while formatting block 1025
INFTL: corrupt block 1026 in chain 1026, chain length
0, erase mark 0xbf?
INFTL: formatting chain at block 1026
INFTL: formatting block 1026
MTD: Error 0xffffffa5 erasing at 0x2010000
INFTL: error while formatting block 1026
INFTL: corrupt block 1027 in chain 1027, chain length
0, erase mark 0xbf?
INFTL: formatting chain at block 1027
INFTL: formatting block 1027
MTD: Error 0xffffffa5 erasing at 0x2018000
INFTL: error while formatting block 1027
INFTL: corrupt block 1028 in cha
......


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/

Re: Problems with DOC Millennium Plus

[David Woodhouse]

If your mailer is broken and loses References: headers, get a real one.
Don't just remove 'Re:' from your subject line to get around the
filters. 

On Wed, 2004-02-04 at 02:12 -0800, Roy Lauer wrote:
> > The DiskOnChip Millennium Plus uses INFTL not NFTL.
> You should be very
> > careful using the current INFTL code -- it does not
> observe the Bad Block Table.
> 
> What does it mean?
> Does it mean that practically the current INFTL code
> is unusable with the DiskOnChip Millennium Plus?
> 
> The DOC is recognized correctly but I keep getting
> "corrupt block" errors (please see the log below).

It does indeed look like it's trying to erase blocks which are actually
bad -- which it should have _known_ are bad if it had been able to read
the BBT.

We really do need to implement support for reading the BBT.

-- 
dwmw2

Re: Problems with DOC Millennium Plus

[Greg Ungerer]

David Woodhouse wrote:
> If your mailer is broken and loses References: headers, get a real one.
> Don't just remove 'Re:' from your subject line to get around the
> filters. 
> 
> On Wed, 2004-02-04 at 02:12 -0800, Roy Lauer wrote:
> 
>>>The DiskOnChip Millennium Plus uses INFTL not NFTL.
>>
>>You should be very
>>
>>>careful using the current INFTL code -- it does not
>>
>>observe the Bad Block Table.

How did you format the DoC INFTL?
Did you use the M-Systems tools, or a modified nftl_format
under Linux?


>>What does it mean?
>>Does it mean that practically the current INFTL code
>>is unusable with the DiskOnChip Millennium Plus?
>>
>>The DOC is recognized correctly but I keep getting
>>"corrupt block" errors (please see the log below).
> 
> 
> It does indeed look like it's trying to erase blocks which are actually
> bad -- which it should have _known_ are bad if it had been able to read
> the BBT.
> 
> We really do need to implement support for reading the BBT.

I have a modified nftl_format code that reads the BBT when
doing the INFTL formating, and thus avoids the appropriate
bad blocks at format time. Now we just need the inftlmount
code to parse it as well.

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
SnapGear -- a CyberGuard Company            PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com