I have burnt a few proms...I am seeing an error flag set 51 PROM error. I don't see an SES light though, I only see the error in the software (Moates and WinALDL). It doesn't seem to affect anything except as noted below.

I also get a a problem receiving data...the program runs fine until I jump on the gas pedal then I stop getting data (usually 3300-4000 rpms). Sometimes after a few minutes it "comes back". I don't know if its related to the PROM error, but they seem to have showed up at the same time..it really bits since I can't get the logging to work over a certain RPM.

A couple of things I am using the moates switcher, with a customized (timing, fan temps ) ARAP bin. I did change the prom id so that i could see what program was running via the switcher...I have tried the stock bin and I see the same error...I guess I could take the ecm out and remove the switcher....

Anyone seen this?

 

You sure about your binary locations and offsets? It sounds like you have the info tucked in the wrong PROM space. You need it in the 'top' of each 32k slot. Check the settings on the MansurWare stacker...

 

Hmm...Top meaning the higher address space? I am using BinStacker in GMECEdit and now TunerPro...

Let see Chip Size 512K, Bin Size 16K, block size 32K..offset within block is $4000

So that would be:

Pos 0: address $78000 - $80000, with the .bin offset by $4000 its between $80000 and $7C000 right...

In fact looking at the prom...the space between $78000 and $7C000 is all 0s.

....

Pos F: 0 - $8000,
0-$3FFF = 0s
$4000 - $7FFF = the bin

But if that wasn't right wouldn't I get all kinds of problems? Not just the err 51? But my timing and settings should be all screwed up..I wouldn't even see the prom id in the scanning software....

 

Sorry, I didn't read closely enough. Don't know what the issue could be. No SES light? Weird.

 

well I cleared the codes, after reseating the switcher and and cal pak. The Prom error no longer comes up, but I still the hang...interestingly the "data" comes back when I come to a complete stop...it almost seems like the ECM is too busy or there is some sort of data timing problem. I guess the only thing I could think of is that my laptop is too fast (1.8 Ghz) running DOS and might cause some serial issues...I am gonna try it with a slower laptop.