Author |
Topic |
|
danisz
Romania
3 Posts |
Posted - 05/25/2009 : 12:18:20
|
I need help erasing a Winbond W25x80 SOIC-8 with a True-USB PRO GQ-4X. It's a 1MB BIOS chip from an Asus P5B motherboard. I'm using GQUSBprg 4.01 and GQ USB Driver 2.01.
I connected the 8 pins to the programmer with a home-made adapter. The adapter is just for the pins to reach the programmer's socket. I respected the pin position for W25x80. The ID and content from the chip is read successfully, code memory is not all FFs. The program also says it erased the chip but failed Blank Check with error "Device blank check failed at address: 0x000000, Read= 0x41". Tried all speed options with no positive result. Also tried the Unprotect command, but it hangs and does nothing. Not even sure it's meant for W25x80 (says "29F0XX protect feature") but tried it anyway. Same experience with another chip: Macronix MX25L8005 (both are 8 pin Serial EEPROMs).
Any good suggestion would be much appreciated.
|
|
Reply #1
ZLM
2945 Posts |
Posted - 05/25/2009 : 19:24:14
|
Do you have another 25X80 for testing?
It seems the chip is proected.
try to connect the pin 3,7,8 together. This will make sure the chip is not hardware protected.
chip pinout:
|
|
|
Reply #2
danisz
Romania
3 Posts |
Posted - 05/26/2009 : 11:27:18
|
Thank you for the quick reply.
Tried with another w25x80, this time directly from the motherboard with a SOIC8 testing clip. It can read, but can't erase. I measured pins 3,7 and 8 and they are all 3.6V, VCC is 3.9V, so i guess it`s not hardware write protected. In the W25x80 manual i found that "after power-up, /CS must transition from high to low before a new instruction will be accepted. The /CS input must track the VCC power supply level at power-up" and a pull-up resistor is suggested. I wonder if the programmer does that transition from high to low and track the VCC automatically. |
|
|
Reply #3
ZLM
2945 Posts |
Posted - 05/26/2009 : 19:15:15
|
If the chip can be read, then the CS sinal is working fine.
Can you try to select AT25DF041A to erase the chip?
|
|
|
Reply #4
bebacu
Romania
2 Posts |
Posted - 05/27/2009 : 05:07:47
|
I have the same problem. I think the Re. 4.02 Beta 1 don't execute this instruction Chip erase C7h for W25x80. I'm wrong? Sorry for mi englease. |
|
|
Reply #5
ZLM
2945 Posts |
Posted - 05/27/2009 : 07:13:06
|
It works on my W25X80 chip. So, I guess the erase command is correct but the chip is locked. try to select AT25DF041A to erase the chip. The AT25DF041A has unlock feature when eraseing. |
|
|
Reply #6
danisz
Romania
3 Posts |
Posted - 05/27/2009 : 08:08:09
|
Didn't work with AT25DF041A. It's strange that both my chips refuse to erase. How did you connect the chip to the programmer? Did you insert it in the ZIF socket, used a SOIC8 to ZIF adapter or testing clip directly on the PC motherboard? Did you use USB or AC power? How about the software and driver version? |
|
|
Reply #7
ZLM
2945 Posts |
Posted - 05/27/2009 : 09:50:10
|
The software is Re 4.01 I am using. Nothing to do with USB driver. I put the chip directly on ZIF, no adapter used since my chip is DIP8 chip. The USB power is good enough for this chip.
Are you able to send a testing chip to me? I will send it back to you after testing.
|
|
|
Reply #8
ZLM
2945 Posts |
Posted - 05/30/2009 : 01:06:47
|
Try new testing patch done today:
http://www.mcumall.com/download/TrueUSBWillem/USBPrg4.02Beta1Patch.zip
unzip and copy to the software directory. Overwire the old version USBPrg.exe file.
The patch does not work standalong, it only works with other files under "C:\ProgrammerFiles\GQ USB Programmer" directory with all other files together. So, you need to overwrite the Re 4.01 USBPrg.exe in that directory with this file.
Let me know if it works. |
|
|
Reply #9
bebacu
Romania
2 Posts |
Posted - 05/30/2009 : 14:31:33
|
I select Eon EN25F08 and erase and write the w25x80 and mx25l8005 whiout any erors. That it's a best solution for the moment. I whant test whit new patch, maybe monday. |
|
|
Reply #10
Bad_Ad84
210 Posts |
Posted - 06/01/2009 : 04:04:15
|
if theres a type that works, you can just add an entry to the devices file. |
|
|
|
Topic |
|