Help - can't flash 2017 brz
 

Hello all,

I have a 2017 USDM 5mt brz (ZA1JK00C), i'm trying to flash the car using opensource/ecuflash. I have the xml and 32bitbase from TD-D, the car read the stock ecu just fine, but gave me this error when i tried to save it. "The rom image contains sections of invalid data which must be zero padded to make a contiguous file. It is possible upon subsequent loading of this file that you might flash over valid areas with these zeroed areas. Do you wish to continue?"

If i click yes it allows me to save the file. I saved it made another copied and made a few changes, tried to flash it and only had the option to write SHboot, i tried it and got this:

[16:33:34.630] J2534 API Version: 04.04
[16:33:34.630] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[16:33:34.630] Device Firmware Version: 1.16.4769
[16:33:34.630] Device Serial Number: TAh0RMVn
[16:33:52.027] sending bit rate sync bytes...
[16:33:53.713] no bit rate adjust response
[16:33:53.714] interface close

Can anyone help me out? I've tuned lots of wrx/sti but this is my first brz

Do you have an ecuflash definition in the correct ecuflash directory

How did you edit rom romraider or ecuflash

Did you select brz as the vehicle type ?? In ecuflash before flash

Does car srill start ??

Can you still read the ecu ??

You 100% cannot use boot mode flash method its only if you connsct to the serial interface by soldering an interface directly to ecu.

You must use oem flash method, if ghe oem icon is not active you have not open a valid rom to flash or your tactrix in not plugged into computer or is stuffed usually both read nad write icons will be grey if not tactrix
The error re padfing and unused areas is normail if saving in bin format.

Found the problem

Their is a small error in the ZA1JK00C definition

The flashmethod is set wrong its set to subarucan it should be subarubrz


<flashmethod>subarubrz</flashmethod>
<memmodel>SH72531</memmodel> <checksummodule>subarudbw</checksummodule>


Change the flashmethod in the def and should be ok

Steve, thank you so much for the response! yes the car still started and read fine. Should i not save it in bin format? or is that okay?

I used ecuflash to make the changes in the rom. I'll try editing the .xml like you said and see if that fixes it!

Also is there a way to log the car without using the tactrix SD card setup? I found the OBD logging thread on romraider but the links are bad

Unfortunatly romraider logger never got sorted for these cars so only option with tactrix is sd card logging and you need to know ram addresses for the 2017 which i dont have, but you could ask the romraider guys.

The android torque app will do basic logging using a cheap elm327 but its no good for knock parameters and its refresh rate is to slow for tuning.

Other option is to buy brzedit or use techstream software , again techstrea is a bit slow refresh rate but it does have the iam and flkc knock parameters.

The other drama you will have is the 2017 is new logic for fueling and timing , especially fueling has more tables and some are not defined in the current K00C definition one that ecutek calls power afr is one you will need to efectivly tune