(01-06-2016, 05:25 AM)BDMaster Wrote: You have a problem with the Clip probably !
Align all Tools to Pin #1 from Programmer to the Eeprom Chip (foot with ball) on MoBo,
look the red wire (Pin #1 to align too) then check connection into Program and try to
read the chip device (the program has to recognize It) !
Then Read again the chip and if You get all 0xFFh bytes then You are not connected to the
Eeprom Chip !
Then could You explain to me what have You done precisely ?
You have to read and not write so I hope You didn't erased the chip ?
Let me know
Regards
P.S. Here NASA may be I can help U yet
Initially I unplugged the computer, took the case apart, and installed the drivers on a desktop. I then connected the tools, albeit incorrectly at first (plugged in to the 24xx instead of 25xx, had the clip on backwards) and also had the pins in the 24xx rather than 25xx. When I first got it set up properly, I hit read and it was filled with 0xFF as in the video.
Here is a short video. I know it looks like I am clicking blank, but I did hit read, the framerate is just a tad low.
https://www.youtube.com/watch?v=dZnir2dKYGk
Also, here are two images of the tools hooked to the laptop: up
http://tau.rghost.ru/7zxbKR8Lv/image.png and
http://rghost.net/8rb9BsjZC/image.png
Lastly, I do have the AIDA64 report too, if that is of any use.
EDIT: Those images have the clip on the only winbond chip on the whole board. I would take that to assume that is the correct chip. I feel I should point out that the USB connected to the desktop is not the typical green one, however it looks as though the circuitry is the same, aside from a noticeable difference in placement of the chip, the 24xx/25xx sockets, and subsequent wiring leads. I did use the driver that most people use with the more common USB programmer. I found one or two posts buried on the net saying that they had success.