DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
OK so Friday I tried burning my first chip and it went well except when I put it in my car immediately went into limp home mode. Found out I put in the chip backwards so I turned it around and no change. I even emulated the stock tune back to the computer and no change, take the chip out entirely and no change. I can't get anything in my datalog except a bunch of troublecodes and my O2 sensor readings. Did I fry my ECM by putting the chip in backwards the first time?
Trouble Codes:
Bad PROM
Faulty ECM
System voltage too high
Fuel pump voltage too low
Low coolant Temp
High coolant Temp
This ad is not displayed to registered members. Register your free account today and become a member on ThirdGen!
Sponsored Links
Registered users do not see this ad. Click here to register for free!
__________________ -Jeremy- EFI Calibration Engineer, Director of R&D, Software Designer (Fuel Injection Technologies - dianpen.com) - still in China since Nov '04!!!
86 Z28 - rusty, tired, and in storage - 89 GTA with plans, but - also in storage now needs paint - badly, 79 Malibu classic with 91 L98, 4L60, 3.73
What is your setup?
Are you using $6E in a '165, $32B in a '165, $8D in a 730, or some TBI, or something else?
I tried to attach a picture of Mask ID in tunerpro, but it's not attaching (no it's not too big or anything stupid like that). Basically, Mask ID is the second item in the Constants list.
Last edited by RednGold86Z; 08-21-2006 at 11:02 PM.
See what's at location 08. Change it to AA and try that. Also, yeah, make sure you're stacking stuff right (easiest way), or at least starting at the bin at the right offset, and loading the buffer right, etc...
__________________ -Jeremy- EFI Calibration Engineer, Director of R&D, Software Designer (Fuel Injection Technologies - dianpen.com) - still in China since Nov '04!!!
86 Z28 - rusty, tired, and in storage - 89 GTA with plans, but - also in storage now needs paint - badly, 79 Malibu classic with 91 L98, 4L60, 3.73
E6 is the computer for a 93 tbi truck, i'll upload a screenshot of what i see tomorrow, because i don't see mask ID anywhere in the constants
Open TunerPro, hit Ctrl + H, and look at location (address) 0x08. It should say E6. If it does, change it to AA.
However, I don't think this is likely to fix your issue. You mention that you "emulated your stock chip." What does that mean? That you uploaded the stock chip to the emulator and tried? Or did you put your stock chip back in? If the former, remove the emulator from the equation and physically put your stock chip back in the ECM and see if it works. If the latter (you tried your physical stock chip), then your ECM might be dead.
The mask ID is definetly at L4008. See the attached pics. You need to setup TunerPro to calculate the checksum correctly. Hit CTRL-F2 to see the XDF header info and set it ilke the first pic. If you are using TunerProRT you will also need to set emulation to disable the checksum by loading AA al 4008 in the ALDL/Emulation section of the "Preferences" tab under the tools menu. See the second pic. HTH
__________________ If it doesn't make it go fast, stop fast, or look cool, its fluff!
Your reading something wrong or dumping the wrong locations from the base file your using. Should not be FF everywhere.
For the $E6 mask (64KB, 27C512), $FF is normal for locations L0000 to L3FFF. The calibration does not start until L4000. Checksum is a double byte at L4006. Mask ID at L4008. HTH
ok i guess i was just kidding about that statement earlier, it drove like a bat out of hell on saturday and when i started it up this morning it died, then on the next start it went into limp home mode. disconnected the computer for the rest of the day at work, and when i went to drive it home plugged it back in and it drove fine for about 10 seconds then screwed up again. guess i'll try lookin at the code again tonight