ECUFlash - Getting close!

[Sportsguy83]

Originally Posted by jsimon7777

So I pulled the stock ROM with Ecuflash. No problems. My car has the ZA1JA01C ROM from the factory. However, Ecuflash has no definitions for the file.

Then I open the openflash ZA1JA01C ROM. No definitions. Wants me to develop them. No go.

Then I open the ZA1JA00C rom. It says the checksum needs to be corrected. My understanding is that correcting this then flashing is what bricked Skullworks's car.

Questions then.

Can I flash the ZA1JA00C rom?
Should I modify the definitions file in some way to get the ZA1JA01C rom to flash? I believe they're the same ROM with a slightly different name. Or perhaps I'm adding the wrong ecu defs somehow. I don't think I am, though.
Should I fix the checksum? My understanding is a big NO.

Thanks! My intention is to make a guide for this to make it easier for others.

@Td-d @mad_sb @jamesm

[ztan]

Originally Posted by jsimon7777

So I pulled the stock ROM with Ecuflash. No problems. My car has the ZA1JA01C ROM from the factory. However, Ecuflash has no definitions for the file.

Then I open the openflash ZA1JA01C ROM. No definitions. Wants me to develop them. No go.

Then I open the ZA1JA00C rom. It says the checksum needs to be corrected. My understanding is that correcting this then flashing is what bricked Skullworks's car.

Questions then.

Can I flash the ZA1JA00C rom?
Should I modify the definitions file in some way to get the ZA1JA01C rom to flash? I believe they're the same ROM with a slightly different name. Or perhaps I'm adding the wrong ecu defs somehow. I don't think I am, though.
Should I fix the checksum? My understanding is a big NO.

Thanks! My intention is to make a guide for this to make it easier for others.

Make a copy of the A00 .xml definitions file and change any A00 to A01 in the <romid> section

If you open a ROM file which has been checksum corrected by RomRaider in EcuFlash, it will sometimes tell you the checksum is incorrect. RomRaider adds some date data at the end of the checksum block (view in a Hex editor) when it corrects a checksum. If you reset the date data all to FF, EcuFlash then is happy with the checksum.

[Td-d]

The definition are available, not need to recreate:

Romraider: https://raw.github.com/TD-D/SubaruDe...R_ZA1JA01C.xml
Ecuflash: https://raw.github.com/TD-D/SubaruDe...Z/ZA1JA01C.xml

[EAGLE5]

Originally Posted by Td-d

The definition are available, not need to recreate:

Romraider: https://raw.github.com/TD-D/SubaruDe...R_ZA1JA01C.xml
Ecuflash: https://raw.github.com/TD-D/SubaruDe...Z/ZA1JA01C.xml

Wow, thanks! The last question is, should I correct the ROM checksum in ROM Raider or EcuFlash or neither before flashing it to the car?

Oh yeah, and it's odd that the 00C definitions are like 622K ut the 01C is only like 44K. Am I missing something?

[Td-d]

Originally Posted by jsimon7777

Wow, thanks! The last question is, should I correct the ROM checksum in ROM Raider or EcuFlash or neither before flashing it to the car?

Oh yeah, and it's odd that the 00C definitions are like 622K ut the 01C is only like 44K. Am I missing something?

I would correct it in Romraider - the only difference is the time stamp as mentioned.

The difference in the size is that the 44kb definition bundled is actually for Ecuflash (which are much smaller) - not RR, hence it did not work.

[EAGLE5]

I have attached a log showing my success and failure. Here is my outline of it. I am running XP with a Tactrix 2.0 Rev E:

1. Stock ROM - ECUFlash successfully downloads the ROM into memory.
2. Open Vishnu's Stg 1 tune in ROM Raider. Save as to give new checksum.
3. Write ROM to car. Gets an error at the end of writing:
[00:40:52.330] checksum routine start refused.
[00:40:52.330] interface close
4. Try to read ROM:
[00:41:15.794] OBDII communications failed - trying OEM bootloader...
[00:41:15.824] OEM bootloader communications failed.
[00:41:15.834] interface close
5. Power off car. Power on. Try again. Same error.
6. Start engine. Works great. Amazing tuning, Shiv! Freaking amazing. When you hit 4k rpm, VTEC kicks in, yo! So I drive around. Car works great. Come back to garage.
7. Try to write stock ROM that is still loaded in ECU Flash. Get an error:
[01:10:15.064] writing area 00008000-0013FEFF...
[01:11:50.261] J2534 error [ERR_TIMEOUT].
[01:11:50.261] download transfer failure at address 0012EF00.
[01:11:50.271] interface close
8. Shut off car. Turn back on. Try to start engine. NOTHING. Oh dear.
9. Reflash Stg 1 tune. Get same error:
[01:15:42.655] checksum routine start refused.
10. Shut off. Turn on. Engine starts.

So I have Shiv's tune installed and running. However, I cannot read the ROM nor go back to stock. Ideas?

Thanks!

[Td-d]

Hmm... I suggest you give MikeyPSF a shout (on the RR forum via PM or email) so that you can get the beta version that Colby organised for Skullworks, I'm sure that will sort it out.

[Td-d]

I've also just thought of something - when you say you have Shiv's tune on there, did you copy the maps across to the stock rom that you pulled over from Ecuflash from Shiv's rom, or just use the OFT rom? You must remember that whilst the OFTtunes are out in the open, the OFT is not open source - I believe that the OFT is locked to one vehicle (through VIN verification of some sorts I would expect), so there is obviously some custom code that has been inserted to undertake this. Perhaps this is what is causing the issue - Rombinhood@OpenFlash, perhaps you can clarify?

[EAGLE5]

Originally Posted by Td-d

