I finally got my programmer to work, but the scantool will not work with the new chips. I only get, Vehicle Not Responding, but when I replace the new chip with the old one it works fine. The car runs great with the new chips, but I have no speedometer. Anyone seen these problems before and have a solution?

I'm using 29C256 chips and a moates adapter.

 

I guess the first question would be what kind of chip are you using? Should be a 27C256. Also, how are you using the chip? What kind of adapter are you using?

 

Sounds like the chip didn't program correctly.

Try reading it, and then compare that with the .bin you were using.

If a 29C256 try first loading a .bin of all FF's. And then try loading the .bin file.

 

Well, I gave it another shot and it still didn't work. When I erase the chip it's all FF's. I can burn it and verify it and it seems to be the same when comparing the original bin to the one on the chip. When I put the chip in, the fans kick on and the scantool won't work, so I guess this means that something is screwed up. I've tried a couple of different bins and chips. This sucks.

 

There shouldn't be FF's in there. It should be blank. If your fans are coming on, that's a signal that there is a problem.

How are you erasing the chip?

 

I'm using a willem eprom programmer. The software will erase the chip, but it reads all FF's when erased. What should be on a blank chip when I read it? The strange thing about this is that the car will run. It's not in limp home mode, because the two different chips caused the car to run differently. The speedometer didn't work though and my scantool wouldn't work.

 

If you're trying to erase the chips electronically, you have to get the electronically eraseable chips. Most of the EPROM chips I know of are erased via exposure to ultraviolet radiation. If you're using one of those types of chips, I'm not sure you can erase them electronically. I could be wrong.

When you do a blank check, there should be nothing there. Not FF's... nothing. All of the addresses should be blank.

 

I take it your using atmel 29c256 EEPROM's type chips so the method of loading with FF's and loading your .bin file is fine. Sometimes I get the same problem as you if my chip is not inserted correctly meaning one pin got bent out of the way, I didn't have a ZIF socket for awhile there. I would look to see if all pins are making contact first and if that didn't work then try a different 29c256 chip if you have one, could be the one you have is blown.

 

A blank chip is a chip full of FFs.

Your problem could be caused by a number of things, including an invalid checksum, a bad PROM, the wrong PROM, the wrong bin for your application, invalid burn, etc.

try reading the programmed prom and doing a compare (windiff, whatever) with the original. make sure its byte-for-byte the same. if it is identical, then the prom could be the wrong type.