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

MX25L8005

jpr233

New Member
Hello,

Got a fresh PCB 2.1 v371 to flash an MXic MX25L8005 . But chip is not in SPI db.

Complete chip spec here : http://www.macronix.com/en-us/Product/Pages/ProductDetail.aspx?PartNo=MX25L8005

fcusb log is :
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 225
SPI database loaded: 226 devices supported
Welcome to FlashcatUSB interfacing software, build: 371
Running on: Microsoft Windows 10 Professionnel (64 bit)
Device connected in SPI mode, firmware version: 4,06
Successfully opened device in SPI mode (8 MHz)
Connected to Flash (RDID:0xFFFFFF REMS:0xFFFF)
For read write support email contact@embeddedcomputers.net with RDID/REMS


RDID should be : C2 2014 and REMS should be C2 13 (see page 16 datasheet).
FCUSB is set to 3,3v (normal range for that chip).
Chip' 8-PIN PDIPD (300mil) is same as FCUSB diagram for a typical SOIC-8 and DIP-8 package of a SPI compatible Flash device.
Chip is connected thru 3M SOIC clip.

Any chance to get my "Blackcat USB SPI I2C JTAG Flash Programmer SPANSION MXIC Winbond Microchip ATMEL" work with my chip ?
Thx
polo
 
Hello,

Got a fresh PCB 2.1 v371 to flash an MXic MX25L8005 . But chip is not in SPI db.

Complete chip spec here : http://www.macronix.com/en-us/Product/Pages/ProductDetail.aspx?PartNo=MX25L8005

fcusb log is :
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 225
SPI database loaded: 226 devices supported
Welcome to FlashcatUSB interfacing software, build: 371
Running on: Microsoft Windows 10 Professionnel (64 bit)
Device connected in SPI mode, firmware version: 4,06
Successfully opened device in SPI mode (8 MHz)
Connected to Flash (RDID:0xFFFFFF REMS:0xFFFF)
For read write support email contact@embeddedcomputers.net with RDID/REMS


RDID should be : C2 2014 and REMS should be C2 13 (see page 16 datasheet).
FCUSB is set to 3,3v (normal range for that chip).
Chip' 8-PIN PDIPD (300mil) is same as FCUSB diagram for a typical SOIC-8 and DIP-8 package of a SPI compatible Flash device.
Chip is connected thru 3M SOIC clip.

Any chance to get my "Blackcat USB SPI I2C JTAG Flash Programmer SPANSION MXIC Winbond Microchip ATMEL" work with my chip ?
Thx
polo


PS: I have 3,28v on both :
a) chip strapped 7-8 vcc / 4 gnd pins, and
b) FCUSB Vcc / Gnd on the I/O port.

PPS: Note that I have never flashed FCUSB board in DFU mode (like FCUSB.RC19.370 SPI fw) as doc stated FlashcatUSB is shipped with the latest SPI firmware installed
Also I got RDID and REMS readings with another SOC-8 (TVbox EON 1C 5114 found)
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 225
SPI database loaded: 226 devices supported
Welcome to FlashcatUSB interfacing software, build: 371
Running on: Microsoft Windows 10 Professionnel (64 bit)
Device connected in SPI mode, firmware version: 4,06
Successfully opened device in SPI mode (8 MHz)
Connected to Flash (RDID:0x1C5114 REMS:0x1C13)
For read write support email contact@embeddedcomputers.net with RDID/REMS

so i think everything is right with FCUSB ?

