superfluous
New Member
I am having some trouble programming my S29GL064N devices. They will read and erase just fine, but when programming, it fails. If I read the chip after a failed program, there are random blocks of 0xFF in the mix where valid data is supposed to be. The pattern changes every time I try to program. I have tried several chips and get the same general results. These are brand new chips.
Also, the chips are being incorrectly detected as a S29GL064M, so I wonder if this has anything to do with it. Also, while the size is usually correctly detected at 8MB, one time it detected as 16MB. In the source code I do see a reference to S29GL064N.
If I up the voltage to 5v with the DIP switch (note that this is a 3v device) then far fewer blocks are 0xFF but I still do not get a successful program. This suggests to me that it is a software or firmware timing issue. I say this because devices can accept up to 12v on the WP/ACC line for faster programming.
I downloaded the latest software, and tried earlier versions to be sure, but nothing helped. All fail to program the chips in the same way. I also tried the console version and got the same results. I have tried changing just about every imaginable setting and nothing helps.
If there is anything I can try let me know.
Here is the console log:
After this the program fails with "Write operation was not successful."
I then programmed a file that has a bunch of zeros to easily visualize the problem. Note the difference between 3v and 5v programming.
3v programming:
5v programming:
Note that I am more than happy to send some of these chips to developers if that is necessary to support them.
Also, the chips are being incorrectly detected as a S29GL064M, so I wonder if this has anything to do with it. Also, while the size is usually correctly detected at 8MB, one time it detected as 16MB. In the source code I do see a reference to S29GL064N.
If I up the voltage to 5v with the DIP switch (note that this is a 3v device) then far fewer blocks are 0xFF but I still do not get a successful program. This suggests to me that it is a software or firmware timing issue. I say this because devices can accept up to 12v on the WP/ACC line for faster programming.
I downloaded the latest software, and tried earlier versions to be sure, but nothing helped. All fail to program the chips in the same way. I also tried the console version and got the same results. I have tried changing just about every imaginable setting and nothing helps.
If there is anything I can try let me know.
Here is the console log:
Code:
Connected to FlashcatUSB XPORT, firmware version: 5.28
Detecting connected Flash device...
Initializing Parallel NOR device mode
Parallel mode successfully initialized
Attempting to automatically detect Flash device
Mode NOR X16 (Word addressing) returned ident code: 0x01227E0C01
Successfully detected device in NOR X16 (Word addressing) mode
Connected to Flash (CHIP ID: 0x01227E0C01)
Common Flash Interface information present
Flash detected: Cypress S29GL064M (8,388,608 bytes)
Programming mode: Parallel I/O
Device interface: NOR X16 (3V)
Write mode supported: Standard
Flash device successfully detected and ready for operation
Disconnected from FlashcatUSB XPORT device
Connected to FlashcatUSB XPORT, firmware version: 5.28
Detecting connected Flash device...
Initializing Parallel NOR device mode
Parallel mode successfully initialized
Attempting to automatically detect Flash device
Mode NOR X16 (Word addressing) returned ident code: 0x01227E0C01
Successfully detected device in NOR X16 (Word addressing) mode
Connected to Flash (CHIP ID: 0x01227E0C01)
Common Flash Interface information present
Flash detected: Cypress S29GL064M (8,388,608 bytes)
Programming mode: Parallel I/O
Device interface: NOR X16 (3V)
Write mode supported: Standard
Flash device successfully detected and ready for operation
Sent memory erase command to device: Cypress S29GL064M
Opened file for writing: d.BIN, (size: 4,194,304 bytes)
Target Flash address: 0x00000000, bytes to write: 4,194,304 bytes
After this the program fails with "Write operation was not successful."
I then programmed a file that has a bunch of zeros to easily visualize the problem. Note the difference between 3v and 5v programming.
3v programming:
5v programming:
Note that I am more than happy to send some of these chips to developers if that is necessary to support them.