• 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

Need MX25L8005M2C added to SPI

Francisco

New Member
I can't seem to get this chip recognized by Blackcat USB... Three console logs follow and datasheet is attached.

using script engine build#110 & interface software build #260
LOG1:
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 110
Welcome to Blackcat USB interfacing software, build: 260
Running on: Microsoft Windows 7 Ultimate (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash JEDEC found: 0 0000
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash JEDEC found: 0 0000
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash JEDEC found: 0 0000
For read write support email contact@embeddedcomputers.net with JEDEC ID

using script engine build#150 & interface software build #266
LOG2:
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 150
Welcome to Blackcat USB interfacing software, build: 266
Running on: Microsoft Windows 7 Ultimate (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash JEDEC found: 00 0000
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash JEDEC found: 00 0000
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash JEDEC found: 00 0000
For read write support email contact@embeddedcomputers.net with JEDEC ID

Starting BlackcatUSB.exe without usb cable connected displays SPI Settings tab...
and allows manual configuration of device but still doesn't read and/or write correctly.
using script engine build#150 & interface software build #266
LOG3:
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 150
Welcome to Blackcat USB interfacing software, build: 266
Running on: Microsoft Windows 7 Ultimate (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash JEDEC found: 00 0000
Using custom settings from SPI Settings page
Flash detected: SPI_SPECIFIC (131072 bytes)
Programming mode: SPI (high-speed)
Disconnected from BlackcatUSB
SPI mode set to 3
SPI clock mode set to Fosc/64 (250 KHz)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 3 (Fosc/64 MSB)
Flash JEDEC found: 00 0000
Using custom settings from SPI Settings page
Flash detected: SPI_SPECIFIC (1048576 bytes)
Programming mode: SPI (high-speed)
Address 0x0: wrote 0xFF and read 0x0 (32650 mismatches)
Address 0x0: wrote 0xFF and read 0x0 (32650 mismatches)
Address 0x0: wrote 0xFF and read 0x0 (32650 mismatches)
Error: data verification at 0x0 failed!
Address 0x8000: wrote 0x3C and read 0x0 (32647 mismatches)
Address 0x8000: wrote 0x3C and read 0x0 (32647 mismatches)
Address 0x8000: wrote 0x3C and read 0x0 (32647 mismatches)
Error: data verification at 0x8000 failed!
Address 0x10000: wrote 0xFB and read 0x0 (32659 mismatches)
Address 0x10000: wrote 0xFB and read 0x0 (32659 mismatches)
Address 0x10000: wrote 0xFB and read 0x0 (32659 mismatches)
Error: data verification at 0x10000 failed!
Address 0x18000: wrote 0x45 and read 0x0 (32591 mismatches)
Address 0x18000: wrote 0x45 and read 0x0 (32591 mismatches)
Address 0x18000: wrote 0x45 and read 0x0 (32591 mismatches)
Error: data verification at 0x18000 failed!
Address 0x20000: wrote 0x71 and read 0x0 (32654 mismatches)
Address 0x20000: wrote 0x71 and read 0x0 (32654 mismatches)
Address 0x20000: wrote 0x71 and read 0x0 (32654 mismatches)
Error: data verification at 0x20000 failed!

Please help
 

Attachments

D3m0n

Administrator
Staff member
What settings did you input on the SPI settings tab ?? On the previous builds it did not seem to be picking up the JEDEC ID , also using the new build266 it did not either. All you are using is specific settings but it is still not seeing the SPI flash , you need to get the device to see the Jedec ID before you can actually read/write to the device.

You will be looking for a JEDEC ID similar to this : C2 2014 .

Are you connecting to the chip via an ISP method or have you removed the chip and connected directly to it ? Also what voltage are you connecting to the chip with , i have found that i require it to be on the 3.3v setting for MX chips via ISP method .
 

Francisco

New Member
Normally use these settings as automatic doesn't ID device:

SPI device commands
- - - - - - - - - - - - - -
Chip Size 0x100000 Page Program 0x02 Read 0x030 SPI Mode Mode 0
Erase Size 0x8000 Write Enable 0x06 Sector Erase 0x52 Clock Divider 2 (8 MHz)
Write Status 0x01 Read Status 0x05 Chip Erase 0x60 Bit Order MSB
if my math is right... 8,388,608 bits equals 1,048,576 bytes equals 100000 Hex
unsure of Erase Size... Sector Erase code 0x52 is really Block Erase on device should be 0x20... all other codes appears to be correct.

Connected via ISP (In-System Programming)... Blackcat USB jumper across 3.3v pins... BCUSB pcb 1.8

Pics and diagrams to follow
 

D3m0n

Administrator
Staff member
Are you 100% sure you have the correct ISP point ? I was talking to the developer regarding this , and he reckons as it is a very old chip 1mbit , that there is a possability that you may not get a connection , and that he will have to write a custom function into the software for it to be supported , but he needs to be sure that it is indeed not getting a connection , hence the reason i ask if that is the true ISP point.
 

Francisco

New Member
Is this device not an 8Mbit chip???

MX25L8005M2C-15G
8M-BIT [x 1] CMOS SERIAL FLASH
• Serial Peripheral Interface (SPI) compatible -- Mode 0 and Mode 3
• 8,388,608 x 1 bit structure
• 256 Equal Sectors with 4K byte each
- Any Sector can be erased individually
• 16 Equal Blocks with 64K byte each
- Any Block can be erased individually
• Single Power Supply Operation
- 2.7 to 3.6 volt for read, erase, and program operations
• Latch-up protected to 100mA from -1V to Vcc +1V
• Low Vcc write inhibit is from 1.5V to 2.5V

MX 25 L 8005 M2 C - 15 G
25: Serial Flash
L: 3V
8005: 8Mbit
M2: 200mil 8-SOP
C: Commercial (0°C to 70°C)
15: 70MHz
G: Pb-free

I must not understand what is meant by true ISP point... maybe you can help me with that???

Attached is SPI header pin-outs from manufacturer docs... also attached is picture of MX25L8005 and SPI header... additionally, this flash device is in a HP p6130y with a Asus/Pegatron M2N78-LA v3.02 motherboard aka HP Violet-GL8E

SPI header pin-outs have been ohm'ed / continuity checked to flash device leads...
pin-out GND to device lead #4
3VSB to lead #8
right side SPI CS# to lead #1
SPI CLK to lead #6
SPI MISO to lead #2
SPI MOSI to lead #5
left side SPI CS# ohms out at about 9 to 12 Meg ohms to all device leads... when computer is in normal working condition a jumper is placed across both SPI CS# pins

Using 6 individual 12" jumper leads from Blackcat USB header to M/B SPI header and using supplied 36" USB cable from Blackcat to working computer
 

Francisco

New Member
Slightly off topic... I found plain text list of various supported? flash devices in manufacturers BIOS file

ESMT 25L008A, ST M25PE80, SPANSION 25FL008A, PMC 25LV080, MXIC 25L8005, EON 25P/F80, AMIC A25L080, INTEL 160S33B, WINBOND W25X80, SST 25VF080B, ESMT F25L08
 

Francisco

New Member
OK... won't load the images???

I will try to type an approximation of the SPI header below;

_ SPI_CS# * * SPI_CS#
SPI_MOSI *
SPI_MISO * * 3VSB
_ SPI_CLK * * GND

header pin GND ohms to device(MX25L8005) lead #4
3VSB to lead #8
right side SPI_CS# to lead #1
SPI_CLK to lead #6
SPI_MISO to lead #2
SPI_MOSI to lead #5
left side SPI_CS# pin to any lead on device ohms at about 9 - 12 Megohms

Again when computer is operating normally, a jumper bridges the two SPI_CS# pins
 

D3m0n

Administrator
Staff member
Try uploading the images now , had some permission errors wrongly set.

It will be a lot better to understand with the images. Basically to find the true ISP point means stopping the cpu from booting thus allowing you full access to the chip. now becasue this is a pc motherboard , finding the ISP pin may be harder than expected , there is an alternative way by exteranlly adding 3.3 -5v to the actual spi chip itself pin8 ( with NO POWER to the motherboard ) and see if that offers you a JEDEC ID or gives you a reading.

Apologies it is a 8M spi flash , typo on my part.
 

Francisco

New Member
Power supply, HDD, DVD-RW, fans and all headers have been disconnected from M/B... only thing left in place is CPU... The previous attempts were done like this with no power to motherboard, only 3.3V applied to 3VSB pin on SPI header
 

D3m0n

Administrator
Staff member
This is from the developer :

I would say its not connected correctly.

Remember, there is no "ISP" pin, that is a board specific feature that changes the attached state of the flash device (so the clock from the board does not interfere with the clock from our programmer.

Now I bet that header has two CE pins for a reason. One CE is from the main board, the second CE is to the chip. So with a jumper the board can use the SPI chip, and without a jumper and BCUSB connected to the one CE pin that goes to the chip, BC can use the flash.

So ask him if he has both CE pins connected, and if he does, that is the problem.
 

Francisco

New Member
Previous attempts done with jumper removed and Blackcat connected to only the SPI_CS# pin that shows continuity to device lead #1
 

D3m0n

Administrator
Staff member
So i am assuming with no jumper connected you still receive the Flash JEDEC found: 00 0000 in console correct ?

Is there a possability you have the option to remove the SPI chip and connect directly that way? I am asking this purely for the sole reason of trying to eliminate any issues with it being In Situe.
 

Francisco

New Member
No jumper in place when I attempt to use the Blackcat... only connection is to Blackcat and finds JEDEC 00 0000. Can't remove device without risking further damage to motherboard... Device is surface mounted and soldered to board.
 

D3m0n

Administrator
Staff member
Only other thing i can suggest is by trying to inject 5v itself onto the chip and see if you get a connection that way. There are a few devices i have that do not get detected by bcusb and unfortunately , like yourself i am awaiting answers from the develop regarding these.
 

Francisco

New Member
The computer I am using right now has a very similar motherboard... socket AM3 instead of AM2+... has same SPI header... I can load Blackcat on laptop and try to read this M/B to verify if it works and the other flash chip is gone or there is other problems work out.
 

D3m0n

Administrator
Staff member
Sounds like it is worth a try , let us know how it goes.
 

Francisco

New Member
OK... same result with other computer. Removed all components from m/b, removed jumper on SPI header... connected Blackcat USB... got JEDEC ID #00 0000. This device appears to be SST 25VF080B with date code 0944

Must require more than connecting SPI interface to the onboard header
 

D3m0n

Administrator
Staff member
It is interesting that bcusb does to a certain extent , see the m/board as it throws out the JEDEC ID #00 0000 .
Only option i can offer at this moment in time is to connect directly to the chip ( solder or clip) and apply the extra 3.3 -5v onto the vcc pin to see if you get a similar detection
 
Top