Problems after g2 install
Problems after g2 install
Hey guys, I can't seem to get my ecm to work after I installed my G2 adapter & AT29C256 chip on my 8063 ecm. I soldered my adapter in (not pretty looking) loaded my chip with the 4k bin with the offsets on Moates site. I hook the ecm up and turn the key to on and the ses light flickers on and off which I read could be a prom error?? Am I not loading the bin onto the chip right??
I've used these offsets
File Size Chip Buffer Start -> End Chip Start -> End
4k (4096) AT29C256 000000 -> 000FFF 007000 -> 007FFF
I've used these offsets
File Size Chip Buffer Start -> End Chip Start -> End
4k (4096) AT29C256 000000 -> 000FFF 007000 -> 007FFF
Supreme Member
Joined: Mar 2001
Posts: 6,577
Likes: 0
From: Portland, OR www.cascadecrew.org
Car: 1990 Camaro RS
Engine: Juiced 5.0 TBI - 300rwhp
Transmission: T5
Axle/Gears: 3.42 Eaton Posi, 10 Bolt
Is the bin you are using known to be good?
I'm sure you've already checked it, but the chip is not in backwards is it?
FWIW, I never use offsets, because I never get them right. ;-) I just stack the bin into a 16k bin, you might give that a try, and see if it works. My first guess is that your bin is bad though.
I'm sure you've already checked it, but the chip is not in backwards is it?
FWIW, I never use offsets, because I never get them right. ;-) I just stack the bin into a 16k bin, you might give that a try, and see if it works. My first guess is that your bin is bad though.
Senior Member
Joined: Oct 1999
Posts: 6,621
Likes: 2
Car: 91 Red Sled
Axle/Gears: 10bolt Richmond 3.73 Torsen
What are you using to edit the bin? Sounds like a bad checksum and I think you had a typo when you said "AT29C256 000000 -> 000FFF 007000 -> 007FFF" it should be AT29C256 000000 -> 007FFF 007000 -> 007FFF.
E-mail me your bin and I'll check the checksum out for you.
E-mail me your bin and I'll check the checksum out for you.
No it wasn't a typo thats what I was using to load the bin. I tried to load it by the offset you said JPrevost but the numbers keep changing to something different automatically in the addressing box. Im using Tunerpro to edit and FlashnBurn to load the bin.
I emailed you my bin file.
I emailed you my bin file.
Senior Member
Joined: Oct 1999
Posts: 6,621
Likes: 2
Car: 91 Red Sled
Axle/Gears: 10bolt Richmond 3.73 Torsen
Yeah, your checksum was wrong. I sent you that bin with a correct checksum. See if that works for you and if so, send me your ecu file and I'll get the checksum working. There was a problem with TunerPro and doing 16-bit checksums in these bins.
If you ever want to do your own checksum checks manually here's how I did it. I opened your bin with Hex Workshop and looked for your mask ID. It's 4D, that was in the correct location (0004), select that byte and all the rest till the end. Run a 16-bit checksum and see if it matchs the 1st 2 bytes in the bin (locations 0000 and 0001, remember, 2 bytes = 16-bit). The bin you sent me has 96 C9, it should be 8D 2A. Another quick fix is to change the mask ID (location 0004) to AA. This will disable the checksum routine from forcing limp home mode. No more code 51. Since code 51 "improperly installed prom (aka chip)" is a stored code it will still be in the memory of the computer for a while. Ignore it if the SES light is off
.
You've got mail.
edit: Almost forgot, you're right, it is 000000-000FFF, that's the chip address, not the chip size
If you ever want to do your own checksum checks manually here's how I did it. I opened your bin with Hex Workshop and looked for your mask ID. It's 4D, that was in the correct location (0004), select that byte and all the rest till the end. Run a 16-bit checksum and see if it matchs the 1st 2 bytes in the bin (locations 0000 and 0001, remember, 2 bytes = 16-bit). The bin you sent me has 96 C9, it should be 8D 2A. Another quick fix is to change the mask ID (location 0004) to AA. This will disable the checksum routine from forcing limp home mode. No more code 51. Since code 51 "improperly installed prom (aka chip)" is a stored code it will still be in the memory of the computer for a while. Ignore it if the SES light is off
.You've got mail.
edit: Almost forgot, you're right, it is 000000-000FFF, that's the chip address, not the chip size
Last edited by JPrevost; May 3, 2005 at 09:11 PM.
TGO Supporter
Joined: Jan 2000
Posts: 1,861
Likes: 0
From: In your ear. No, the other one.
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
Originally posted by JPrevost
There was a problem with TunerPro and doing 16-bit checksums in these bins.
There was a problem with TunerPro and doing 16-bit checksums in these bins.
In any case, make sure you're always using the latest version.
Alright ive stacked my 4k bin into a 32k bin in Tunerpro. Erased the chip and did a blank check. Loaded the bin to the buffer and programed the chip. Verified that the chip took the bin and that was ok. Hooked the ecm up and still got a flashing ses light. I don't get whats going on or maybe Im doing something wrong. Maybe I screwed up my ecm soldering the adapter in???
Trending Topics
TGO Supporter
Joined: Jan 2000
Posts: 1,861
Likes: 0
From: In your ear. No, the other one.
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
Originally posted by kidcamarosc
Maybe I screwed up my ecm soldering the adapter in???
Maybe I screwed up my ecm soldering the adapter in???
Thread
Thread Starter
Forum
Replies
Last Post
Pac J
Tech / General Engine
3
May 17, 2020 10:44 AM




Got it to work. Cleaned up my soldering job a little and did a fresh burn on the chip and got her to fire up. Now the fun stuff begins!!! 
