Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging

[steve99]

Originally Posted by lizbrayan

I have a A01C rom, can I flash the B01C rom instead? Since I saw in the first page that its compatible I just want to make sure I read it right.

Yes you can flash B01C roms to A01C cars, B01C is latest factory base map for those cars

[Tor]

Originally Posted by steve99

WARNING : Always make sure your definition file matches your ROM. Do NOT rely on the name of the ROM file. The internal Calibration ID may not be the same as the file name.
Always open the ROM in ECUFLASH and check some tables such as the "Primary Open Loop Fuel Table" and the "Base Timing B" check that the values in these tables look ok and the table Axis both X and Y look ok. If they don't then it likely that the Definition file and the ROM are mismatched. If you FLASH or EDIT a ROM using an incorrect Definition you WILL Brick your ECU.

I am trying to write a guide in German and was trying to deliberately open a wrong ROM with EcuFlash to make a screenshot of what a garbled "Base Timing B" table would look like.

To my surprise it looked fine. OL fueling too.

Specifically what I have/did:

- EcuFlash A00G and A01G defs in the 2012 folder.
- Loaded OFT OTS A00G

Since OFT OTS A00G is Calid manipulated I expected to see errors in the tables. But they were both fine!!

Then I looked in the "ROM Info" section and see the Calid is mention 3 times.
ECU ID: ZA1JA00G
Internal ID: ZA1JA00G
Inherits: ZA1JA01G

Also notice the log entries:

using metadata XML ID ZA1JA00G from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/BRZ/2012/ZA1JA00G.xml
which inherits XML ID ZA1JA01G from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/BRZ/2012/ZA1JA01G.xml
which inherits XML ID 32BITBASE from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml

Then I tried to remove the A01G definition and open the A00G ROM again. This time I had no tables showing up at all:



I also tried to open an A02G ROM for which I have no definitions at all. I got an error message:




This might be an unusual question: But how do I get it wrong? Or what am I doing right?

Is it possible that EcuFlash got smarter since this info was written and is actually capable of recognizing and correcting a Calid modified ROM?

[steve99]

Originally Posted by Tor

I am trying to write a guide in German and was trying to deliberately open a wrong ROM with EcuFlash to make a screenshot of what a garbled "Base Timing B" table would look like.

To my surprise it looked fine. OL fueling too.

Specifically what I have/did:

- EcuFlash A00G and A01G defs in the 2012 folder.
- Loaded OFT OTS A00G

Since OFT OTS A00G is Calid manipulated I expected to see errors in the tables. But they were both fine!!

Then I looked in the "ROM Info" section and see the Calid is mention 3 times.
ECU ID: ZA1JA00G
Internal ID: ZA1JA00G
Inherits: ZA1JA01G

Also notice the log entries:

using metadata XML ID ZA1JA00G from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/BRZ/2012/ZA1JA00G.xml
which inherits XML ID ZA1JA01G from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/BRZ/2012/ZA1JA01G.xml
which inherits XML ID 32BITBASE from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml

Then I tried to remove the A01G definition and open the A00G ROM again. This time I had no tables showing up at all:



I also tried to open an A02G ROM for which I have no definitions at all. I got an error message:




This might be an unusual question: But how do I get it wrong? Or what am I doing right?

Is it possible that EcuFlash got smarter since this info was written and is actually capable of recognizing and correcting a Calid modified ROM?

Yes correct some rom changes are just data table changes this appears to be what happened between A00G A01G and A02G . If only data table changes made, and these may be in undefined tables in rom, remember their are lokely hundreds of undefined tables or parameters we dont knowabout. Then the structure of rom remains constant and tables usually end up in same place, although its possible that the undefined tables may have moved and we dont see them.

When their is code changes then all or most of the tables get shifted arround try the same with say a D00G and an A01G, the oft guys dont do that change but will show weird tables. We are lucky with A01G roms and this is why few people brich their ecu, the usa guys need to be very carefull as they had several updates thet shifted tables with their 900C A00C and B01C from memory its the A00C to B01C transition thats the issue.

[Tor]

Originally Posted by steve99

Then the structure of rom remains constant and tables usually end up in same place, although its possible that the undefined tables may have moved and we dont see them.

Thanks for the info. So what would be the best advice for G users to check if their ROM and defs match up?

It seems that looking at Base Timing B and OL fueling, isn't reliable in this case?

Would it instead be a good advice to tell people to check the "ROM info" that "ECU ID", "Internal ID" and "Inherits" is the same?

Are these 3 the same IDs the same that you would get from opening the ROM with a Hex-editor and doing a search for the Calid?

[steve99]

Originally Posted by Tor

Thanks for the info. So what would be the best advice for G users to check if their ROM and defs match up?

It seems that looking at Base Timing B and OL fueling, isn't reliable in this case?

Would it instead be a good advice to tell people to check the "ROM info" that "ECU ID", "Internal ID" and "Inherits" is the same?

Are these 3 the same IDs the same that you would get from opening the ROM with a Hex-editor and doing a search for the Calid?

Yes best way is to open rom with hex editior and check all 3 calid are same like in a stock rom.

Only flash roms with tactrix where all three calid same

always check tables anyway

only have the ecuflash definition for your intended rom in the ecuflash defs area this will stop you un intentionally flashing or opening incorrect calid roms.

