DM355 NAND Flash Selection

Terry said:

1) SPRUFB3 (page 160) lists the compatible NAND Flash by (single byte) Device ID, but I can't seem to find the Device ID in the Flash datasheet (maybe I'm just missing it?).  As I understand SPRUFB3 this byte is read from the Flash and compared to the table.  If the datasheet doesn't list the device ID then I can't say for sure if the device is supported or not.

The device id code should be listed in the datasheet, unfortunately the MT28F16G08DAAWP seems to require an NDA to access the datasheet, so I cannot really verify this on a public forum, you may want to contact Micron for such issues, note that there may be several informational bytes in the NAND in addition to the device id. 

Terry said:

2) Is there a list available that correlates the Device ID in SPRUFB3 to manufactures P/N?

Unfortunately there is not that I have seen, since the table was put into place long ago during silicon development it is likely that many of the IDs are in the same situation as your current NAND or worse anyway. 

Terry said:

3) The forum indicated that the RBL would be updated from time-to-time.  Does anyone know when the next update will be?  Does anyone know what the new device ID table will look like, i.e. what Flash devices will be supported?

There is always the potential that there will be an updated RBL, though this would mean a new silicon revision, at the moment I do not believe there are any plans to extend the NAND table, and I see no mention of rev 1.2 silicon adding any additional NAND devices to the table, I will look into this and let you know if I find that device ids have been added (or will be).

Terry said:

4) Lacking item 2, can anyone recommend a Flash to replace the one going obsolete (MT29F16G08DAAWP) that is also in the table?

Unfortunately I do not know of a good replacement, perhaps someone on the forum can comment on options they have come across. I can suggest some alternative booting strategies however, for one you could attempt to get a lifetime buy for the NAND with Micron, assuming you are already in production and purchasing parts. Another option would be to switch to NOR flash instead of NAND if it is acceptable. The third option would be to boot from some other device and have a higher level boot loader on the NAND, i.e. boot from I2C, SPI, or UART to load a secondary boot loader that can read the main boot loader from the NAND.

Thanks Bernie,

Looking at the datasheet for the new part I can't seem to devine the Device ID. I will request the datasheet for the old part and compare.

This is quite frustrating.  How do people pick a NAND Flash that the DM355 will recognize and boot from?

Terry

Bernie,

Downloaded the datasheet for the old part and I think I'm starting to figure out a few things.

The Flash Read ID command (90h) will return 5 bytes, 0-4.  Byte 1 is the Device ID.  The ID for the MT29F16G08DAA is D3h.  I don't see D3 in the DM355 table which means that the default ID will be used, which looks like it happens to fit this part.

Now that I know where to find the ID I looked at the datasheet for the new part, the MT29F16G08ABABA, which doesn't detail the Read ID bytes nearly as well as the above datasheet, and find that the Device ID for this part is 48h.  48 isn't in the DM355 table either, but in this case the default doesn't fit the Flash.

If my thinking is off here, please let me know.

We went through this loop at the beginning of the year. At least on the DM355 EVM the DAA does not appear to work. We ended up buying a few 29F16G08FAA , which do work on the DM355 EVM running WinCE. These cost us an inflated price, I think they are end of life. I heard Spectrum had a lifetimes supply of this part in for these boards.

At that time we could not find a non-obsolete part that would work on the EVM. If there is no such part maybe the RBL should be changed.