OFT files with Tactrix Open Port 2.0

[ztan]

Originally Posted by ST-A

i read my 2013 GT86 using ecuflash and tactrix OP2 but when i want to save it as a bin file i got following fault



does anybody now what i'm doing wrong?

i put the ZA1JA00G.xml from github in de rommetdata/subaru/brz/2012 folder and the 32bitbase in the bases folder.

do i forgot something?

You're not doing anything wrong. EcuFlash is telling you that it has not (can't) read the addresses 0-8000 (Initial part of the User MAT). Continue with a file save then open the saved file with a Hex editor - if the addresses from 0-8000 read as "00" then all good. If not, they might need to be inserted - double check length of file compared to a known good ROM.

When EcuFlash writes to our ECUs, it bypasses 0-8000 at the moment.

[steve99]

Originally Posted by ztan

You're not doing anything wrong. EcuFlash is telling you that it has not (can't) read the addresses 0-8000 (Initial part of the User MAT). Continue with a file save then open the saved file with a Hex editor - if the addresses from 0-8000 read as "00" then all good. If not, they might need to be inserted - double check length of file compared to a known good ROM.

When EcuFlash writes to our ECUs, it bypasses 0-8000 at the moment.

my main concern was the references to 16bitbase file in the log on the same lines as ZA1JA01G , was conserned ecuflash using 16bitbase instead of 32 bitbase , more than the normal remove padding message when saving srf as bin although the image is blurry

im conserned it trying to save as a 512k rom not a 1Mb rom for some reason.

[steve99]

There might be an error in the definition your using

check in the header of the definition

memmodel is SH72531
flashmethod is subarubrz
checksum module is subarudbw

however you should not need definition to read and save rom image only to edit or write.

but if ecufalsh can match def to the image read it will try to use it.

sorry if i seemed harsh , i just know several who brick their ecu and unfortunatly their is no method to unbrick at this time.

[Wayno]

Originally Posted by Toyota John

If you have Tactrix OP2 cable you have to use ecuflash to read and write rom files anyway. The rest of the Subaru peoples use romraider because it can log but that feature doesn't work yet on the frs/brz/gt86 yet as far as i know. Why use Romraider if ecuflash can do everything romraider can and more.

Maybe because the Y axis on the graph is god damned backwards, or because you can resize it, or because you don't need to memorise 20 different hot keys to enter data, or you can actually read the values in the table, or a dozen other reasons.

[steve99]

Originally Posted by ST-A

i read my 2013 GT86 using ecuflash and tactrix OP2 but when i want to save it as a bin file i got following fault



does anybody now what i'm doing wrong?

i put the ZA1JA00G.xml from github in de rommetdata/subaru/brz/2012 folder and the 32bitbase in the bases folder.

do i forgot something?

Thats an old version of ecuflash, the latest one has a third flash icon for sh boot mode (but it wont unbrick ecu yet).

also looks like your tactrix dongle firmware needs updating as well hard to read numbers

older versions of ecuflash may not flash brz\86 correctly depending on how old

[ST-A]

removed all old versions of ecuflash and reinstalled:

[09:09:24.503] EcuFlash Version 1.44.4503 [09:09:24.503] OS Version Windows (unknown version)
[09:09:24.503] Kernel Type winnt
[09:09:24.503] Kernel Version 6.3.9200
[09:09:24.503] CPU x86_64
[09:09:24.503] Product Name Windows 8.1
[09:09:24.503] Product Type windows
[09:09:24.503] Product Version 8.1
[09:09:24.503] Qt Version 5.4.0
[09:09:24.519] 67 memory models read.
[09:09:24.519] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[09:09:24.784] 749 ROM metadata models scanned.
[09:09:24.784] checksum module "subarudbw" loaded.
[09:09:24.784] checksum module "subarudiesel" loaded.
[09:09:24.784] checksum module "mitsucan" loaded.
[09:09:24.784] checksum module "mitsuh8" loaded.
[09:09:24.784] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[09:09:24.784] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[09:09:24.800] using metadata XML ID read_subarush72531brz from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_subarush72531brz.xml
[09:09:24.800] flashing tool "wrx02" loaded.
[09:09:24.800] flashing tool "wrx04" loaded.
[09:09:24.816] flashing tool "sti04" loaded.
[09:09:24.816] flashing tool "sti05" loaded.
[09:09:24.816] flashing tool "mitsucan" loaded.
[09:09:24.816] flashing tool "mitsukernel" loaded.
[09:09:24.816] flashing tool "mitsukernelocp" loaded.
[09:09:24.816] flashing tool "mitsubootloader" loaded.
[09:09:24.816] flashing tool "shbootmode" loaded.
[09:09:24.816] flashing tool "shaudmode" loaded.
[09:09:24.816] flashing tool "subarucan" loaded.
[09:09:24.831] flashing tool "subarucand" loaded.
[09:09:24.831] flashing tool "subarubrz" loaded.
[09:09:24.831] flashing tool "subaruhitachi" loaded.
[09:09:24.878] J2534 API Version: 04.04
[09:09:24.878] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[09:09:24.878] Device Firmware Version: 1.15.4474
[09:09:24.878] Device Serial Number: TAPbdxXv
[09:09:24.878] interface close
[09:09:24.894] J2534 API Version: 04.04
[09:09:24.894] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[09:09:24.894] Device Firmware Version: 1.15.4474
[09:09:24.894] Device Serial Number: TAPbdxXv
[09:09:24.894] interface close
[09:09:24.909] J2534 API Version: 04.04
[09:09:24.909] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[09:09:24.909] Device Firmware Version: 1.15.4474
[09:09:24.909] Device Serial Number: TAPbdxXv
[09:09:24.909] interface close
[09:09:24.925] J2534 API Version: 04.04
[09:09:24.925] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[09:09:24.925] Device Firmware Version: 1.15.4474
[09:09:24.925] Device Serial Number: TAPbdxXv
[09:09:24.925] interface close
[09:09:24.941] J2534 API Version: 04.04
[09:09:24.941] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[09:09:24.941] Device Firmware Version: 1.15.4474
[09:09:24.941] Device Serial Number: TAPbdxXv
[09:09:24.941] interface close
[09:09:24.956] J2534 API Version: 04.04
[09:09:24.956] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[09:09:24.956] Device Firmware Version: 1.15.4474
[09:09:24.956] Device Serial Number: TAPbdxXv
[09:09:24.956] interface close

installed the 32bitbase file in the bases folder
installed the ZA1JA00G xml in the BRZ/2012 folder

going to retry next when it stops raining

[steve99]

Originally Posted by ST-A

removed all old versions of ecuflash and reinstalled:



installed the 32bitbase file in the bases folder
installed the ZA1JA00G xml in the BRZ/2012 folder

going to retry next when it stops raining

The A00G is an outdated ROM


You can use A01G (it has DI Seal/Transient retard fix) or the A02G rom. Both are compatable with A00G cars


only issue with A02G is the logging parameters are a bit different from A01G , you would have to ask one of the ecu dissembly guys ztan or td-d to find them


so maybe A01G is best one to run as the logcfg.txt file for logging is working for Tactrix logging on A01G rom