A01G is best rom to flash for early cars, well supported and is not calid hacked buy oft guys.

[Tor]

Originally Posted by steve99

Yes best way is to open rom with hex editior and check all 3 calid are same like in a stock rom.

Are those the same 3 Calid shown in "ROM info" in EcuFlash?

Some people wouldn't know how to use a Hex-editor, so I am trying to make as simple instructions as possible.

[steve99]

Originally Posted by Tor

Are those the same 3 Calid shown in "ROM info" in EcuFlash?

Some people wouldn't know how to use a Hex-editor, so I am trying to make as simple instructions as possible.

Unfortunatly no

Both ecuflash and romraider only check the calid string at hex location 8000.

However the other two at 10000 and arround 11000 are not checked.

this is where problem occurrs oft guys alter the first two calid to make rom look like a different rom for oft, but the third calid is the one that shows true rom id, romraider and ecuflash get fooled and then problems occurr.

If people just want to flash without editing you could make up a bare bones definition that was flash only for ecu flash.

i wrote a very simple batch tool (windows) to check all three calid are same, wayne wrote a better one

[Tor]

Originally Posted by steve99

Unfortunatly no

Both ecuflash and romraider only check the calid string at hex location 8000.

However the other two at 10000 and arround 11000 are not checked.

this is where problem occurrs oft guys alter the first two calid to make rom look like a different rom for oft, but the third calid is the one that shows true rom id, romraider and ecuflash get fooled and then problems occurr.

How did EcuFlash see the need to load up the A01G definition for the OTS A00G ROM in the example above with the screenshots?

That really puzzles me.

Originally Posted by Tor

Also notice the log entries:

using metadata XML ID ZA1JA00G from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/BRZ/2012/ZA1JA00G.xml
which inherits XML ID ZA1JA01G from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/BRZ/2012/ZA1JA01G.xml
which inherits XML ID 32BITBASE from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml

[steve99]

Originally Posted by Tor

How did EcuFlash see the need to load up the A01G definition for the OTS A00G ROM in the example above with the screenshots?

That really puzzles me.

have a look in the def directories and subdirectories to see you dont have multiple def in their ie the brz/2012 2013 2014 or anywhere else in that subdirectory, ecuflash searches tat directory tree for defs

it will just load the first one it finds with matching calid to rom at 8000 hex

just like romraider

again this can trap you if you have multiple defs especially mix of oft defs and standard defs

[steve99]

Rom check tool windows batch file, just unzip it and place it in directory with your roms to check calid

[Tor]

Originally Posted by steve99

have a look in the def directories and subdirectories to see you dont have multiple def in their ie the brz/2012 2013 2014 or anywhere else in that subdirectory, ecuflash searches tat directory tree for defs

Yes, I have both the A00G and A01G definitions in the 2012 folder.

I just tried to load up a stock A00G and it calls up the A01G definitions too.

Again I got wiser. Thanks for your help!

[steve99]

Originally Posted by Tor

Yes, I have both the A00G and A01G definitions in the 2012 folder.

I just tried to load up a stock A00G and it calls up the A01G definitions too.

Again I got wiser. Thanks for your help!

also look at A00G def its very short and just basicly points you to A01G def for tables as they are same

On any car prior to A01G just use A01G based roms its much better , no point in flashing outdated roms just update early cars to A01G or A02G


<rom>
<romid>
<xmlid>ZA1JA00G</xmlid>
<internalidaddress>8000</internalidaddress>
<internalidstring>ZA1JA00G</internalidstring>
<caseid>8644387107</caseid>
<ecuid>ZA1JA00G</ecuid>
<make>Subaru</make>
<market>AUDM</market>
<model>BRZ</model>
<transmission>6MT</transmission>
<year>2012</year>
<flashmethod>subarubrz</flashmethod>
<memmodel>SH72531</memmodel>
<checksummodule>subarudbw</checksummodule>
</romid>


<include>ZA1JA01G</include>

[Tor]

Originally Posted by steve99

also look at A00G def its very short and just basicly points you to A01G def for tables as they are same

On any car prior to A01G just use A01G based roms its much better , no point in flashing outdated roms just update early cars to A01G or A02G

As I mentioned it was just for a test, because I am trying to write a simple guide in German.

By the way, how comes that OTS or Wayno's ROMs are not based on A02G?

What are the differences between A01G and A02G anyway? I tried searching for that but didn't find anything.

[steve99]

bare bones definition with no edit ability

if you just want a flash only def this is all you need

all the roms are same length .

A def like below makes tactrix like the oft, ie it just corrects check sum loads and flashes with no edit ability

just do your editing in romraider, its a better editor anyway


<rom>
<romid>
<xmlid>ZA1JA01G</xmlid>
<internalidaddress>8000</internalidaddress>
<internalidstring>ZA1JA00G</internalidstring>
<caseid>8644387107</caseid>
<ecuid>ZA1JA01G</ecuid>
<make>Subaru</make>
<market>AUDM</market>
<model>BRZ</model>
<transmission>6MT</transmission>
<year>2012</year>
<flashmethod>subarubrz</flashmethod>
<memmodel>SH72531</memmodel>
<checksummodule>subarudbw</checksummodule>
</romid>