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

Getting Flashcat to recongnize a PFL064PIF

D

damic

New Member
So I'm new to using a Flashcat but I can't seem to get mine to detect it being connect to a Spansion PFL064PIF. I have it connected via some wires and test clips, I tested the ground and VCC and detected I was getting a 3.3v signal.

RGHX3.jpg


I tried to unplug and plug back in the Flashcat. I've also attempted with the DIP switches (1 and 2, not the power settings) set in all different settings. Non have produce the detection of the chip.

What am I missing?
 
Never heard of a Spansion PFL064PIF are you sure it is not a Spansion S25FL064 ??
Do you have the chip connected out of situe or is it still connected to a board ?

Also what does your software output say on status and console windows ?
 
D3m0n said:
Never heard of a Spansion PFL064PIF are you sure it is not a Spansion S25FL064 ??
Do you have the chip connected out of situe or is it still connected to a board ?

Also what does your software output say on status and console windows ?
Click to expand...

I don't have anything that will take a clear enough picture of the chip but what I could read off it was this:

--snip text on chip--
"Spansion logo"
FL064PIF
42200026A
©08 SPANSION
--end--

Not sure what that makes it. Below is the output of the console messages.

iZfgs.jpg


The chip is on a board.
 
I didn't want to side track the thread but a couple of things I was wanting to try was changing the image on the Flashcat but I don't see how I would use the images in the "firmware" directory via the software nor is there any documentation on how to do this.

Another thing I noticed in the console output is that it says its running SPI firmware version 3.06 but only the 3.05 image is provided in the download.

The console is also incorrect in providing Windows OS info running in 32-bit mode, it should be 64-bit.
 
SPI firmware 3.06 is the newest firmware for PCB 2.0 boards. All of the firmware in the current RC package is for PCB 1.x.

The console will always report 32 bit on a 64 bit os, because the exe is compiled for 32 bit (to make it more compatible).

Also, from your picture, you are connecting SI to SI and SO to SO on the chip? Aren't you suppose to connect SI to SO and SO to SI?
 
Pantheon said:
SPI firmware 3.06 is the newest firmware for PCB 2.0 boards. All of the firmware in the current RC package is for PCB 1.x.

Also, from your picture, you are connecting SI to SI and SO to SO on the chip? Aren't you suppose to connect SI to SO and SO to SI?
Click to expand...

I see, are separate firmwares needed on the PCB 2.0 boards or does the extra space on chip allow for only one version now?

Indeed I'm connecting SI to SI and SO to SO, although I have tried swapping them to make sure that wasn't the issue as I saw in a different post. In either configuration I get "Unable to connect to compatible SPI device"
 
Pantheon is correct your SI should be connected to your SO

SPI_Connection_ISP.jpg

Are you soldered onto the chip or using a clip ? If you are usinf a clip try to solder as the clips are unreliable and make sure your connection wires from FCUSB to the chip are not long.
 
Actually, show me a picture of your connection between the FCUSB and the chip. I am curious to see this device.
 
Is it not possable for you to solder to the chip and also shorten the length of the cable you are using ?
 
It is possible, I was just trying to avoid soldering. What signal would have a problem with cable length? Power is 3.1v at the chip.
 
You have to maintain solid connection points to all pins , the longer the cables the more chance of problems , your cables may not be that long but it is hard to tell from the photo . You may be getting the correct Voltage going to the board on the VCC , but the other pins 1,3 & 5 also have voltage going through them , so these all need to be checked.
 
D3m0n said:
You have to maintain solid connection points to all pins , the longer the cables the more chance of problems , your cables may not be that long but it is hard to tell from the photo . You may be getting the correct Voltage going to the board on the VCC , but the other pins 1,3 & 5 also have voltage going through them , so these all need to be checked.
Click to expand...

I assume that you are talking about the pins on the chip? Here are the readout of the voltages read at the pins of the chip (PLF064PIF) with only the Flashcat connected to the chip as shown in the picture from previous posts in this thread.

hfGu6.jpg


The majority of the cable lengths are 25cm + the clip 6cm + 2cm header. The cable for the VCC line is 20cm + the clip 6cm and is one that shipped with the Flashcat unit.
 
The cable is a little long but you seem to be getting the correct voltages to the chip ..??
The only way i can be 100% sure that your cable is not causing an issue is by using shorter lengths and soldering direct to the chip .
Saying that at times i have had issues getting a detection unless i have let the device fully boot then powered it down and then tried.
Normally best way of R/W to these chips is if they were off the board or if you knew where the ISP point was off the device.
 
Ok, I have identified the ISP point on the board although I'm not sure what it is or how to use it. Can you point me to some info or what I should try next with regards to the ISP point?
 
Ok if you have the ISP point connect the VCC from FCUSB to it , and then power up the modem itself and try to detect , if the ISP point is correct , your modem will not boot up as normal but will seem to be in a stuck mode
 
The pin on this chip is too small to connect with my EZ-clips.

How would this help in detecting the chip with the FlashcatUSB program? Also I'm not sure about the correct settings I should be using. I've been playing around with changing the settings.

RF24LE1 SPI mode gets some sort of detection but not the flash chip as it is 64Mb and it detects 16k in that mode with blank data "FF FF".

What are the dip switches used for on the Flashcat too, should these be set in any manner that would help in the detection of the chip?
 
The ISP pin is an alternate way of detecting the chip as it halts the CPU making it easier for a detection ...
The nRF24LE is a totally different chip , so there is no point in trying to use that for your detection.
The dip switches are just for setting the bootloader mode to flash the different firmwares onto the FCUSB more so on the old 1.x versions.

If on the one end of your wire from the VCC of FCUSB you have a small pin just to touch the ISP pin this should be enough for you to hold it in place to get your detection and do your programming , although you have to be 100% sure this is the correct point or you could damage either of your devices.
 
So I still haven't given up on this but I had to get a different device because my first attempt at soldering wires to it seems to have damaged the device. Could have been from getting device too hot/bad solder point. Second attempt I tested the device after each solider point. The device works however the Blackcat still does not read the chip.

My connection:

mY8Wd.jpg


The next step looks like to solder VCC/TCK from the Blackcat to the ISP point correct?

I want to confirm this before I solder the VCC to the ISP point. I see that people using the JTAGUSBNT use TSRT to the ISP point which on the Blackcat seams to be CS/TRST or possible RST/GND.

Thanks for pointers.
 
You must log in or register to reply here.
Back
Top