Man I have searched these boards over 2 hours and have settled on the fill buffer with FF initially and program device using Win PP2. Then change start of device to 04000 and end of device to 07FFF and load buffer with my 16K .bin. Programs and verifies just fine....only problem is it won't work at all. No SES light and runs in Limp Home mode.

I don't know if this matters or not but I'm using a Hypertech chip to put the 29C256 chip into...

Thanks for any help.

Brian P

 

Thats exactly what I'm doing. I've probably burnt about 30 chips already, every single one works fine. If the SES light isn't coming on, why do you think its in limp home mode? As far as I knew, if it goes into limp mode, the check engine light comes on. Are you using the correct definition file to edit the bin?

 

It was a corrupt .bin. I tried everything to get it to work then figured what the hell, could be a bad .bin file. Turns out I was right. Why do I think it was in Limp home? 'Cuz the fans came on in the key on position something they always do on my car if the PROM did not program properly.

 

Well I'm glad you found what the problem was.

 

How did you finally get the chip to work? I am having a similar problem as you, but I can only program to the upper half of the chip (AT29C256), 0000-03FFF. When I try and program to the lower half, 04000-07FFF, the .bin gets corrupted some how and my editor is unable to recognize the file. When I program to the upper half, my editor can recognize the .bin and I can see all tables and parameters, unfortunately it won't work in the ecm.

Just to give you a little more detail, Prior to prog. I fill the buffer with FF and program the chip, then it reads the device is erased, the I load my program into the buffer and prog. and it still comes back blank. I am using Wintronics pocket programmer and ver. 1.52 software (running windows 98 or XP made no difference).

Also, when I put a 27C128 chip in, it programs with no problem!

Any ideas????

 

Figured it out, never mind. With the combination of a few other posts (which took a while to hunt down) I finally got the AT29C256 chip to work in my 165 ecm. This might seem redundant to some, but might help some of you who are having issues similar to mine. Ok, here's what I did:

Using the pocket programmer (and ver1.52 software),
1) select AT29C256 as your chip.
2) fill the buffer with FF.
3) set start of the buffer and device to 04000.
4) the end of the buffer should already be 07FFF, if not, make it so
5) then, verify that your chip is blank.
6) load the buffer with your modified .bin file
7) then, Program the device.
8) once programming is completed, change the chip selection to a 27C128
9) move the Device to buffer,
10) Save the buffer (give it a different name than the original, I simply add verify to the end of the name and save the buffer to a different folder).
11) Finally, open tunercat and check to see if you were successful.

This is exactly how I did it and it worked beautifully. So, good luck.

 

https://www.thirdgen.org/techbb2/sho...threadid=39297

Tim

 

AWWW SWEET!

Been looking for something like this ALL morning!

 

I need to make a slight correction to my chip burning protocol. Line #3: You only need to set the start of the buffer to 04000. You can leave the start of device set to 0000.

 

If I'm using a double entried .bin. I build an editor for it, and use the full lenght of the file, rather then always adding the FFs from 0000-4000.

 

The loading of Hex FFs shouldn't really be necessary anymore. It was with an older version of the Pocket Programmer software. Once you are comfortable the Pocket Programmer is "working properly" and you have used the AT29C256 successfully, all you need to do is "offset" the starting address in the buffer by x'4000.

I find I never have to "go back" to read the bin off the Flash Prom as I usually have in on my computer for further changes. But the key is to remember that if you WANT to read the bin, that you must read it as a 27C128 (to get the proper offsets and bin size) while you write it as a AT29C256.

 

I forgot that the first time I tried to read one of my 29C256s.

Really messed me up.