Here's the deal: I've got my bin worked out, I erase the 29C256, then load to bin on it. When I then "read" the eprom back into the buffer there are some areas that do not appear to be programmed. Large blocks of FF's. However, when I do a "display" function which looks at small blocks of data one at a time, the data all seems to be there.

My gut feel is that the data is programmed correctly but the eprommer fails when it tries to read the whole chip at once. Any ideas?

Ive got a pretty slow computer with windows 2k.

Steve Huddleston

 

what size bin are you using?

a 29c256 will hold a 32K bin

if you are using a 16K bin you will need to double it to 32K by

@ command prompt

copy /b 16K.bin + 16K.bin 32K.bin

the programmer cannot manually set the start point, otherwise you could just start programming @$4000.

 

It's a AUJP bin that I only changed the usual flags and the injector constant. Appears to be 32K in size.

The area of FF's starts at $4772 to the end.

But it only shows them when I do a "read". A "display" shows the correct data. weird.

Thanks

Steve Huddleston

 

ive had problems with my epromer5 with win2k and winME. its just a bug. usaully restarting the program will clear it up. program the chip then do a verify. i have a routine where i verify it 3 times in a row. if it doesnt verify i reprogram the chip.then verify it as outlined before. if it fials to verify then i restart the program and try again. if on that second attepmt it doesnt verify i restart the computer and as long as i dont run any other software it work flawlessly all day long.