08 STi ROM

gabedude · **Posted:** Fri Aug 15, 2008 4:57 pm

There is a new SOA flash that came in a TSB about high rpm overboost for certain 08 STI models that can cause "broken ringlands". My friend who is the perf specialist at the dealership here in town told me about it. Once the new cable comes out, I'll get a copy. I also have access now to get copies of all the CanBus roms (once I have the new cable and software).

-Gabe

Fiend · **Joined:** Tue Apr 24, 2007 10:49 pm **Posts:** 243

I just ordered the new cable and should have it next week. I have a CDN '08 STI and haven't gone in for the reflash yet. I want to download the stock image first then the modified one (I'm already running AP stage 1 93 anyhow...but I'm curious).

I can submit the images next week if it would help.

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

We don't allow Cobb images or any other commercial maps to be posted, so you can only post the factory ROM. Cobb recently started locking out the ECU with AP ver. 2, so you may not be able to do anything with it until you unmarry.

Fiend · **Joined:** Tue Apr 24, 2007 10:49 pm **Posts:** 243

merchgod wrote:

We don't allow Cobb images or any other commercial maps to be posted, so you can only post the factory ROM. Cobb recently started locking out the ECU with AP ver. 2, so you may not be able to do anything with it until you unmarry.

I wasn't planning on posting the Cobb maps, I just wanted to provide the stock ROMs (before and after reflashing).

So Cobb has started locking out the ECU now too (ala ECUTek)? Great...at least I know I can still datalog as my OP1.3 works fine. The OP2 cable should still be great for datalogging because you don't need to tote a laptop around; well, that is, once Colby gets that feature up and running.

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

Fiend wrote:

merchgod wrote:

We don't allow Cobb images or any other commercial maps to be posted, so you can only post the factory ROM. Cobb recently started locking out the ECU with AP ver. 2, so you may not be able to do anything with it until you unmarry.

I wasn't planning on posting the Cobb maps, I just wanted to provide the stock ROMs (before and after reflashing).

So Cobb has started locking out the ECU now too (ala ECUTek)? Great...at least I know I can still datalog as my OP1.3 works fine. The OP2 cable should still be great for datalogging because you don't need to tote a laptop around; well, that is, once Colby gets that feature up and running.

We do have the 08 STi ROM before and after the recall (cal ids AZ1G201I AND AZ1G202I) that were pulled by the beta testers.

Fiend · **Joined:** Tue Apr 24, 2007 10:49 pm **Posts:** 243

merchgod wrote:

We do have the 08 STi ROM before and after the recall (cal ids AZ1G201I AND AZ1G202I) that were pulled by the beta testers.

Awesome, now get back to work on decoding them.

In all seriousness, are the definitions attached to the first post in this thread the latest for the '08?

By the way, thank you for taking the time to reply to Crawford's thread on IWSTI. It seems there is a lot of misinformation being tossed about in that thread and it is nice to have someone that really knows what they are talking about keep things in check.

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

Fiend wrote:

Awesome, now get back to work on decoding them.

In all seriousness, are the definitions attached to the first post in this thread the latest for the '08?

Only the ROM is attached to the first post - I removed the definitions since the OP 2.0 is being released and they were only preliminary defs - not to tune with.

altaic · **Joined:** Tue Oct 23, 2007 8:27 am **Posts:** 26

merchgod wrote:

We do have the 08 STi ROM before and after the recall (cal ids AZ1G201I AND AZ1G202I) that were pulled by the beta testers.

Would you post AZ1G202I, please? I'd like to run a program I've written on it so I can start adding a compare functionality.

Fiend · **Joined:** Tue Apr 24, 2007 10:49 pm **Posts:** 243

merchgod wrote:

Only the ROM is attached to the first post - I removed the definitions since the OP 2.0 is being released and they were only preliminary defs - not to tune with.

Out of curiosity, when do you expect the new definitions to be available? Sorry for all the questions.

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

