Verification fails on intel flash chip

Topics related to the Dataman 48Pro2
Davemartin
Posts: 1
Joined: 27 Jul 2023 07:18

Verification fails on intel flash chip

Postby Davemartin » 27 Jul 2023 07:29

Hi,

I've been using a dataman 48pro2 for the last couple of years to program some Intel E28F800B5B flash chips.
I get controllers in that have these chips on them and most of the time, the chip has gotten corrupted and I just desolder it, reflash the program and everything's is fine.
I had one recently where the chip was physically damaged so I bought some and when I try to program them I get a verification error. I can erase the chip and it blank checks fine and seems to program fine but fails verification immediately.
The chips are obsolete so I bought from ebay so thought they may be fake or faulty but I've since removed chips from working units to test and they fail verification too.

Excerpts of the log are below.

Code: Select all

L0001: Welcome to Dataman programmers control program PG4UW. L0002: Version 3.86/06.2023. L0006: Processor: Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz Frequency: 1795\1795.30 MHz L0007: CID: 1E50-DCAF:00-50-56-C0-00-08:00331-60000-00000-AA720:6D2E0134 L0008: Operating system: Windows 10 (v10.0, Build 18363). L0009: Physical RAM memory: 2038 MB L0009.S0001: Selected language: English L0012: >> 2023.Jul.27, 08:09:52 L0013: Default programmer: Dataman-48Pro2. L0014: Scanning USB port(s) for Dataman-48Pro2 .................. found at port USB. L0015: Establishing connection ... (High Speed mode) done. L0016: Programmer serial number: 1176-03846. L0019: List of command line parameters present: L0020: 1. /prj:E:\8 group\intel.eprj L0021: Buffer operation "Checksum", time elapsed: 00:00:00.2 L0023: Main Checksum of selected buffer(s): 0007F800h - Byte sum (x8), Straight L0024: ------------------------------------------------ L0025: Buffer(s) included to Main Checksum calculation: L0026: ------------------------------------------------ L0027: 1. Buffer "Program Memory" (0h..7FFh) (x8) L0028: ------------------------------------------------ L0031: Log file name: C:\Users\Siemens\AppData\Roaming\Dataman\Dataman-Pro\report.rep L0032: Log file mode: Append L0034: >> 2023.Jul.27, 08:09:58 L0035: Executing command line parameters...: /prj:"E:\8 group\intel.eprj" L0037: >> 2023.Jul.27, 08:09:58 L0038: Loading project: "E:\8 group\intel.eprj" L0039: >> 2023.Jul.27, 08:09:58 L0040: Selected device (Device selection by project load): Intel E28F800B5B [TSOP48]. L0041: -------------------------------------------------------------------- L0042: Date:||for project 2020.Sep.04 11:50:47 L0043: Created by SW version:||for project PG4UW 3.60/06.2020 L0044: Created on programmer: Dataman-48Pro2 (S/N: 1176-03846) L0045: Author: dmartin L0046: Description: L0047: -------------------------------------------------------------------- L0049: Main Checksum of selected buffer(s): 0B8F662Eh - Byte sum (x8), Straight L0050: ------------------------------------------------ L0051: Buffer(s) included to Main Checksum calculation: L0052: ------------------------------------------------ L0053: 1. Buffer "Program Memory" (0h..FFFFFh) (x8) L0054: ------------------------------------------------ L0056: >--- Begin of options list --- Intel E28F800B5B [TSOP48] --- (Device selection by project load) L0058: |>---------- Device operation options ---------- L0059: | ---------- Addresses ---------- L0060: | Split: None L0061: | ---------- Insertion test and/or ID check ---------- L0062: | Insertion test error terminates the operation: Enable L0063: | Device ID check error terminates the operation: Enable L0064: | ---------- Command execution ---------- L0065: | Erase before programming: Disable L0066: | Blank check before programming: Disable L0067: | Verify after reading: Disable L0068: | Verify: Once L0069: | Verify options: VCCmin - VCCmax L0070: | ---------- Programming parameters ---------- L0071: | ( ) Boot block only L0072: | ( ) Without boot block L0073: | (o) All blocks L0074: |<---------- Device operation options ---------- L0077: |>---------- Automatic YES! ---------- L0078: | Automatic YES!: Disable L0079: | Response time: Standard L0080: | ---------- L0081: | Device removal hold off time (in seconds): 2 L0082: | Device insertion complete time (in seconds): 5 L0083: | ---------- L0084: | Suspend on error: Enable L0085: | ---------- L0086: | NCP: 27, 37, 46, 47 L0087: |<---------- Automatic YES! ---------- L0089: <--- End of options list --- Intel E28F800B5B [TSOP48] --- (Device selection by project load) L0091: === Recent serialization settings === L0092: Serialization Mode: None L0093: === end of serialization settings === L0095: === Recent statistics settings === L0096: --- Apply statistics increment on ---- L0097: [x] Device Program L0098: [x] Device Verify L0099: [x] Device Blank check L0100: [x] Device Erase L0101: [x] Device Read L0102: ----- Count down ----- L0103: [ ] Enabled L0104: === end of statistics settings === L0106: >> 2023.Jul.27, 08:10:00 L0107: Project file MD5 checksum: B51E4D106E7C11B45C9209F14AC73C7C L0108: Elapsed time: 78 ms L0109: Project loaded successfully. L0110: Elapsed time: 2734 ms L0112: >> 2023.Jul.27, 08:10:01 L0113: Command line parameters execution finished. L0113.L0001: L0113.L0002: >> 2023.Jul.27, 08:10:02 L0113.L0003: Called menu item "Program". L0115: >> 2023.Jul.27, 08:10:02 L0116: Opened window "Program?". L0118: >> 2023.Jul.27, 08:10:04 L0119: Opened window "Device operation options". (in 0min, 0sec, 188ms) L0121: >> 2023.Jul.27, 08:10:08 L0122: Closed window "Device operation options" (by pressing "OK"). L0124: |>---------- Device operation options ---------- L0125: | ---------- Addresses ---------- L0126: | Split: None L0127: | ---------- Insertion test and/or ID check ---------- L0128: | Insertion test error terminates the operation: Enable L0129: | Device ID check error terminates the operation: Enable L0130: | ---------- Command execution ---------- L0131: |* Erase before programming: Enable L0132: |* Blank check before programming: Enable L0133: | Verify after reading: Disable L0134: | Verify: Once L0135: | Verify options: Not supported L0136: | ---------- Programming parameters ---------- L0137: | ( ) Boot block only L0138: | ( ) Without boot block L0139: | (o) All blocks L0140: |<---------- Device operation options ---------- L0142: Changed items are marked with asterisk "*" on the left. L0144: >> 2023.Jul.27, 08:10:10 L0145: Closed window "Program?" (by pressing "Yes"). L0147: >> 2023.Jul.27, 08:10:11 L0148: Programming device: Intel E28F800B5B [TSOP48]. L0149: Main Checksum of selected buffer(s): 0B8F662Eh - Byte sum (x8), Straight L0150: Programming adapter test ... L0151: Searching for programming adapter Bottom TSOP48 NOR-1 (ord.no. 70-1227) / Top TSOP48 ZIF 18.4mm (ord.no. 70-1228). L0152: Programming adapter found, identification: L0153: Bottom TSOP48 NOR-1 (ord.no. 70-1227), S/N: 1227-02111. L0154: Top TSOP48 ZIF 18.4mm (ord.no. 70-1228), S/N: 1228-02250 (168). L0155: Programming adapter test - O.K. L0156: Device insertion test ... L0157: Checking device ID ... L0158: Erasing device ... L0159: Device blank checking ... L0160: Programming device ... L0161: Verifying device with buffer ... L0162: Verifying device - error! L0164: Verify - error(s) L0166: ADDRESS DEVICE BUFFER L0167: ----------------------- L0168: 0000A588 7FFF FFFF L0170: Elapsed time: 0:00:13.0 L0171: Statistics info: Success:0 Failure:1 Other failure:0 Total:1 L0173: -------------------------------------------------

Dataman (Neil Parker)
Posts: 931
Joined: 10 Nov 2011 09:51

Re: Verification fails on intel flash chip

Postby Dataman (Neil Parker) » 27 Jul 2023 09:07

Hello Davemartin,

The Intel E28F800B5B device is a pretty straightforward FLASH memory device. I would not expect any issues programming it unless there was a problem with the programmers hardware or the device itself was suspect.

Can you run the Selftest... from the programmer menu using the supplied 48pin diagnostic pod and let me know the result? This will perform a thorough test of the programmers internal HW. This of course rests on the programmers 48way ZIF socket being in good condition and giving good contact.

You can try filling the buffer with random data, saving it out to a hex file, programming a device, if verification fails, READ the device into the buffer and save that data out to another hex file and compare the two files using Notepad++ or a similar tool. This may give an insight to where the problem is. Repeating this and getting the same or different results will also tell us something.

Please let me know how you get on.

Best regards,

Neil Parker
Dataman Programmers


Return to “Dataman 48Pro2”

Who is online

Users browsing this forum: No registered users and 13 guests