i have all my burning equipment and got the AT29C256 chips. well i am at the stage in the pocket programmer windows software where you verify device to buffer. i am have loaded the arap.bin it expects XX(every pair of #'s is different) and always finds value FF. i have set start of device offset 4000. is it supposed to do that? i thought the values were supposed to be the same? has anybody else had a problem similar to this? help me out guys i'm trying to learn.

 

I don't like to fiddle with the offsets, so what I do is this:

copy /b arap.bin + arap.bin burn.bin

Then I open PP, load the burn.bin into the buffer, and hit program device.

It should be set on auto verify, if not, hit the verify button to check. I'm not sure how verifying works with the changing the offset in PP.

 

well i now got rid of that problem. the next thing is i load the bin. then move device. then it says device verified to buffer. the checksum changes to zero among other settings. well then i save the bin file. and open it with winbin and all values are zero? aren't they supposed to say what they said before i verified? as before i am new to this and try to bear with me please. thanks.

 

can some please tell me how they use this pp program with the original 16K bin. Tell me if i am doing something wrong here.

1.) Open Program
2.) AT29C256 Is Selected PROM Type
3.) Load Buffer ARAP.BIN
4.) Move Device To Buffer
5.) Start Of Device Is Set To 4000
6.) Device Is Verified
7.) Program (Burn)


is this the right order to program. or am i doing something wrong here. first chip total failure. check engine light always on. i KNOW i'm doing something wrong. come on burning guru's i know your out there and know the correct procedure to get up and running.

 

This worked for me:

To load a 16k file in the top half of a 32k AT29C256 EEPROM with Pocket Programmer II and Win_pp2, try this.

1st) Select AT29C256
2nd) Fill buffer with FF
3rd) Program chip with buffer (just to make sure it's blank when I start)
4th) Change Start of Device to 04000
5th) Load buffer with 16k your.bin file
6th) Program the chip
7th) Change Start of device back to 00000 <- The key to seeing WHERE it's at in the buffer!
8th) Move device to buffer
9th) Edit the buffer

You'll see that the .bin file is located in the upper half (04000-07FFF)of the chip now
and from 00000 to 03FFF is blank.

Acutally I can shell out to DOS and COPY /B myfile.bin+myfile.bin myfileD.bin faster but after reading how confusing this was to some people and I wanted to figure out how to do it, so I did.

Remember, if you try to save this bin file off of the chip you programmed Winbin is not going to read it correctly because it will save as a 32k file unless you change the start of device before you save it. Just edit the bin you programed in previously and either double it or use the method above to program the 16k bin file into the 32k chip.

Works for me, hope this helps.

 

Alternatively, you can READ the "already programmed" AT29C256 as a 27C128 (which is what you are trying to emulate anyway) and you SHOULD see the bin you just programmed in the Edit Memory from 0000-3FFF. Just make sure you pull the Flash prom from the PP while you are changing the "selected eproms" on the PP from AT29C256 to 27C128, fill the buffer with FF, insert the Flash Prom and read it as a 27C128.

 

ok guys thanks for the GREAT INFO. i will attempt to burn per the instructions provided. i will report back with results. thanks SMasterson and Glenn.

 

.

 

ok i double checked my steps and see that i have missed that part. i can get to 9th step and know not what to do to the buffer. you say edit it. what should i edit in there exactly. i do see that 00000-03FFF is blank. i'm sorry for so many question i'm just eager to burn my own chips.

 

i did the copy command and now have a 32K file. so can i omit steps 4, 7, 8, 9? am i on the right path or pissing in the towards the wind?

 

ok i finally go it working. i'll buy all you guys a beer if your ever down here in san antonio

 

OH, I didn't mean edit it to change it, just to view where it's at in the buffer with the PP software. Anyway, I see you got it working!
I'm sure you realize by now to edit the bin file you use the Winbin/Tunercat, or a hex editor if don't have anything else.

Good luck and let the fun begin!