See All Categories

Learn More



Current Page

  1. Home
  2. Question Board

Question Board

Question Board

Forum Details
Title Legacy dapter fails read/write/verify/erase
Posted by tommy (ip:)
  • Date 2017-01-25 07:33:13
  • Recommend 27 Recommend
  • View 385
Rate 0points

25January2017 UPDATE:  Re-installing USB driver enabled functions.  Windows XP discovered board, asked to install driver.  I used Windows XP installation to re-install(I thought) and the board worked properly.  Yellow LED flickered on read/write, and the progress bar displayed progress properly.  SUCCESS.

 Word instructions seem contradictory, indicating to install program, then drivers before inserting USB NANO board.  I am still confused as Windows 7 recognizes the board, but does not work, and does not want to 'install' drivers itself.

Any way, !success!


 The Legacy board indeed recognizes older eeproms, and will re-program them quite well.


tom

...................................

Yellow LED flickers as adapter tries to identify SST29EE010 chip.  Cannot READ, etc, get 'Fail' msg.


Device Information

 Device Name:

 Manufacturer :

 Device ID : 0x25D9

 Interface: 8bit - FWH to Legacy Adapter

Densifty : 0 byte


 All functions have green moving shapes in bottom status bar, then prompt: "Plug jumper ON:5V" click OK, and ' X FAIL' in red is the displayed.

 LOW SPEED in right corner of status bar.

 Program asks for ROM file name when I attempt to write, etc, but then get the same 'FAIL" and red X


 Never get any progress indication.  Legacy jumper on 5V (on jumper pins).  Also tried with jumper removed. Same result.


EE-prom/rom was programmed on motherboard, with wrong bios.   Will not boot.  Bought programmer to re-install original bios programming.


 No mention of "Legacy Adapter" use in any documentation.  I plugged pin 1 into USB board as indicated in question board post.

****

 Tried a "known good" W29EE0110" with an Award bios for a shuttle HOT569.  It took a bit longer to 'read' and 'Get ID', with the yellow LED flickering longer, and reported a similar result, with the Device ID: 0X494D, 8-bit, and ZERO byte density as before.  Would not read the EEROM.  Failed.

 Am I doing something wrong?  Will this device read & program these eeproms?

 Suggestions?

tom

 

Attachment
Password Please enter password to remove or edit this post.
관리자게시 게시안함 Spam Not Spam
List Delete Modify Reply
  • 대표 관리자 2017-02-03 01:55:28 0points
    Modify Delete Comment
    Spam OK, I understand. Thanks for update.

Spam Not Spam

Edit Comment

Password :

Edit Cancel

0 / 3000 byte

Password : Submit Cancel

Add Comment

Add a commentName :Password : View Reply

submit

/ byte

Please type without any spaces.(case sensitive)

Comments can be added by Member only.