• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
  • 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

11 Pin MSI JSPI1 port need additional VCC connection the WP# pin??

#1
What does that mean:
The only difference is with the 11-pin version you will need to connect an additional
VCC connection to the WP# pin

Got a few MSI motherboards and I want to test being able to read the flash chip through the JSPI1 port but confused about how to layout
the jumper cables?

Thanks
 
#2
These are my logs after unsuccessfully trying to get it to work over the JSPI1 port:

Going to return this device.

FlashcatUSB Script Engine build: 300
Welcome to FlashcatUSB interfacing software, build: 482
LibUsbDotNet version: 2.2.8.104
Running on: Microsoft Windows 10 Pro (64 bit)
NAND memory (x8/SLC) database loaded: 69 devices supported
NOR memory (x8/x16) database loaded: 190 devices supported
SPI memory database loaded: 315 devices supported
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Connected to FlashcatUSB Classic, firmware version: 4.29
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect SPI device (auto-detect mode)
Unable to connect to compatible SPI device
Successfully opened device in SQI mode
Connected to Flash (RDID:0x333333)
For read write support email contact@embeddedcomputers.net with the CHIP ID
Disconnected from FlashcatUSB device
 
#4
As I have a 11 pin JSPI1 - I followed the manual routing CS to CS, SO to SI, SI to SO, CLK to SCLK, GND to GND, VCC to VCC like this illustration:

msi11.png flashcat.png

I even tried to route WP# to the second VCC (Not sure if below illustration is correct) on the Flashcat.
The schematics of the Flashcat say the 2nd and 3rd top pins on left row are SIO2 and SIO3 but I tried
with and without routing it that way.

I also tried routing the wires this way ignoring the top two pins of the 11 pin JSPI1. I also tried routing the WP# to the
2nd pin on the left side detailed as VCC in the below illustration.



blackcat.png

Though my MSI boards have 11 Pin configurations such that above illustration ignored the top two pins

Not sure whats going on here. If anyone can help I would appreciate though not life or death as I was just
testing things out to see if it would work just in case of an emergency.

Thanks
 
#6
Its an B85M Gaming board.

I should note the only thing I did not try was splitting the 1st VCC pin in two and running it to WP#.

Is that even necessary?
 
#8
why don't you buy a soic8-clip and connect it directly to the chip? It should work that way. I'm waitung for my clip to arrive and test it on my msi board (with 9 pins though)
 
#9
No I tried it with a Soic8 clip and couldn't get it to work on that board and an older one I bricked last month.
However was able to use the clip with a CH341A Black usb stick no problem and rescue the machine back from death.

Anyhow for testing purposes I could not get the Blackcat USB programmer to identify the flash. Ordered a JSPi1 adapter
from Alibaba and should have it soon. Curious if that will work or recognize my MSI based boards.

Hope I didn't waste $40 bucks on this Blackcat. Only reason I got it was because of the 3.3 voltage selector where as they
say the CH341A black overvolts. FWIW over volt or not it saved the day.
 
#10
Well, I also had problems with blackcatusb (v1.8) and my msi. However after several trial-and-errors I managed somehow to reflash the board. The problem back then was the voltage. I could read the chip via the jspi1 header but the voltage ov BC was not enough for writing. My solution back then was powering up the board through the on-board button and .... luckily I had enough time before restarting for the new bios to be written on the chip. That was my experience in 2013. Haven't tried it since then.

Now I've ordered a soic8 clip and will give it a try when it arrives. My boards is v1.8 though. I'll see how high the voltage goes when connected.