On Sat, 2 Oct 2010 14:50:23 +0200 Matthias Weißer weisserm@arcor.de wrote:
Hi Scott
Am 01.10.2010 21:52, schrieb Scott Wood:
On Fri, 1 Oct 2010 16:31:40 +0200
MT29F16G08CBABA The NAND is connected (8 bit wide) to an iMX25 which is booting from NOR. So the NAND is only a mass storage device. I am able to read the ID of the chip.
2Ch 48h 04h 46h 85h
According to http://patchwork.ozlabs.org/patch/60042/, this chip is supposed to have ID: 2C 48 00 26 89
Take a closer look at the table in the link. There is a MT29F16G08ABABA with ID: "2C 48 00 26 89" and a MT29F16G08CBABA with ID: "2C 48 04 46 85". The second one is the one I have here.
Ah, misread the part name.
I have also a datasheet of the chip here from where I copy & pasted the above ID. The ID gets read correctly from the chip by u-boot NAND subsystem.
Does the datasheet say anything about what it intends that bit to mean? Is there a new ID format we need to support?
Do you have a datasheet that says what it's supposed to be?
The bytes may be getting corrupted. If you hack up the code to override the ID bytes with good ones, do you see any problems doing real I/O?
I tried that. If I run a "nand bad" command then it never returns and keeps performing some actions on the NAND device as I can see with an oscilloscope.
Could you instrument the code to see what software thinks it's doing?
-Scott