• Visit https://www.embeddedcomputers.net/ for Hardware; Software and all other things related to FlashcatUSB

FlashcatUSB XPORT -- troubleshooting write issues

McFly1986

New Member
Hi -- I can't seem to write anything using the XPORT. I can erase data, but writing always fails at 0x0. If I turn off "Verify Programming" -- it will proceed to write, but all my attempts have resulted in a 78% match to the original file. Any idea what I may be doing wrong?

Here is the log:
Welcome to the FlashcatUSB interfacing software, build: 643
Copyright 2023 - Embedded Computers LLC
Running on: Windows (64 bit)
FlashcatUSB Script Engine build: 312
Serial NOR memory database loaded: 499 devices supported
Serial NAND database loaded: 66 devices supported
Parallel NOR memory database loaded: 405 devices supported
Parallel NAND memory database loaded: 267 devices supported
OTP/UV EPROM memory database loaded: 46 devices supported
Connected to FlashcatUSB XPORT, firmware version: 5.29
Detecting connected Flash device...
Initializing Parallel NOR device mode
Parallel NOR mode successfully initialized
Attempting to automatically detect Flash device
Mode NOR X16 (Word addressing) returned ident code: 0x01FFAD0000
Mode NOR X16 (Byte addressing) returned ident code: 0x01FF000100
Mode NOR X8 (A0 addressing) returned ident code: 0x0100AD0000
Successfully detected device in NOR X8 (A0 addressing) mode
Connected to Flash (CHIP ID: 0x0100AD0000)
Common Flash Interface information not present
Flash detected: AMD AM29F016B (2,097,152 bytes)
Programming mode: Parallel I/O
Device interface: NOR X8 (5V)
Write mode supported: Standard
Flash device successfully detected and ready for operation
Opened file for writing: Seikendensetsu3_01.sfc, (size: 2,097,152 bytes)
Target Flash address: 0x00000000, bytes to write: 2,097,152 bytes
Address 0x0: wrote 0x4C and read 0x40 (14548 mismatches)
Address 0x0: wrote 0x4C and read 0x40 (14648 mismatches)
Address 0x0: wrote 0x4C and read 0x40 (15186 mismatches)
Data verification failed at 0x0
 
This is a common flash, so I will assume there are no software issues.

Did you try another flash? It is possible that your device is damaged. Is this a desoldered chip? Make sure all the pins are correct/not bent, etc. Even if it detects, a slightly bent pin will result in programming errors.
 
Hi, I have a similar problem but with an AT45DB041E flash, I also use Flashcat XPORT.
When i try to write data it only writes in the first ~64KB. I use the automatic detection and configuration of commands but I don't know what is happening, I already tried with other chips but the exact same thing happens.
Even in the data buffer it does not allow me to go beyond the address 0x100E0

flashcat.png

LOG:
Welcome to the FlashcatUSB interfacing software, build: 643
Copyright 2023 - Embedded Computers LLC
Running on: Windows (64 bit)
FlashcatUSB Script Engine build: 312
Serial NOR memory database loaded: 499 devices supported
Serial NAND database loaded: 66 devices supported
Parallel NOR memory database loaded: 405 devices supported
Parallel NAND memory database loaded: 267 devices supported
OTP/UV EPROM memory database loaded: 46 devices supported
Connected to FlashcatUSB XPORT, firmware version: 5.29
Detecting connected Flash device...
Initializing SPI device mode
Attempting to detect SPI device (auto-detect mode)
Successfully opened device in SPI mode
Connected to SPI Flash (RDID:0x1F2400 REMS:0xFFFF)
Device configured to page size: 256 bytes
Flash detected: Adesto AT45DB041E (524,288 bytes)
Page erase size: 2,048 bytes
Detected SPI Flash on high-speed SPI port
Setting SPI clock to: 8 Mhz
Opened file for writing: Globus PREMIUM 400 Adesto AT45DB041D.bin, (size: 131,072 bytes)
Target Flash address: 0x00000000, bytes to write: 131,072 bytes


Any idea what is happening?
 
Thanks

I have even made sure that I have the memory version with 256 Bytes/Page, assuming that the FLASHCAT is incompatible with the 264 Bytes/Page version, but it is not the case.Memory_name.png
 
I shot a video of a few attempts at writing, showing exactly what I am doing. New flash, right out of the packaging, no bent pins, carefully seated.

Any ideas what's wrong?

 
Thanks for the video. I will try and reproduce the same thing and let you know my results.
 
1676164312495.png

I just tested with exact settings (XPORT 2, TSOP48-C, 5V). Wrote all bytes, and verified the read.

So for your situation, I would either check another chip, and if it is the same, I would check pins on the adapter or the header on XPORT. If you still can not identify the problem, contact EC and arrange to send in your programmer+socket for testing.
 
Hello again, I continue with my problem. I have now tried with a 128K I2C EEPROM (24LC1025) and the error persists, I cannot record beyond 64KB.
I already tried on another computer, also re-installing the driver for my FLASHCAT, recording another data file but the error persists.:(

Even now tried with an I2C EEPROM the data buffer on the screen also does not allow me to see beyond the address 0x10020


Disconnected from FlashcatUSB XPORT device
Connected to FlashcatUSB XPORT, firmware version: 5.29
Detecting connected Flash device...
Initializing I2C EEPROM device mode
Attempting to detect I2C EEPROM device
I2C Address byte: 0xA0
I2C EEPROM device size: 131,072 bytes
I2C protocol speed: 400kHz
I2C EEPROM detected and ready for operation
Opened file for writing: Main.bin, (size: 131,072 bytes)
Target Flash address: 0x00000000, bytes to write: 131,072 bytes
Error communicating with I2C device

flashcat2.png


Is it a problem that my flashcat's firmware is damaged?
 
I am having the same issue as Daniel with an Adesto AT45DB041E flash.

If I uncheck "Verify Programming," I can program all 512KB. If I check "Verify Programming," it fails when it attempts to write to Block 32 (block address starts at 0x010000).

When I try to read the contents back from the chip, I always get 64KB when it is supposed to be a 512KB.

It seems like there's an issue with the read operation at >16bit addresses. Has anyone else ran into this issue?
 
Hello I solved the problem programming two times, the first one with automatic setting and the second one by setting the erase size as DisabledScreenshot (34).pngScreenshot (35).pngScreenshot (36).png
 
Hi Luis, I used the same settings as you and it still won't let me program the memory. I tried with the same version (build 638) and it didn't work either.

This is frustrating, I remember a few months ago doing the same process and everything worked ok, I think the new version of the software affected something in the flashcat firmware. For security, do not update the version.

I wrote directly to Embedded computers and they replied that they would review this situation last week, but they have not notified me yet
 
One comment i don't know if you did, at the moment to do the first programming disable the verify program, and then the second programming using the same settings as the picture but with verify program
 
I did it as you commented, first with the verification deactivated and then activated with manual adjustment.
The error persisted when doing the data check (it only read the first 64KB). But I discovered that if I change the language of the FlashCat from before doing the test, it already allows me to read and write the entire memory.

It can even be seen in the image that with the language changed it already allows me to advance beyond address 0xFFFF in the data buffer

Thnaks Luis

Prog_no.pngPorg_ok.png
 
Back
Top