| Author |
 Topic  |
|
|
Praz
22 Posts |
|
| Reply #1
ZLM
2945 Posts |
 Posted - 06/09/2013 : 22:36:51
|
Try to add this line to devices.txt
Name="W25Q64FV",ID="EF4017",Class="W25X10",Category="SERIAL_EPROM",MFG="Winbond",Vcc="3.6V",CodeSize="8388608",Adapter="ADP-081, ADP-027 adapter",Platform="GQ-4X";
|
 |
|
| Reply #2
Praz
22 Posts |
Posted - 07/24/2013 : 16:56:24
|
| Just saw this. Thanks much. |
|
|
| Reply #3
ZLM
2945 Posts |
Posted - 08/17/2013 : 22:39:37
|
can you get the ID correctly?
|
|
|
| Reply #4
Verkkotalo
3 Posts |
Posted - 08/22/2013 : 13:45:11
|
Hi
I have same problem , please help flash bios chip .
id: read good
thanks |
|
|
| Reply #5
Verkkotalo
3 Posts |
Posted - 08/24/2013 : 12:01:19
|
quote:
Originally posted by WaskanyanTigran@yandex.ru
Can't erase W25Q64FVSIG, USBPrg 6.23, GQ-4X Re-1.30. When I press "erase" USBPrg says "OK" in 0.00 seconds, nothing erased. Tested on two chips, same effect. Any ideas?
Hi
I have same problem , please help flash bios chip .
id: read good
thanks |
|
|
| Reply #6
ancient
Finland
3 Posts |
Posted - 11/28/2013 : 04:36:21
|
Slow read works and write if erased with another programmer.
So erase needs fixing. |
|
|
| Reply #7
vlad_itj
Brazil
8 Posts |
Posted - 12/02/2013 : 09:44:19
|
This options works fine to me:
config.txt:
Name="W25Q64",ID="EF4017",Class="W25X10",Category="SERIAL_EPROM",MFG="Winbond",Vcc="3.6V",CodeSize="8388608",Adapter="ADP-081, ADP-027 adapter",Platform="GQ-4X";
Panel settings:
speed=0 (or speed=3 in message log)
|
|
|
| Reply #8
Ripple
1 Posts |
Posted - 04/26/2014 : 09:18:49
|
was then solved the problem of cancellation of this flash?
I too have the same problem and I can not write properly without deleting it.
Is it possible that even after almost a year there a solution? |
|
|
| Reply #9
juanmiglesias
Venezuela
4 Posts |
Posted - 06/16/2014 : 14:04:20
|
| im having issues with an asrock bios, chip is 25q64fv, datasheet seems identical to cv, mine is DIP so I believe I don't need the smd adapter, at first I had the same issues, but after using the 25q64vc device id, and 0 in speed ( -2 -1 0 +1 +2), I manage the write, erase, blank check and verify. my problem now is with my MB seen the bios. |
|
|
| Reply #10
ZLM
2945 Posts |
Posted - 06/16/2014 : 21:11:53
|
If the chip is verified after write, then your bios data file is not correct.
|
|
|
| Reply #11
timarzsolt
22 Posts |
Posted - 10/15/2014 : 05:39:08
|
Hi!
I have W25Q64FVAIZ and GQ-4X. There is no 25Q64FV in the device list, so I decided to write it with Device W25Q64. I read about that the erase works only, if the speed is set to 0. Now, I'm writing the chip with zero speed, and the input file and what is read out from the chip is different every time, but the read files are the same.
Here are the three files. What am I doing wrong?
www61.zippyshare.com/v/7354633/file.html
www61.zippyshare.com/v/71519184/file.html
www61.zippyshare.com/v/89062060/file.html
|
|
|
| Reply #12
ZLM
2945 Posts |
Posted - 10/17/2014 : 22:43:36
|
| Erase use 0 and write you can try +2. |
|
|
| Reply #13
timarzsolt
22 Posts |
Posted - 10/18/2014 : 02:09:43
|
| I tried it. I don't know what the problem is. If I fill the whole buffer with AA, then if I write it into the chip with +2 then the verify is successful. I need to write a Z87-K ROM, but it have a CAP bios rom. The CAP file is 2048 byte larger, than other old ROM files, so I googled after, and found a solution how to convert this CAP into a ROM file: use linux, and "dd bs=2048 skip=1 if=BIOS.CAP of=BIOS.ROM". Every time I'm trying to write and verify this converted ROM, I get an error always at 0x4C00F3. But if I'm using a different BIOS version, that is also coverted from CAP to ROM, it fails to verify at different offset. What the hell? |
Edited by - timarzsolt on 10/18/2014 02:12:05 |
|
|
| Reply #14
ZLM
2945 Posts |
Posted - 10/22/2014 : 22:46:31
|
| can you send your data file to support@mcumall.com? it will be tested in lab and see what is wrong. |
|
|
| Reply #15
timarzsolt
22 Posts |
Posted - 10/24/2014 : 12:52:07
|
| Yes, I did it. I'm curious why this happens. |
|
|
| Reply #16
timarzsolt
22 Posts |
Posted - 11/05/2014 : 12:38:02
|
| Nothing yet. How long do I wait? |
|
|
| Reply #17
GQ5XSupport
104 Posts |
Posted - 11/06/2014 : 11:44:38
|
| Highly suspect it is the power.Please find an external power adapter. Erase and programming needs draw more power. The USB from PC might not be powerful enough. Nothing wrong with GQ logic. |
|
|
| Reply #18
timarzsolt
22 Posts |
Posted - 11/12/2014 : 10:13:58
|
I just bought a 9V external power adapter, and there is no difference. Here is my log:
Ready
H/W Re: GQ-4X Re-2.20(SW Re. 6.32)
USB Driver Re.2.0
Software Re. 6.32
Checking new software on server...
<<W25Q64FV>>
This software is updated already.
xxxxxxx\z87-k-asus-1401.rom.
Speed = 1
Speed = 3
ID check OK
Erasing...
Elapsed time: 18.78 seconds.
Erase completed.
Writing... Code
Elapsed time: 750.66 seconds.
Device write completed OK
Verifying... Code
Verify Failed, Address=0x4C00F3, Device=0x5E, Buffer=0x5F
Verify Failed
So some offset are different in the chip as in the buffer. BUT, if I read the content of the chip (so 0x4C00F3 will be 0x5E instead of 0x5F), erase the chip and write it back what I read out (so in buffer at 0x4C00F3 will be 0x5E) then it passes the verifing process. But why?
Update: I filled the buffer with full of 5Fs, and here is my log:
ID check OK
Erasing...
Elapsed time: 19.13 seconds.
Erase completed.
Writing... Code
Elapsed time: 755.22 seconds.
Device write completed OK
Verifying... Code
Device is verified
Elapsed time: 819.61 seconds.
 |
Edited by - timarzsolt on 11/12/2014 10:49:56 |
|
|
| Reply #19
GQ5XSupport
104 Posts |
Posted - 11/12/2014 : 15:45:46
|
| Can you do a blank check after the erase? |
|
|
| Reply #20
timarzsolt
22 Posts |
Posted - 12/04/2014 : 03:01:25
|
| Yes, blank check goes well. |
|
|
| |
Topic |
|
W25Q64FV
