• Seems like hotmail /outlook is blocking emails from here so please refrain from using one of these accounts as you may not receive your authorization email.. many thanks

Unable to successfully write to AM29F016B or 29F800BA

Kyuruma

New Member
I have a bit of a strange problem that I used to think was human error, but now starting to think is a hardware issue. No matter what I do differently, or how the chips are positioned in the socket, the programmer is unable to write a complete file to any of these chips I've tried. It always fails to verify a specific block or completely flubs it in general if I turn verification off. At first I thought it was an issue with having the wrong pins shorted on the NOR X16 module, but correcting those/using the X8 module (in the case of the AM29F016B) produces the same result still; a 30-40% mismatch count with minor variance in percentages.

For reference this was a voultar bundle which contained the xPort, a TSOP48 NOR x16 module and a TSOP48 NOR x8 module. I'm attempting to right ROM files to both variants of chips that are the correct size, 1024kb and 2048kb respectively. I've tried multiple USB ports on my PC and my board is on the 5.04 firmware.
 

GenjiHarvester

New Member
I seem to be in the same boat writing to AM29F016B. Tried it on two different computers (Win7 and Win10) I always get to the same block at like 6% total progress and verification fails. Everything installed fresh today. Firmware 5.06. So far I've only tried writing the same 2048kb size file.

This is also from the Voultar bundle. I also had trouble with the device finding the memory but it's "not found in flash library." I had to set switch to 5v and only the x8 module works. Cannot get the x16 to work on any setting. Tried multiple chips when troubleshooting all problems.
 

Pantheon

Active Member
Developer
New software version coming out this weekend, will double check these Flash devices.
 

Pantheon

Active Member
Developer
100% Tested and verified: XPORT 2.0 (5.07) BUILD 580

AM29F016B (Switch: 5V, TSOP-48 TYPE-C adapter)
Fuijitsu 29F800BA(Switch: 5V, TSOP-48 TYPE-A adapter, jumpers in default position LEFT)
 

GenjiHarvester

New Member
Thanks Pantheon, I've updated, but unfortunately am still getting the same results. Writing to the chip using the nor x8 fails verification at 6% and the x16 gives the same "flash memory detected but not found in flash library" message. I'm still seeing that "common flash interface information not present" line in the console window for both modules, if that means anything. I'm set to 5V with the other switch in the left APP position (after having updated firmware).
 

lanyap

New Member
Unfortunately, I am in the same boat: the new software version still returns the "flash memory detected but not found in flash library" message.
 

Kyuruma

New Member
I'm having the same issues as well, so gonna attempt to make this post as detailed as possible.


