<br><span class="gmail_quote">On 11/21/06, <b class="gmail_sendername">Peter Stuge</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> They have one week warrany on them so I would like to test them if<br>> they are free of errors even if the 440bx is not ready for prime<br>> time. Is there some easy way to do this?</blockquote><div><br> </div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">But you can test that they actually work right now.<br>1. Boot your system with the normal BIOS.
<br>2. Run: flashrom -r original.bin<br>3. Email original.bin to self.<br>4. Remove your original flash chip while the board is powered. Put<br> one of the new chips in. Observe polarity! There's a notch on one<br> end of the package.
<br>5. Run: flashrom -wv original.bin<br>6. If the write+verify works you should be able to reboot with the<br> new chip working as your BIOS.</blockquote><div><br></div></div><br>Well both chips failed verify. Read and Erase seems to work fine, yet verify seems to fail at the same place for both chips 0x2f. Doing less on written binary it seems that there are areas that were left zeroed, and unwritten. For both chips pattern seems to be the same.
<br><br>Do I blame eeprom and return them or problem is elsewhere?<br><br>./flashrom -r ATC-6220.Award.1-1-03-WB.orig.bin <br>Calibrating delay loop... ok<br>No LinuxBIOS table found.<br>Enabling flash write on PIIX4/PIIX4E/PIIX4M...OK
<br>W29C020C found at physical address: 0xfffc0000<br>Flash part is W29C020C (256 KB)<br>Reading Flash...done<br><br>[please cc]<br>-- <br>Thanks!<br>Shaddam IV