Hi all,
I am looking at replacing the DM365 DVEVM's obsolete Micron NAND MT29F16G08FAA with an 8Gbit 8 bit MT29F8G08ABABA . I have queried Sprufg5A Rev Aug 2009 Sect 11.2.1.2 which says the RBL supports the following (first column) of Device ID's:
Device ID block extra data) (For address) No. of address cycles
0x43 32 512+16 13 3
0x45 32 512+16 13 3
0x53 32 512+16 13 3
0x55 32 512+16 13 3
0x73 32 512+16 13 3
0x33 32 512+16 13 3
0x75 32 512+16 13 3
0x35 32 512+16 13 3
0x76 32 512+16 13 4
0x36 32 512+16 13 4
0x79 32 512+16 13 4
0x71 32 512+16 13 4
0x46 32 512+16 13 4
0x56 32 512+16 13 4
0x74 32 512+16 13 4
0xF1 64 2048+64 22 4
0xA1 64 2048+64 22 4
0x78 32 512+16 13 4
0x98DA 64 512+16 14 4
0x98DC 64 512+16 14 4
Looking next at the MT29F8G08ABABA's parameter tables, the JEDEC Manufacturer ID is 0x2C which is not listed in the above (Is this Jedec Manu ID the correct "ID" I should be referencing?). I have browsed a number of related NAND links on this forum but unfortunately none have been too helpful in telling either a definite yay or nay regarding support.
I do know that I have Rev 1.2 Silicon (Rev E DVEVM) and would ultimately like to know whether the RBL will be able to boot off a MT29F8G08ABABA NAND & then secondly (& secondary as it should theoretically be posted on the Linux forum), whether this NAND is supported by the Arago DVEVM v3.1 and its packaged kernel (or at least where I can look to see whether it is supported).
It was mentioned in a previouspost that the 4th ID byte information on the NAND might have some relevance? According to my NAND datasheet,the 90h "Read ID" command returns: 0x2C; 0x38; 0x00; 0x26; 0x85 @ address 20h. Further to this, the 90h "Read ID" command returns 0x4F;0x4E;0x46;0x49 @ address 20h. Am I able to use this data somehow to determine support?
I would appreciate any input on the above as to where to turn next.
Many thanks,
NicKA