Problems with 128MB DoC 2000

[Zachi Friedman]

Dave,

I have just grabbed one of those MD2202-D128, and ran some tests on it.
It is built out of 2 flash devices, 64MB each. They seem to be Samsung
KM29V512000, and their flash chip ID is EC 76.

It seems you have a problem if you get C6 C6... It is definitely not the
correct flash ID.

Zachi.

-----Original Message-----
From: linux-mtd-bounces at lists.infradead.org
[mailto:linux-mtd-bounces at lists.infradead.org] On Behalf Of Dave Dillow
Sent: Wednesday, July 30, 2003 4:56 PM
To: linux-mtd at lists.infradead.org
Cc: dwmw2 at infradead.org
Subject: Problems with 128MB DoC 2000

I've got a DoC MD2202-D128-X that I'm trying to get working with Linux.
The binary only drivers from M-Sys may be an option, but I'd much rather
have the source to work with.

I first tried the CVS version of docprobe, and it reported an unknown
chip ID of 0x30. Following an exchange between David Woodhouse and Zachi
Friedman, I cooked up the attached patch to docprobe, which lets it find
my 2000, but then it fails with the following errors:

Using configured DiskOnChip probe address 0xd0000
DiskOnChip 2000 found at address 0xD0000
Unknown flash chip found: C6 C6
Please report to dwmw2 at infradead.org
Unknown flash chip found: C6 C6
Please report to dwmw2 at infradead.org
Unknown flash chip found: C6 C6
Please report to dwmw2 at infradead.org
Unknown flash chip found: C6 C6
Please report to dwmw2 at infradead.org
No flash chips recognised.

It seems kind of odd that the flash id and manufacturer id are the same
number, so I also tried forcing the chip to be a Millennium, and got the
expected failure -- it did not report unknown flash chips; it didn't see
any at all.

So, if doc2000.c is working for DoC 2000 < 128MB, then it looks like the
new ASIC changed more than just the toggle bit?

I have a fairly urgent need to get this working in some form or fashion.
I'm guessing the programming information is not publicly available --
any pointers on who I should talk to? Zachi, maybe? I'm willing to write
the code if I can get the information, or at the very least, I can be a
pretty quick turnaround tester.
-- 
Dave Dillow <dave at thedillows.org>