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

Request for Winbond W25Q64BV SPI

Need a bit more information , like does your BCUSB detect the flash etc. If so what output do you get in the console window etc.
 
Hello,

I think that Winbond w25q64bv is official supported.

I have got software in version 322 (I requested to add support for another SPI flash chip and got 322 build) and it detects Winbond w25q64bv after run Main -> Detect device but... write speed is very low - about 5~6 KB/s. Is there any possibility to speed up write process? I tried to use manual settings for SPI flash but without any better results.

Thanks in advance!
 
It seems that there is a problem with Winbond w25q64bv programming.
I tried couple of times with verify programming option enabled and I get following errors:

Opened file for writing: wr703n_uboot_websafe_OK.bin (binary hex format), total file size: 8 388 608 bytes
Address 0x0: wrote 0x10 and read 0x0 (23398 mismatches)
Address 0x0: wrote 0x10 and read 0x0 (23398 mismatches)
Address 0x0: wrote 0x10 and read 0x0 (23398 mismatches)
Error: data verification at 0x0 failed!
Address 0x8000: wrote 0x5E and read 0x0 (32632 mismatches)
Address 0x8000: wrote 0x5E and read 0x0 (32632 mismatches)

Info from console:

LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine build: 200
Welcome to BlackcatUSB interfacing software, build: 322
Running on: Microsoft Windows 7 Professional (32 bit)
Device connected in SPI mode, firmware version: 3,01
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: EF 4017)
Flash detected: Windbond W25Q64BV (8 388 608 bytes)
Programming mode: SPI (high-speed)
 
Please try the latest release build 326 available on the embeddedcomputers website and report back.
 
Still something is wrong.

I have loaded new SPI firmware 3.04 and I tried with software 326.

I think that reading functionality works OK (I can't confirm because my second programator is broken) but programming isn't.

I tried to load some image but I got again error during data verification.

I have tried with 3 different chips (I bought a lot of them).
Same error during programming with data verification.

With verify option disabled transfer speed is very poor (~2 KB/s) and I think that image isn't write to chip at all - after reading I'm not getting the same image.

Furthermore, sometimes software isn't responsible during writing operation with those chips (sometimes it freezes) and I think that BCUSB is hanging - after try to write something, the blue LED is still blink after end of operation and reading speed after that is very poor (~2 KB/s). I need to close software and reconnect BCUSB.

PS. Does this version (326) contain support for EON EN25Q64 SPI?
I got build 322 directly from embeddedcomputers after my request by e-mail.

Here is log from my attempt:

LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine build: 202
Welcome to BlackcatUSB interfacing software, build: 326
Running on: Microsoft Windows 7 Professional (32 bit)
Device connected in SPI mode, firmware version: 3,04
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: EF 4017)
Flash detected: Windbond W25Q64BV (8 388 608 bytes)
Programming mode: SPI (high-speed)
Opened file for writing: uboot__0x0.bin (binary hex format), total file size: 60 107 bytes
Address 0x0: wrote 0x10 and read 0x0 (23397 mismatches)
Address 0x0: wrote 0x10 and read 0x0 (23397 mismatches)
Address 0x0: wrote 0x10 and read 0x0 (23397 mismatches)
Error: data verification at 0x0 failed!
Address 0x8000: wrote 0x36 and read 0x0 (27225 mismatches)
Write Flash operation complete!
60 107 bytes written in 45,02 seconds, 1 335 Bytes/s
 
Contacted the developer and i am awaiting a response from him regarding this.
 
Can you post some images of your connection to the device/ flash ?
Also what device is it and what script are you using as it looks like you are trying to program the u-boot
 
D3m0n said:
Can you post some images of your connection to the device/ flash ?
Also what device is it and what script are you using as it looks like you are trying to program the u-boot
Click to expand...

Ad 1. I'm not at my workshop now, so I can't upload real images. I'm using simple adapter SOIC8 (like this one: http://www.futurlec.com/Pictures/SOIC_8.jpg) with solderless cables (like for arduino: http://i00.i.aliimg.com/img/pb/718/801/398/398801718_098.jpg) connected like on page 9 from documentation. The flash is always soldered to the adapter, so connection is very good (I have programmed many flashes, like EON EN25Q64, in this configuration without any problems).

Ad 2. I don't use any script and I don't connect BCUSB directly to a device. And yes, I want to load u-boot in this case. It's for TP-Link WR703N router.

