SMasterson

I bought a AUJP16151348 MEMCAL from a local dealer a few weeks ago. I've burned many 165 27c256 and 29c256 PROMs successfully with my Pocket Programmer 2 and have read several stock and custom PROMs with it but I'm having a problem with (now) *TWO* NEW AUJP1615 MEMCALs.

Everytime I read them the 1st x00000, 00100, 00200 and every 16th line after that is all 'FF'. I can pull this MEMCAL out and read any of my other four 165's just fine so it's not my MEMCAL to PP adapter.

I ordered another one from gmpartdirect and received it yesterday. I have the exact same problem reading it.

Neither of them would start my engine. The fan came on like it was a bad MEMCAL.
The engine runs great with the one I changed to a 29c256 and re-programmed. I have been tuning on it for a few weeks, so it not my ECM or electronics.

I'll be changing this one to a 29c256 also, but I'm just curious. Anyone got any ideas? How likely would it be to get TWO MEMCALs from different parts on the country, (probably both from the same warehouse though) and both of them being bad? I can't believe this has only happened to me, unless it's something in my hardware.

Could it be a Pocket Programmer problem? It burns chips fine and reads others just fine, including two new ARAP MEMCALs I bought when I had the 165 ECM.

BTW, does anyone know if this would be an appropriate question for the GMECM digest?



------------------
_ ___ _
SMasterson

Grim Reaper

Based on what you are saying, I would assume you are doing EVERYTHING correctly - sounds fine to me.

I have 2 AUJPs, my original that came in the car and a second one I purchased when I got into eprom burning. I have never touched my original, so I cannot comment on that one. The second one worked fine, but I was using the older FIlEPROM and EDITPROM DOS software. I have never tried reading/reprogramming my spare with the Windows version of the PP software.

I will try reading them with my Windows Version and see what happens. Assuming mine reads fine, two things come to my mind.

1) The first pin is cut or not making a connection, this will prevent you from reading an eprom. It MAY be hidden and you cannot see it. Try "jumping" a wire between #1 pin and the "adapter" (assuming you are using one with the PP).

2) Your PP is defective. A few people have had this problem. Try and find someone that has a known good PP that is willing to read the Memcal for you. If they can, then it would have to be either you version of the software is not properly installed or the PP itself is defective.

[This message has been edited by Glenn91L98GTA (edited December 13, 2001).]

SMasterson

BTW, I tried it with a bare DOS boot and using FILEPROM. Same thing. Here's a sample and notice that all the data is correct except for the 1st,17th, 33rd lines, etc...

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0666010000E61004D82D0CCD08080808
0808080808110077FFF518182C181071
0171FF00000C39393939393939393939
39393939393939393939393939393939
44444444413F3C39393939414A4A4A44
413E3C39393939475050504A4744413F
3C3939475B5B5B524D44413939394761
675E5B52504D413C393955616961615B
55504A44393955616C66665E5B554D44
3C3955616C666663585047413F395561
6C66665B52504A3F3C3655616C636355
4D47443C363455616C61614D44413C36
343655616C6C61504A443F3939365564
72726150504A3F3F39396C727272725E
58504A4444446C72727272665B55504A
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
4A7272727272665B55504A4A4A727272
7272665B55504A4A4A0E121410121014
15131414141414392000095050505050
505050504A4A4A4A4A4A4A4A4A4A4A4A
4A4A4A4A4A4A44444444444444444439
39392B2B393939393939392B2B393939
39393939303039393939393939393939
39393939393939393939393939393939
39393939393939393939393030303939
39393028282828FF2BFE0A0000000000
000000000003060B1411111111110E0E
0E0E0E0E00000B010064646464643C1E
64645028281E3C808080808080808080
80808080FF0F4060C08008000E0E0E0E
0E0E0E0E0EFFFFFFFFFFFFFFFF393939
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0D101014141A1F1F4D5A56565E545A5A
... and so on.

When I removed the PROM from the first one it read the same as above.

This is weird!


------------------
_ ___ _
SMasterson

Grim Reaper

Have you compare what you have typed to the actual AUJP BIN? I haven't but the rest of the code doesn't look right either. Load the AUJP1615 from DIY-EFI and load it into the PP. Compare the two codes and I think you'll find there is even more errors.

I think your PP may not be reading a 27C256 properly. Again, I will assume you have the PP set to 27C256 (not 27256). Let me know what you find.

SMasterson

I have it set to 27C256. Also, I can read other 27C256's. I have several from before I switched to 29C256's. I looked up the numbers on the chip at
http://www.cruzers.com/~ludis/p4pinouts.html#16045915

Here's the comparison and I didn't type it in. I save them in ASCII HEX from Win_PP2.

NEW ONE:
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0666010000E61004D82D0CCD08080808
0808080808110077FFF518182C181071
0171FF00000C39393939393939393939
39393939393939393939393939393939
44444444413F3C39393939414A4A4A44
413E3C39393939475050504A4744413F
3C3939475B5B5B524D44413939394761
675E5B52504D413C393955616961615B
55504A44393955616C66665E5B554D44
3C3955616C666663585047413F395561
6C66665B52504A3F3C3655616C636355
4D47443C363455616C61614D44413C36
343655616C6C61504A443F3939365564
72726150504A3F3F39396C727272725E
58504A4444446C72727272665B55504A
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

ONE OFF THE NET:
023B0624500BDA398D00FA23C1070CCD
0666010000E61004D82D0CCD08080808
0808080808110077FFF518182C181071
0171FF00000C39393939393939393939
39393939393939393939393939393939
44444444413F3C39393939414A4A4A44
413E3C39393939475050504A4744413F
3C3939475B5B5B524D44413939394761
675E5B52504D413C393955616961615B
55504A44393955616C66665E5B554D44
3C3955616C666663585047413F395561
6C66665B52504A3F3C3655616C636355
4D47443C363455616C61614D44413C36
343655616C6C61504A443F3939365564
72726150504A3F3F39396C727272725E
58504A4444446C72727272665B55504A
4A4AC0000C7272727272665B55504A4A


Seems everything compares but those lines. I tried pushing a pin into the top of each socket and read it. Same result.

Doesn't matter much now since I'm erasing it. I'll put in a flash chip tomorrow whether it burns tonight as a 27C256, or not.

If anyone else has this problem with a new AUJP maybe they'll find this thread and not be so confused. There might just be some bad ones from GM??? Heck, I'm going to order another one just to see if it happens again! Three chip for tuning fits my program pretty well. One in the ECM, one in the glove box that I *KNOW* works well, and one to make changes after reading all this info each night on 730 tuning.

Thanks for the reply!



------------------
_ ___ _
SMasterson

SMasterson

Glenn, just an update. Erased the chip via UV and reprogrammed it. Worked fine and compared three times. Even filled the buffer with FF, reloaded file into the buffer, then verified it. Worked prefect. Seems like it was programmed wrong to start with???



------------------
_ ___ _
SMasterson

Grumpy

Hmm, maybe they were nuked in shipment.
I'd try erasing one, and reprogramming it with a stock correct .bin, and try that.

If it doesn't erase, or program correctly and your other 256 are fine, then they were defective. Over the years, I think I've had 2 bad new ones, but that's out of hundreds of chips.

Grim Reaper

It's the only thing that makes sense.

Maybe the eprom was improperly programmed, got exposed to UV or got zapped by some static electricity.

Seems the eprom itself is fine, and that's the important thing.

Sarkee

...But what about the limp-home chip(s)??? If an external malady like electrostatic contamination, then limp-home may be shot, too???

Any way to check the limp-home chips??? (Besides the obvious one!)