I've also just thought of something - when you say you have Shiv's tune on there, did you copy the maps across to the stock rom that you pulled over from Ecuflash from Shiv's rom, or just use the OFT rom? You must remember that whilst the OFTtunes are out in the open, the OFT is not open source - I believe that the OFT is locked to one vehicle (through VIN verification of some sorts I would expect), so there is obviously some custom code that has been inserted to undertake this. Perhaps this is what is causing the issue - Rombinhood@OpenFlash, perhaps you can clarify?

I did try the OFT ROM directly. It's all new and crazy, is it not? It is not locked down to a specific car, apparently, because it did work so far, but there is some sort of incompatibility. I have not had a chance to play with it as I did try to get some sleep. Probably Sunday or Monday I'll explore more.

[SkullWorks]

Originally Posted by jsimon7777

I have attached a log showing my success and failure. Here is my outline of it. I am running XP with a Tactrix 2.0 Rev E:

1. Stock ROM - ECUFlash successfully downloads the ROM into memory.
2. Open Vishnu's Stg 1 tune in ROM Raider. Save as to give new checksum.
3. Write ROM to car. Gets an error at the end of writing:
[00:40:52.330] checksum routine start refused.
[00:40:52.330] interface close
4. Try to read ROM:
[00:41:15.794] OBDII communications failed - trying OEM bootloader...
[00:41:15.824] OEM bootloader communications failed.
[00:41:15.834] interface close
5. Power off car. Power on. Try again. Same error.
6. Start engine. Works great. Amazing tuning, Shiv! Freaking amazing. When you hit 4k rpm, VTEC kicks in, yo! So I drive around. Car works great. Come back to garage.
7. Try to write stock ROM that is still loaded in ECU Flash. Get an error:
[01:10:15.064] writing area 00008000-0013FEFF...
[01:11:50.261] J2534 error [ERR_TIMEOUT].
[01:11:50.261] download transfer failure at address 0012EF00.
[01:11:50.271] interface close
8. Shut off car. Turn back on. Try to start engine. NOTHING. Oh dear.
9. Reflash Stg 1 tune. Get same error:
[01:15:42.655] checksum routine start refused.
10. Shut off. Turn on. Engine starts.

So I have Shiv's tune installed and running. However, I cannot read the ROM nor go back to stock. Ideas?

Thanks!

This is strange...

I will attempt to read my ECU afterwork today. I am currently running Shiv's OFT E85 map on my car,

I have had success flashing and running the car with and without letting ECUflash correct the checksum error.

[01:11:50.261] J2534 error [ERR_TIMEOUT].
[01:11:50.261] download transfer failure at address 0012EF00.
This is the same errors I was getting that left me immobile for weeks, but it would give this error regardless of what I tried to flash, Stock, OFT stage 1, made no difference. I still get this error on occasion, but it wll retry several times now before terminating the flash...It has completely failed to flash 2X but subsequent attempts have allowed success...let me tell you, there was severe pucker factor while parked at McDonalds uploading E85 maps for the first time...and I kept getting failures...I was wigging out bad, then i got a clean flash and all was unicorns and pixie dust and stuff...

[SkullWorks]

Originally Posted by Td-d

I've also just thought of something - when you say you have Shiv's tune on there, did you copy the maps across to the stock rom that you pulled over from Ecuflash from Shiv's rom, or just use the OFT rom? You must remember that whilst the OFTtunes are out in the open, the OFT is not open source - I believe that the OFT is locked to one vehicle (through VIN verification of some sorts I would expect), so there is obviously some custom code that has been inserted to undertake this. Perhaps this is what is causing the issue - Rombinhood@OpenFlash, perhaps you can clarify?

I expected this to be feature of the hardware, recognizing the Vin of the vehicle...I'm not sure I understand why the Rom would need to be different, I didn't see any instruction in the OFT threads about needing to copy the maps over to the factory image, Just that the factory image is stored in the device until it is "unmarried"

[EAGLE5]

Do you fix any checksums before flashing? Which program? Did you use the romraider provided defs for romraider or the vishnu supplied defs?

Originally Posted by SkullWorks

This is strange...

I will attempt to read my ECU afterwork today. I am currently running Shiv's OFT E85 map on my car,

I have had success flashing and running the car with and without letting ECUflash correct the checksum error.

[01:11:50.261] J2534 error [ERR_TIMEOUT].
[01:11:50.261] download transfer failure at address 0012EF00.
This is the same errors I was getting that left me immobile for weeks, but it would give this error regardless of what I tried to flash, Stock, OFT stage 1, made no difference. I still get this error on occasion, but it wll retry several times now before terminating the flash...It has completely failed to flash 2X but subsequent attempts have allowed success...let me tell you, there was severe pucker factor while parked at McDonalds uploading E85 maps for the first time...and I kept getting failures...I was wigging out bad, then i got a clean flash and all was unicorns and pixie dust and stuff...

[Td-d]

Skullworks - maybe send jsimon7777 the beta version of Ecuflash that Colby sorted you out with, see if that helps?

[ztan]

Originally Posted by SkullWorks

I expected this to be feature of the hardware, recognizing the Vin of the vehicle...I'm not sure I understand why the Rom would need to be different, I didn't see any instruction in the OFT threads about needing to copy the maps over to the factory image, Just that the factory image is stored in the device until it is "unmarried"

I agree this is likely to be the problem - when using the OFT, the checksum correction + anything else needing to be corrected gets processed by the OFT or OFT manager.

For my successful flashing, I was using EcuFlash brzBeta 1.44.3948, changes to my stock ROM made in TunerPro and RomRaider, checksum corrected in RomRaider, date stamp removed in Hex editor (so EcuFlash woudn't bother me), and written with EcuFlash.