Probably in about 3 weeks, hopefully, maybe sooner, maybe later. As far as posting more canbus ROMs, I'm a little leary as there appears to be a byte sequence in these ROMs that is possibly unique to the car. I don't know if that can be traced back to the car by a dealership - I doubt it, but I would rather see more ROMs of the same revision and perhaps decipher what it is used for before uploading them.

Jon [in CT] · **Posted:** Fri Sep 05, 2008 8:57 pm

merchgod wrote:

I'm a little leary as there appears to be a byte sequence in these ROMs that is possibly unique to the car. I don't know if that can be traced back to the car by a dealership - I doubt it, but I would rather see more ROMs of the same revision and perhaps decipher what it is used for before uploading them.

It's conceivable those bytes are written when the VIN is stored in another part of the ECU and are VIN-specific. If so, you'd probably need the last 8 digits of the VIN from which the ECU was pulled in order to decipher those ROM bytes.

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

Jon [in CT] wrote:

It's conceivable those bytes are written when the VIN is stored in another part of the ECU and are VIN-specific. If so, you'd probably need the last 8 digits of the VIN from which the ECU was pulled in order to decipher those ROM bytes.

Actually, I forgot Colby had said the following recently in comparison of the 08 STi original rom and recall rom:

Quote:

Once thing I noticed in quick diff of the ROMs is that the 3 bytes at addresses 0x02024 and 0xC0020 appear to encode the ROM version date in a YY MM DD BCD format. That is, the first ROM version is 2007/10/12 and the second is 2008/06/27.

Although I don't know why two identical ROMs would have different dates, which was the case with two of the 08 STi non-recall ROMs that were pulled in the past.

bigdweeb · **Posted:** Sat Sep 06, 2008 12:45 am

merchgod wrote:

Jon [in CT] wrote:

It's conceivable those bytes are written when the VIN is stored in another part of the ECU and are VIN-specific. If so, you'd probably need the last 8 digits of the VIN from which the ECU was pulled in order to decipher those ROM bytes.

Actually, I forgot Colby had said the following recently in comparison of the 08 STi original rom and recall rom:

Quote:

Once thing I noticed in quick diff of the ROMs is that the 3 bytes at addresses 0x02024 and 0xC0020 appear to encode the ROM version date in a YY MM DD BCD format. That is, the first ROM version is 2007/10/12 and the second is 2008/06/27.

Although I don't know why two identical ROMs would have different dates, which was the case with two of the 08 STi non-recall ROMs that were pulled in the past.

Could it perhaps be some routine that gets run when the ECU is flashed with a new image? Once the image is verified it changes the date in that memory location? That would be a pretty easy way for a dealership to see if an ECU was being reflashed to be tuned or reflashed back to stock before a visit for service.

They would know roughly what dates should show up for the stock ROM (AZ1G201I should show a date just before the chassis build date) and they would know what date the recall ROM was flashed (AZ1G202I should show the date of the service visit). If the dealership checks a ROM and the flash date was incorrect, they would know something's up.

That's all speculation since I don't know if it's even feasible given the reflash routines. Just throwing it out there...

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

bigdweeb wrote:

Could it perhaps be some routine that gets run when the ECU is flashed with a new image? Once the image is verified it changes the date in that memory location? That would be a pretty easy way for a dealership to see if an ECU was being reflashed to be tuned or reflashed back to stock before a visit for service.

No, because the date was June something on the recall flash and it was just flashed like a week ago.

bigdweeb · **Posted:** Sat Sep 06, 2008 1:25 am

merchgod wrote:

bigdweeb wrote:

Could it perhaps be some routine that gets run when the ECU is flashed with a new image? Once the image is verified it changes the date in that memory location? That would be a pretty easy way for a dealership to see if an ECU was being reflashed to be tuned or reflashed back to stock before a visit for service.

No, because the date was June something on the recall flash and it was just flashed like a week ago.

Ah, didn't pay that close attention to the dates when I read it. Just a gut guess anyway. Interested to see what you find!

RomRaider

08 STi ROM

Who is online