Code:
FlashcatUSB Script Engine build: 302
Welcome to the FlashcatUSB interfacing software, build: 580
LibUsbDotNet version: 2.2.8.104
Running on: Microsoft Windows 10 Pro (64 bit)
Serial NOR memory database loaded: 387 devices supported
Serial NAND database loaded: 35 devices supported
Parallel NOR memory database loaded: 306 devices supported
Parallel NAND memory database loaded: 162 devices supported
OTP/UV EPROM memory database loaded: 16 devices supported
Connected to FlashcatUSB XPORT, firmware version: 5.07
Firmware features supported: SPI, I2C, EXTIO
Initializing EXT I/O hardware board
EXT I/O board successfully initialized
Attempting to automatically detect Flash device
Mode NAND X8 returned ident code: 0x0505050505
Mode NOR X16 (Word addressing) returned ident code: 0x0422580000
Successfully detected device in NOR X16 (Word addressing) mode
Connected to Flash (CHIP ID: 0x0422580000)
Common Flash Interface information not present
Flash detected: Fujitsu MBM29F800BA (1,048,576 bytes)
Programming mode: EXT I/O (Parallel)
Device interface: NOR X16 (5V)
Write mode supported: Standard
Opened file for writing: Final Fantasy IV.smc, (size: 1,048,576 bytes)
Target Flash address: 0x00000000, bytes to write: 1,048,576 bytes
Failed to erase memory at address: 0x00004000
Address 0x4000: wrote 0x20 and read 0x0 (322 mismatches)
Address 0x540C: wrote 0xC9 and read 0xCB (248 mismatches)
Address 0x542A: wrote 0xA and read 0xEA (184 mismatches)
Address 0x54AE: wrote 0x20 and read 0x21 (227 mismatches)
Data verification failed at 0x4000
Address 0x6050: wrote 0x20 and read 0xFF (7518 mismatches)
Address 0x60CC: wrote 0x85 and read 0xFF (7386 mismatches)
Address 0x6098: wrote 0x3D and read 0xFF (7442 mismatches)
Address 0x6082: wrote 0xB0 and read 0xFF (7464 mismatches)
Data verification failed at 0x6000
Address 0xC000: wrote 0x8D and read 0xFF (15145 mismatches)
Address 0xC000: wrote 0x8D and read 0x0 (15145 mismatches)
Address 0xC000: wrote 0x8D and read 0x3 (15145 mismatches)
Address 0xC000: wrote 0x8D and read 0xFF (15145 mismatches)
Data verification failed at 0x8000
Address 0x10000: wrote 0xEA and read 0xC8 (42856 mismatches)
Address 0x10000: wrote 0xEA and read 0xEC (42723 mismatches)
Address 0x10000: wrote 0xEA and read 0xFC (42711 mismatches)
Address 0x10000: wrote 0xEA and read 0xC8 (42711 mismatches)
Data verification failed at 0x10000
Address 0x20000: wrote 0x20 and read 0x0 (40786 mismatches)
Address 0x20000: wrote 0x20 and read 0x0 (40774 mismatches)
Address 0x20000: wrote 0x20 and read 0x0 (40777 mismatches)
Address 0x20000: wrote 0x20 and read 0x0 (40773 mismatches)
Data verification failed at 0x20000
Address 0x30000: wrote 0xC2 and read 0xFF (41997 mismatches)
Address 0x30010: wrote 0x5F and read 0xFF (41972 mismatches)
Address 0x30026: wrote 0x1E and read 0xFF (41804 mismatches)
Address 0x30026: wrote 0x1E and read 0xFF (41925 mismatches)
Data verification failed at 0x30000
Address 0x40000: wrote 0x9F and read 0x0 (34174 mismatches)
Address 0x40000: wrote 0x9F and read 0x0 (34005 mismatches)
Address 0x40000: wrote 0x9F and read 0x0 (38319 mismatches)
Address 0x40000: wrote 0x9F and read 0x0 (38325 mismatches)
Data verification failed at 0x40000
Address 0x50018: wrote 0x0 and read 0xFF (38406 mismatches)
Address 0x5005A: wrote 0x0 and read 0xFF (38207 mismatches)
Address 0x5005A: wrote 0x0 and read 0xFF (38207 mismatches)
Address 0x5006A: wrote 0x3 and read 0xFF (38570 mismatches)
Data verification failed at 0x50000
Address 0x60043: wrote 0x1 and read 0x0 (31288 mismatches)
Address 0x60043: wrote 0x1 and read 0x0 (31425 mismatches)
Address 0x60043: wrote 0x1 and read 0x0 (31570 mismatches)
Address 0x6011A: wrote 0x4C and read 0x48 (32345 mismatches)
Data verification failed at 0x60000
Address 0x7001C: wrote 0xC0 and read 0xFF (34631 mismatches)
Address 0x7006C: wrote 0xC0 and read 0xFF (34554 mismatches)
Address 0x70074: wrote 0xC0 and read 0xFF (34544 mismatches)
Address 0x70080: wrote 0x2 and read 0xFF (34528 mismatches)
Data verification failed at 0x70000
Address 0x80042: wrote 0xA7 and read 0x24 (40370 mismatches)
Address 0x80042: wrote 0xA7 and read 0x24 (40354 mismatches)
Address 0x80042: wrote 0xA7 and read 0x24 (40364 mismatches)
Address 0x80042: wrote 0xA7 and read 0x24 (40350 mismatches)
Data verification failed at 0x80000
Address 0x90000: wrote 0x0 and read 0xF0 (40966 mismatches)
Address 0x9000C: wrote 0x17 and read 0xF2 (40930 mismatches)
Address 0x9000C: wrote 0x17 and read 0x92 (40961 mismatches)
Address 0x90014: wrote 0x55 and read 0x0 (40914 mismatches)
Data verification failed at 0x90000
Address 0xA0000: wrote 0x24 and read 0x0 (33538 mismatches)
Address 0xA0000: wrote 0x24 and read 0x0 (39290 mismatches)
Address 0xA0000: wrote 0x24 and read 0x0 (39746 mismatches)
Address 0xA0000: wrote 0x24 and read 0x0 (39729 mismatches)
Data verification failed at 0xA0000
Address 0xB0000: wrote 0x0 and read 0xFF (40413 mismatches)
Address 0xB003A: wrote 0xF5 and read 0xFF (40467 mismatches)
Address 0xB003C: wrote 0x1B and read 0xFF (40463 mismatches)
Address 0xB0044: wrote 0xD5 and read 0xFF (40338 mismatches)
Data verification failed at 0xB0000
Address 0xC0001: wrote 0xC and read 0x4 (37728 mismatches)
Address 0xC0001: wrote 0xC and read 0x4 (37333 mismatches)
Address 0xC0001: wrote 0xC and read 0x4 (37595 mismatches)
Address 0xC0001: wrote 0xC and read 0x4 (37444 mismatches)
Data verification failed at 0xC0000
Address 0xD001A: wrote 0x13 and read 0xFF (35449 mismatches)
Address 0xD005C: wrote 0x17 and read 0xFF (35346 mismatches)
Address 0xD006F: wrote 0x6E and read 0xFF (35254 mismatches)
Address 0xD006F: wrote 0x6E and read 0xFF (35272 mismatches)
Data verification failed at 0xD0000
Address 0xE0000: wrote 0x38 and read 0x0 (32467 mismatches)
Address 0xE0000: wrote 0x38 and read 0x0 (32465 mismatches)
Address 0xE0000: wrote 0x38 and read 0x0 (33265 mismatches)
Address 0xE0000: wrote 0x38 and read 0x0 (32501 mismatches)
Data verification failed at 0xE0000
Address 0xF003A: wrote 0xFF and read 0x40 (32954 mismatches)
Address 0xF0018: wrote 0xA8 and read 0x0 (33095 mismatches)
Address 0xF003A: wrote 0xFF and read 0x40 (33032 mismatches)
Address 0xF0018: wrote 0xA8 and read 0x0 (33097 mismatches)
Data verification failed at 0xF0000
Write operation complete, 1,048,576 bytes written
1,048,576 bytes written in 146.224 seconds, 7,171 Bytes/s
Beginning memory compare operation
Filename: Final Fantasy IV.smc
Flash address: 0x00000000, size: 1,048,576 bytes
Address 0x0: wrote 0x78 and read 0x20 (16190 mismatches)
Address 0x4000: wrote 0x20 and read 0xFF (8157 mismatches)
Address 0x6082: wrote 0xB0 and read 0xFF (7464 mismatches)
Address 0xC000: wrote 0x8D and read 0xFF (15145 mismatches)
Address 0x10000: wrote 0xEA and read 0xFF (42719 mismatches)
Address 0x20000: wrote 0x20 and read 0x0 (41740 mismatches)
Address 0x30000: wrote 0xC2 and read 0x43 (34064 mismatches)
Address 0x40000: wrote 0x9F and read 0x0 (32939 mismatches)
Address 0x50000: wrote 0x0 and read 0x3 (34706 mismatches)
Address 0x6011A: wrote 0x4C and read 0x48 (31156 mismatches)
Address 0x70000: wrote 0x2 and read 0xFF (36809 mismatches)
Address 0x80042: wrote 0xA7 and read 0x24 (39718 mismatches)
Address 0x90002: wrote 0x0 and read 0x2D (38429 mismatches)
Address 0xA0000: wrote 0x24 and read 0x0 (33099 mismatches)
Address 0xB0001: wrote 0x0 and read 0x3 (36882 mismatches)
Address 0xC0001: wrote 0xC and read 0x4 (33286 mismatches)
Address 0xD0000: wrote 0x0 and read 0x5 (38662 mismatches)
Address 0xE0000: wrote 0x38 and read 0x0 (32202 mismatches)
Address 0xF0001: wrote 0xDC and read 0xFF (37675 mismatches)
Memory compare complete: 591042 total mismatches (43.6% match)

It basically does the same thing for the x8 module, though with that one matching is usually 31% accurate. I've also attached the file I'm writing if that helps diagnose anything (zipped up of course), really starting to think I just got a bad batch of the hardware or something though.
 

Attachments

Pantheon

Active Member
Developer
So I tested the above chip, with 100% success rate, using the current firmware/software. So if there is a problem, you need to send in your unit/socket/chip, and I will be able to tell you which of those three is not working.
 

Kyuruma

New Member
So I tested the above chip, with 100% success rate, using the current firmware/software. So if there is a problem, you need to send in your unit/socket/chip, and I will be able to tell you which of those three is not working.
Alright, what address do I need to ship to? If it's available somewhere I can't find it
 

GenjiHarvester

New Member
So, I acquired a different run of the AM29F016B from a different vendor and writing fails in the exact same way. Considering that one of the two adapters doesn't work at all and the similar issues others are having with the product attempting to write to both chips, I think an exchange for a device confirmed to be working would be the way to go. Could I be messaged a return address or should I reach out via e-mail? Please advise.
 
Top