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

Trouble Flashing Winbond W25Q64FVSIG

Apelsin

Apelsin

New Member
I am trying to flash a chip (isolated / not on motherboard) and I am able to read data properly, but writing has been problematic. I'm only able to write the first page (256 bytes of input) and nothing more. The start/offset address works as expected, but I'm limited to 256 bytes. I want to write 280000h many bytes, ideally, filling up the higher address range.

Board firmware version: 3.05
JEDEC ID: EF 4017
Flash memory size: 8,388,608 bytes
Flash memory name: Winbond W25Q64

Has anyone had similar trouble with the FW series or is this an issue with FV?
Thanks for any help you can give!
 
Update: I just tried older SPI firmware version 3.01 and I am able to write! :)
 
I have just tested a W25Q64FV chip using Build 340 and 3.05 SPI firmware and it reads and writes ok

LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 202
SPI database loaded: 156 devices supported
Welcome to FlashcatUSB interfacing software, build: 340
Running on: Microsoft Windows 7 Ultimate (32 bit)
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (RDID:0xEF4017 REMS:0xEF16)
Flash detected: Winbond W25Q64 (8,388,608 bytes)
Programming mode: SPI (high-speed)
Beginning memory read from SPI Flash
Start address: 0 (0x00) Length: 8388609
Read operation complete
Read 8388609 bytes in 20.597 seconds, 407,313 Bytes/s
Opened file for writing: Winbond_W25Q64_00-7FFFFF.bin (binary hex format), total file size: 8,388,608 bytes
Write Flash operation complete!
8,388,608 bytes written in 31.24 seconds, 268,521 Bytes/s
 
I should probably mention that I'm using Windows 8.1, 64-bit, recently updated.
I also spoke too soon because this time I managed to write only 2048 bytes thinking I had written the whole thing. I had run into problems with verification before, so I panned to manually verify it instead. I am trying again using normal verification to see if it helps at all. Maybe this is just a bad chip, so I will another one soon.
 
How is your connection to the chip ?

Can you manage to erase the flash ?
 
D3m0n said:
How is your connection to the chip ?

Can you manage to erase the flash ?
Click to expand...

I'm able to erase the chip; it takes about 20 seconds. Reading is very fast, too, but writing is painfully slow (30 min for 280000h bytes). My average write speed is around 8KB/s
 
I think I did just discover the problem. I had the JTAG VCC pin option enabled in Flashcat thinking it would power SPI components! I turned it off and now it's working.
Apparently it was just interfering.

I enabled verifying again and manually verified (read back) using HxD that the entire payload was written properly :D
 

Attachments

  • ss (2015-03-29 at 11.32.19).png
    ss (2015-03-29 at 11.32.19).png
    2.4 KB · Views: 27
You must log in or register to reply here.
Back
Top