DiskOnChip 2000 128Mb problem

[Edward A. Hildum]

I had a similar experience using a DOC 2000 TSOP 256M part.  Its chip ID is 
0x30, which is right for a Millenium part, even though it has a DOC 2000 
part number.  The part also has an IPL which can be updated like Millenium 
parts.

Ted Hildum

At 09:58 AM 5/9/2003 -0700, you wrote:
> > -----Original Message-----
> > From: David Woodhouse [mailto:dwmw2 at infradead.org]
> > Sent: Friday, May 09, 2003 9:48 AM
> > To: Matthew Dharm
> > Cc: linux-mtd at lists.infradead.org
> > Subject: RE: DiskOnChip 2000 128Mb problem
> >
> >
> > On Fri, 2003-05-09 at 17:40, Matthew Dharm wrote:
> > > Is it normal for a DoC 2000 to be detected as a Millenium?
> >
> > No, but it's not normal for its contents to be read back as
> > 0x01 0x02
> > 0x03 etc. either: )
>
>Okay, so we're all on the same page.
>
> > > I've already checked the bus width and timing.
> >
> > And it's definitely not set to 16-bit? -ECONFUSED.
>
>No kidding.  I'm hoping the docs will have something useful, and I'm
>about to pull out the bus analyizer.
>
>
>Matt
>
>
>______________________________________________________
>Linux MTD discussion mailing list
>http://lists.infradead.org/mailman/listinfo/linux-mtd/