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

s25fl256 and s25fl128 writing error

johan2

New Member
s25fl256 and s25fl128 writing error

hi sir i can already read and write s25fl032 and s25fl064

but when i am work on s25fl256 and s25fl128

then i can only read, not write operation

only led blinking

not effect on flash data

please help me why i am can not write operation

CONNECTION is FLASH S25FL128 AND S25FL256
FLASH TYPE 24-Ball BGA, 4 x 6 Ball Footprint

flash black cat

hold and vcc connect VCC
SO SI
SI SO
CS CS
VSS GND
SCLK SCLK



http://www.spansion.com/Support/Datasheets/S25FL128S_256S_00.pdf
 
Are you using Build 330 ? if so try an older build from 320 up and see if you can read /write with that
 
Try an older version either 320 or 326 and see if u have the same issue
 
sir i am use 320,326,330 same problem
and my flash ic is s25fl128s

but these show s25fl128p1.GIF 2.JPG
reading accurate data but
3.JPG
after write operation these show


4.JPG
not write
 

Attachments

  • 4.JPG
    4.JPG
    99.6 KB · Views: 6
Same problem here with S25FL128S and FCUSB build 340: Read is correct; Flash/Erase Chip says "Erase operation successfully completed", but the chip is not erased. Write will not write anything, but if Settings/Verify Programming is activated, it is going to produce lots of error messages. It seems as if there were similar problems with the bus pirate, as someone on their blog reported a similar problem here:
http://dangerousprototypes.com/forum/viewtopic.php?f=40&t=6164 (theory is that OTP lock bytes prevent from writing - but rather questionable if that could prevent any writing at all)

From the source of build 340 I can see that changes were made for Spansion S25FL256S (line 47 in SPI.vb). Still the S25FL128S from the same series and generation is identified as its predecessor S25FL128P by FCUSB. So maybe there have been changes in the command set from the P to the S generation which have so far been reflected only for the bigger S25FL256S but not for the smaller brother S25FL128S in the current sources.
 
It will not kill the chip , i had a similar issue on a Spansion s25fl064 chip, it would read but not erase /write etc , set FCUSB jumper to 5v and it worked perfect
 
Tried the 5V setting and it's indeed been a partial success: I am now able to erase the chip, which did not work with the 3.3V jumper set. But when it comes to writing, there is some strange behaviour:
- the FCUSB (build 340 with FW 3.05) will only write until offset 0xFF; any memory space beyond that address still contains (FF) after the write operation
- the console log will state "Write Flash operation complete!, 65536 bytes written in 5.07 seconds, 13,089 bytes/s", but the blue LED on the FCUSB keeps flashing (waited for more than an hour) and the software becomes unresponsive; only way to get back into business is to reset the device (Non-DFU mode)
 
It seems still to be a power issue , are you using fcusb as the power source ? If so try an external source if possible.
 
Briefly tried with a 3V external power supply, but FCUSB did not even recognize the chip correctly (even not after reconnecting to the FCUSB's power supply pins). As the Dupont cables from the FCUSB were directly soldered to the chip's pins, this might be an issue, too. I have just ordered some SOIC-16 testing PCBs to avoid dodgy pin connections going forward. Will report further progress once I got the testing boards.
 
Just to give a quick heads up for the S25FL128S flash: Chip is now soldered to a testing PCB. I additionally got a variable DC power supply.
I am not sure how to connect the chip to the power supply, though. When connecting the chip's VCC/HOLD pins and the GND pin directly to the power supply (i.e. VCC Pin and GND pin on the FCUSB are not connected at all) and leaving the remaining 4 pins connected to the FCUSB, the software won't identify the chip any longer (tried with 3.3V).

Additionally, I measured the voltage between the chip's GND pin and and the VCC pin with power only supplied from the BCUSB while reading, erasing and writing with the 5V jumper enabled.

- While erasing, the voltage drops from 5V to 3.4V (sometimes this procedure has to be repeated several times to really erase the chip completely).
- While reading the voltage drops from 5V to 4.8V
- While writing (verify off), the voltage immediately drops from 5V to 3.38V and then comes back to 4.8V with the FCUSB hanging. (Result is that offsets until 0xFF are written, but nothing else).

The million dollar question now seems to be, how and where to correctly connect the external power supply - or would it better to resolder the chip to the board and try to flash it "in situ" with external power directly supplied from the board?
 
Just to report that it looks as if the write operation did work correctly. The setup was:
(1) to connect the FCUSB to the S25FL128S on a testing PCB as shown in the manual
(2) to set the voltage jumper to 5V as suggested by D3mon in post #7
(3) to simply add an external 5V DC source to the given setup (i.e. the VCC & hold pins on the chip are connected to both the FCUSB VCC pin AND the + cable from the external PSU; the GND pin on the chip is connected to both the FCUSB GND pin AND the - cable from the external PSU)

Further side notes:
- The above setup did not work with the voltage jumper on the FCUSB set to 3.3V even if an external power supply with the same voltage is added; 5V do indeed look mandatory
- Even for reading, 5V PLUS an additional power supply are advisable. When I read back the chip content with 5V only from the FCUSB, there were actually some diffs to the file which I flashed before. These diffs came from an erroneous read, though and once an external 5V was added as described in the setup above, the readout exactly matched the content flashed before.

Thanks to D3m0n for the advice - would never have been able to figure out a solution without this forum!
 
Glad you got it sorted , I have been trying to aquire one of these chips to replicate the issue , but seems you have it solved.
 
I think the problem is that this Spansion requires a lot more power than other SPI memory. The draw from FCUSB 1.x can only be 20ma. This has been solved with the new version of FlashcatUSB (2.x), which now has an on-board dedicated PSU (dual-linear output voltage regulator) that can provide over 120ma to power external memory chips.
 
Back
Top