I'm able to clear flash with command "Memory.EraseBulk" from console (it took ~9 second). After that, if I read entire flash, I got empty (FF) bin file. Something is wrong only with programming those flash chips.

My BCUSB is version 1.8 with MEGA32U2-AU

IMPORTANT!
I don't remember if I'm using HOLD pin in my configuration, I will check this today. I think it could be related to problems with programming, am I right?
 
If you are programming the flash as standalone then HOLD and VCC must be connected together this could possably be the issue , the developer is ordering one of these chips to test to 100% verify there is no issue with it software wise.
 
D3m0n said:
If you are programming the flash as standalone then HOLD and VCC must be connected together this could possably be the issue , the developer is ordering one of these chips to test to 100% verify there is no issue with it software wise.
Click to expand...
I will check this! Simply, I don't remember if I'm using this pin. But, I'm sure that I didn't use it with EON EN25Q64 flash and I didn't have any problems.
 
It may be chip specific that causes an issue like this , so verify it both ways to see. If you still have the issue then we need to wait a couple of days until the developer has the Flash Chip so he can test it himself and come up with a solution.
The developer has tested the 8mbit and 16mbit versions and they program fine , but the 64mbit version was not tested , but basically should not have any issues.
 
Bingo!

It was my fault... problem occurs only without connected pin HOLD.

Now everything works fine!
Programming speed with verify option enabled reaches 200 KB/s.

I'm sorry for bothering you! :oops:
 
Hi there,

I have just got my programmer today and I was trying to program the W25Q64BV Chip.
Actually, I am facing the same problem as described by "pepe2k"!. Error while verifying the data that has been written, I have verified that the HOLD and WP pins are tied to VCC.

Below is a small chunk of the log file:
"Error: data verification at 0x7D0000 failed!
Address 0x7D8023: wrote 0xA and read 0xCF (32724 mismatches)
Address 0x7D8045: wrote 0xA and read 0xCF (32699 mismatches)
Address 0x7D8002: wrote 0x30 and read 0x3F (32766 mismatches)
Error: data verification at 0x7D8000 failed!
Address 0x7E0009: wrote 0xA and read 0xCF (32727 mismatches)
Address 0x7E002B: wrote 0xA and read 0xCF (32720 mismatches)
Address 0x7E0100: wrote 0x30 and read 0xFF (32490 mismatches)
Error: data verification at 0x7E0000 failed!
Address 0x7E8033: wrote 0xA and read 0xB (32683 mismatches)
Address 0x7E8055: wrote 0xA and read 0xCF (32676 mismatches)
Address 0x7E8033: wrote 0xA and read 0xCF (32713 mismatches)
Error: data verification at 0x7E8000 failed!
Address 0x7F003B: wrote 0xA and read 0xCF (32650 mismatches)
Address 0x7F003B: wrote 0xA and read 0xB (32709 mismatches)
Address 0x7F0081: wrote 0x30 and read 0xF7 (32639 mismatches)
Error: data verification at 0x7F0000 failed!
Address 0x7F8043: wrote 0xA and read 0xCF (32700 mismatches)
Address 0x7F8043: wrote 0xA and read 0xCF (32701 mismatches)
Address 0x7F8043: wrote 0xA and read 0xCF (32686 mismatches)
Error: data verification at 0x7F8000 failed!
Write Flash operation complete!
8,388,608 bytes written in 71.899 seconds, 116,672 Bytes/s"

I have no issue reading the PROM content and I did verify the content with the original file which was correct.
I am using BCUSB PCB version 1.7, software version Build 326.
It detect the correct memory with the right ID numbers as stated on a pepe2k reply.

I hope the developer still working on solving this issue.

thanks.
 
Hi samir,

In my configuration, WP pin isn't connected, like in documentation from BCUSB, page 9.
 
@pep2k,
I am driving the WP low and hi depending on my needs.
I hope someone else can confirm that this chip works well or not? the exact part number is: W25Q64BVZEIG.
 
Have you tried as pepe2k mentioned , by not connecting WP# , he has managed to read/write to the chip this way and the developer has done so as well on the 8 & 16 mbit versions
 
I can't give up the WP# feature. Even the read back option does not work all the time, must be a connection issues! I will double check the connection and let you know my findings.
 
For what reason can you not release the WP# ? This could be the reason for your issues , as it is not connected in the BCUSB schematic.
 
You must log in or register to reply here.
Back
Top