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

[Pro60modman]

Originally Posted by steve99

Hmmm with SD card in device, you should be able to see the SD card as a usb drive when tactrix connected to computer.


assume you don't have usb connected when trying to log as it wont work, must be standalone to log ie just plugged into obd port.


It possible the devices sd card slot is faulty, maybe talk to the tactrix guys.

Got it all sorted out, SD card issue.

Now it is creating 15-20 logs when I go on 20-40 minute drives. Only once has it taken a 15 minute drive and actually logged it continuously into one log. I'm working around it currently but any input on this?

[steve99]

Originally Posted by Pro60modman

Got it all sorted out, SD card issue.

Now it is creating 15-20 logs when I go on 20-40 minute drives. Only once has it taken a 15 minute drive and actually logged it continuously into one log. I'm working around it currently but any input on this?

If you have deleted all trigger lines in code and its still creating multiple logs then you have a connection issue to obd port.

Try bending both rows of pins on tactrix adapter inwards about 0.5mm use something like an old full size SD card or similar .

[renfield90]

Originally Posted by Pro60modman

Got it all sorted out, SD card issue.

Now it is creating 15-20 logs when I go on 20-40 minute drives. Only once has it taken a 15 minute drive and actually logged it continuously into one log. I'm working around it currently but any input on this?

Originally Posted by steve99

If you have deleted all trigger lines in code and its still creating multiple logs then you have a connection issue to obd port.

Try bending both rows of pins on tactrix adapter inwards about 0.5mm use something like an old full size SD card or similar .

I had a similar issue until I bent my pins.

Also note, if you are having this issue you are likely to see flashing failures - which takes you every so slightly closer to bricking the ECU. You can fail 20 times in a row and still get success on the 21st try (ask me how I know) but it's nerve racking, and there's no guarantee you don't brick it if you suddenly lose power for some reason.

[Pro60modman]

Yea that happened last night. 6 failures and success on the 7th. I actually recover bricked 32bit Subaru ECU's at my shop but I've never looked into recovery of a FRS/BRZ yet. Bent the pins this morning and the logs have been continuous and flashes consistent. I appreciate the help Steve.

[renfield90]

Originally Posted by Pro60modman

Yea that happened last night. 6 failures and success on the 7th. I actually recover bricked 32bit Subaru ECU's at my shop but I've never looked into recovery of a FRS/BRZ yet. Bent the pins this morning and the logs have been continuous and flashes consistent. I appreciate the help Steve.

You do recovery via JTAG? Or you got some other secret sauce?

[Pro60modman]

Originally Posted by renfield90

You do recovery via JTAG? Or you got some other secret sauce?

Built the boot circuit on tactrix website, use a soldering iron and ECUflash or the Renesas program.

EDIT: The first ECU I tried was from a friend's 2008 STI. Got impatient and used a spare battery and re-purposed Honda wiring pins to power and ground the computer. Worked like a charm.

[steve99]

Originally Posted by Pro60modman

Built the boot circuit on tactrix website, use a soldering iron and ECUflash or the Renesas program.

EDIT: The first ECU I tried was from a friend's 2008 STI. Got impatient and used a spare battery and re-purposed Honda wiring pins to power and ground the computer. Worked like a charm.

Yes brz\86 ecu is different SH 72531 precessor it has two rom areas called MAT,s the one we write to is the user mat, but it also has a boot mat that tactrix and other flash systems dont touch. This is what saves you when flash fails unlike the older wrx 7058\7059 based ecu.

Dont try to sh boot mode the brz\86 ecu as both user and boot mat get deleted when you enter sh boot mode using hardware circuit. unfortunatly opensource has not been able to read boot mat so you cannot write it back.

http://www.ft86club.com/forums/showthread.php?t=95334

only option at present is to swap in replacement ecu


http://www.ft86club.com/forums/showp...91&postcount=1


other option may be to hardware strap the processor to user boot mode which does not erase both rom areas on entry, ecu has 3 modes run mode user boot mode and sh boot mode

mode is controlled by the MDA and MDB pin voltages. fot just boot mode you need to set mdb pin to 5v, it may float high if just unsoldered for its ground connection, then put ecu back in car and flash with tactrix, as user boot mode ecu still uses obd port not serial port so you dont need external circuit for serial port access.

If flash sucessfull then remove ecu again reconbect mdb to ground.
Have not tried as not bricked one yet
also processor chip is surface mount and extremly fine small pins, desoldering just thge one pin will be difficult.

[Pro60modman]

Oh I definitely didn't plan on trying anything rash in the middle of the night like that but that is some very useful information to have in case a FRS or BRZ ECU is ever sent to me.

[Pro60modman]

How do I setup the logcfg to read actual manifold pressure and log all of the VVT parameters?

EDIT:

Figured out manifold pressure I think

paramname = MAP
paramid = 0xFFF8DB94
isfloat = 1
scalingrpn = x,.14503773773020923,*,14.7,-

[steve99]

Originally Posted by Pro60modman

How do I setup the logcfg to read actual manifold pressure and log all of the VVT parameters?

EDIT:

Figured out manifold pressure I think

paramname = MAP
paramid = 0xFFF8DB94
isfloat = 1
scalingrpn = x,.14503773773020923,*,14.7,-

The big issue with logging on Tactrix is knowing the ecu ram address to log for the parameters.


All the ones I know about are in first post in this thread, if you have a rom calid other than the known ones your in a bit of trouble. you could try posing on romraider site for the ram addresses.


other alternatives are use Techstream for logging, its a bit slow on refresh rate though , but you can use tactrix as the interface or buy a copy of brzedit. see here


http://www.ft86club.com/forums/showp...54&postcount=1





other option is maybe a used ecutek cable for brz/86 as you can log any brz/86 no need for licience, you only need licience to flash ecu.
..

[brianhj]

I have a 2013 FR-S MT that I just returned to stock.

ZA1JB01C-enc.bin in C:\EcuTek\ProECURomFiles\Subaru\BRZ....... is this the file I should flash?

[steve99]

Originally Posted by brianhj

I have a 2013 FR-S MT that I just returned to stock.

ZA1JB01C-enc.bin in C:\EcuTek\ProECURomFiles\Subaru\BRZ....... is this the file I should flash?

use ecutek "query ecu" option to read calid from ecu, then flash the same stock rom calid from the folder you mention above.

[brianhj]

Originally Posted by steve99

use ecutek "query ecu" option to read calid from ecu, then flash the same stock rom calid from the folder you mention above.

[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.