quote:

---

Originally posted by Demotitive

Hi all,

I have the old style willem programmer -- PCB5.0 and PCB3.5 --

http://www.mcumall.com/support/DualPoweredWillemUserGuide.htm

and I am trying to read and write Intel AB28F200BX-B.

Problem is, while willem has the option (i28F200BX-B in device menu) and it correctly identifies as Intel 28F200, the reads are not the same. The buffer and the device never match -- meaning when I do a read, it reads just fine...but when I click verify to verify that it actually read, it spits errors.

Comparing the .bin from willem to a known good programmer shows that willem introduces garbage, even though it CAN read in areas that others cannot. WinOLS cannot read the file, but can easily read the .bin from known good programmer.

Then when I have a known good .bin file to program into it, and I erase the chip, it erase it....but it is not a complete erase. And it keeps spitting out errors after programming and says the value on the chip does not match buffer.

I am frustrated, maybe wondering if I am goofing up something. Any advice is greatly appreciated.

---

quote:

---

Originally posted by anniel

[quote]Originally posted by Demotitive
Are you certain your programmer is fully functional?

---

quote:

---

Originally posted by Demotitive

quote:

---

Originally posted by anniel

[quote]Originally posted by Demotitive
Are you certain your programmer is fully functional?

---

Yes, I know it works with AM29F400 and AM29F800, plus various eeproms. I'm just not sure what 28F200 requires, really.

I was researching and turns out that I may have missed the erase step -- apparently the erase button on the program and the erase button that you find on the Device menu are two different thing.

Also I may need to swap the power supply, one of the theory was that the power supply may not be able to supply sufficient amperage, and I am indeed using a different power supply than the original one I used with AM29F400.

---

quote:

---

Originally posted by Demotitive

Turns out it was the power supply, plus I forgot to disable the disable write to 0xFF feature. Once that was done, then suddenly perfect read and perfect write.

I'm so happy.

---