29DL324BE 3.3V Flash Chip ID 0x0400040000

[Retroplayer]

A little frustrating. Out of the last 4 parts I have attempted to read, not one seems to be supported but all are within families that are supported and support the exact same commands. But because FlashcatUSB reads the CHIP ID and doesn't recognize it, I can't do anything. Why can't we select a device family that we absolutely know is compatible?

I love the form factor and the software for this device and I have spent over $150 on the Xport, PCB 4.0, and several adapters but so far I cannot read a single device I have attempted to read.

Yes, I know there is a compatiblity list, but I didn't know every part number I was going to try to read up front and for those that I did, silly me figured I would be able to select a chip family manually to override the auto detect like programmers I have had before.

Please add this device and consider allowing manual override or some other mechanism for devices within the same family that are compatible in future versions of the software. They are simply way too specific. Is that necessary with the way FlashcatUSB operates? Maybe there is something I don't understand, but a 128K device in the same family as a 64K device but only the 64K is specifically supported so you can't read the 128K seems strange to me. Maybe I am doing something wrong? Maybe there is a way? Help!

 

[Retroplayer]

Most of these NOR Flash devices are JEDEC standard pinouts and support JEDEC standard commands. So many more devices would be supported if we could simply override the auto-detection and there wouldn't be so many requests to add devices.

From the datasheet for this part:

https://pdf1.alldatasheet.com/datasheet-pdf/view/61858/FUJITSU/MBM29DL324BE-90PBT.html

"The MBM29DL32XTE/BE are pin and command set compatible with JEDEC standard E2PROMs. Commands are written to the command register using standard microprocessor write timings. Register contents serve as input to an internal state-machine which controls the erase and programming circuitry. Write cycles also internally latch addresses and data needed for the programming and erase operations. Typically, each sector can be programmed and verified in about 0.5 seconds. "

 

[Retroplayer]

NM, I figured out how to add the part myself to the source code to support this device and successfully read my part.

I am going to look at how the list can be imported from a separate file and read into the program. Maybe with an XML file? And possibly a generic type within a flash family. It seems doable looking through the source code. It seems that I remember that the size of the chip can be read from the memory, but I will need to refresh myself on this.

If I come up with a solution, I will share it back with the developer.