FYI : I need these for a MSI Wind100 (built in the 2008's), without Jdp1 header soldered on the mobo. I did a bad flash with new 10G MSI bios, and now fan run 2 sec at power on button, and then everything stops & remains dark and down.
Of course I made a read backup save of the rom before that flash, but I found no way to start the AMI recovery process (neither usb dongle led access lighting nor usb floppy access with any rcvy processes amiboot.rom or biosname and rcvy protocol on the netbook unplug all, plug AC, hold while etc...).
So I need to reflash the SPI eeprom with previously backuped rom for the netbook revival.
 
Last edited:
Well, me again.

I put SPI settings accordly MX25L8005 datasheet :
SPI data set accordingly MX25L8005 datasheet.png

then did a renew detect device for a full reading.
All i got is a FF's values on screen and on saved file.....

log:
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 225
SPI database loaded: 226 devices supported
Welcome to FlashcatUSB interfacing software, build: 371
Running on: Microsoft Windows 10 Professionnel (64 bit)
Device connected in SPI mode, firmware version: 4,06
Successfully opened device in SPI mode (8 MHz)
Connected to Flash (RDID:0xFFFFFF REMS:0xFFFF)
For read write support email contact@embeddedcomputers.net with RDID/REMS
SPI addressing mode set to 24-bit
SPI addressing mode set to 24-bit
SPI addressing mode set to 24-bit
Device connected in SPI mode, firmware version: 4,06
Checking for a device specific script to automatically load
No script files available
Beginning memory read from SPI Flash
Start address: 0 (0x00) Length: 8?388?608
Read operation complete
Read 8.388.608 bytes in 20,525 seconds, 408.722 Bytes/s

..

While ROM bios is 1Mbyte, chip is 8Mbytes for that full reading, and i was supposed to get somewhere some ROM data.... WTF ????

Please, any help ?
polo
 
Well Well,...

Surprising! My chip should have been recognized within flashDB, as source code for 345 contains in SPI.vb its own entry :
FlashDB.Add(New SpiDevice("MXIC MX25L80", MB008, &HC2, &H2014)) !!

I suspect a very big bug in the way the reading are done, and perhaps also writes ...
Seen same kind of problem ugubudu had, with MX25L6406E on 6-16,2015, with FCUSB.RC16.345 and PCB 1.8 (problem left unsolved)...

In hope that developer and D3m0n can have a look soon to diagnose ...

If not, then i will send back FCUSB to Redmond and get another programmer (as EZP2012 that will do the job)... Before that, a great hope that bug tracking can make this Blackcat even better for MXic (if not many others chips...) in 2016
polo
 
That particular flash is in the most recent database , u can check this using the command "SPI.Database(true)" in the console window , i would re-check your connections to this particular chip.
This is why even when you try to manually insert the SPI settings it fails as well as it is not seeing the chip correctly.
 
Hi,

Thx for reading.
Embedded Computers aleady emailed me same answer.

I did rebuild again all connections from flash chip <>clip <>I/O port. But same results as previous.

After my EON chip witch was recognized (while but not in DB), it's now another chip = AMIC A25L080 (in HP G6-1000) that is not recognized while "37 3014" is found in 365' spi.vb....

Funny thing is that v365 runs have given different 'garbage' ID each time i start that version (while 330, 370 & 371 find no flash at all, as for my MXic chip).

So, with 3 different IOP8 chips, 3 unexpected results...

And just now, in a tenth try, 365 give me erroneous AMIC as an Amtel chip :
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 211
SPI database loaded: 202 devices supported
Welcome to FlashcatUSB interfacing software, build: 365
Running on: Microsoft Windows 10 Professionnel (32 bit)
Device connected in SPI mode, firmware version: 4,06
Opening device in SPI Mode 4 (Fosc/2 MSB)
Connected to Flash (RDID:0x000000 REMS:0x8000)
Flash detected: Atmel AT25010A (128 bytes)
Programming mode: SPI (high-speed)
Checking for a device specific script to automatically load
Loading device specific script: default.bcs
Loading script: default.bcs


Well, I simply think my board can be a deffective one...

Do I have to redo the flash with fw packed in the 370'zip ? I never did DFU mode before ?
Can it be a W10 1511 x64 possible problem alreday reported ?

PS : I just reflashed 4.06 SPI in DFU mode.
I never tried before, as junctions were done, but with an EMTPY I/O port on PCB2.1 (set to be quiet in reflash fw) now v371 tells me "Successfully opened device in SPI mode (8 MHz)" (see below) = what does it mean ????
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 225
SPI database loaded: 226 devices supported
Welcome to FlashcatUSB interfacing software, build: 371
Running on: Microsoft Windows 10 Professionnel (64 bit)
Device connected in SPI mode, firmware version: 4,06
Successfully opened device in SPI mode (8 MHz)
Connected to Flash (RDID:0xFFFFFF REMS:0xFFFF)
For read write support email contact@embeddedcomputers.net with RDID/REMS

==> WTF???? HOW ???

Cheers,
Thx
polo
 
Last edited:
Hello again

I'am tired about lack of success with FlashCat programmer.

Last, I build a Win7 config x86 to try that BlackCat device.

Installing v370 drivers in Win7 then launching FCUSB v371 progy gives :

1) language is default Spanish (i got that too my very first time; FYI my system parameters is France/French, so it's quite funny),

2) with the device usb connected with its red light on ==WHILE NOTHING WIRED on its I/O Port==, nevermind : BLUE LIGHT goes also ON !
Then RDID = FF FFFF and REMS = FFFF and "FlashCatUSB detected SPI device but its not currently supported" on the below status bar.

So I can go on : take default or set SPI value, then do a read ... and get a galaxy of FFFF ....FFFF.

Very nice work, isn't it ? Without chip on line, everything works... same as with a real one plugged !

If it's a joke with PCB 2.1 + fw 4.06 + V371, it's a very very bad one.

I wasted enough time with that fake programmer and am ready to give up any more testing or diagnozing.

By now, no more than 4 MB chips failed und 2 OSes unsuccessfully tried.

Without any explanation about all these tremendous results (IT comprehesive reply, not "it's already supposed to work" --I add "even without chip"),
I should know what to do with Paypal.

And you guys who think that programmer could do the job, you have been warned.

polo, a frustrated customer
 
Look here ,,, i have tried different chips that i have lying around here with the v2.1 programmer i have and they all work on win 10 x64 ... When i start my programmer the red led comes on that is normal , the blue does also come on once you start the software.
Why your software starts in spanish is beyond me as mine does not and never has.

And before you go on about warning me , i have fuckall do to do with development and selling of this product. I started this forum to try and help people of my own back , now i do also have a life and cannot be expected to be here at your beck and call 24/7

Try not using the clip as they are shit , solder to the legs if u can u are guaranteed a better connection.
 
Back
Top