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

[phrosty]

Originally Posted by bur****jp

I got addresses from the 'b01c' addresses file. I can't remember which of the other files I started with, but there were a few things which needed to come over from the addresses file.

Originally Posted by steve99

try @phrosty he is on b01c or d rom sure he has a working logcfg.txt for that rom. strange load does not work as most guys would want that for maf scaling.

B01C/B01D load:

paramname = Load
paramid = 0xFFF8914C
isfloat = 1

I've got a B01C/B01D log file pre-made with all the typical fields here.

[steve99]

Added

I rom logging file
D rom logging lile
Cam timing log parameters for G & I roms thanks @ztan

[dave-]

General question here about bad flash a while back.

Basically went to flash like normal and it failed, don't recall the error and can't find the full log but I left the ignition on and only hit write again. It worked but I got the following error on the second write attempt. I assume it is because the first failed write erased everything?

[11:46:29.509] reading vehicle info...
[11:46:31.514] OBDII communications failed - trying OEM bootloader...
[11:46:31.515] connected to OEM bootloader!
[11:46:31.515] preparing to write area 00008000-0013FEFF...
[11:46:31.517] erasing area 00008000-0013FEFF...
[11:46:37.110] writing area 00008000-0013FEFF...
[11:48:15.121] interface close

Did I avoid a brick by leaving the ignition on and just doing another write? Or is ecuflash smart enough that it would just been able to write the ROM again regardless of what I did with the ignition?

[steve99]

Originally Posted by dave-

General question here about bad flash a while back.

Basically went to flash like normal and it failed, don't recall the error and can't find the full log but I left the ignition on and only hit write again. It worked but I got the following error on the second write attempt. I assume it is because the first failed write erased everything?

[11:46:29.509] reading vehicle info...
[11:46:31.514] OBDII communications failed - trying OEM bootloader...
[11:46:31.515] connected to OEM bootloader!
[11:46:31.515] preparing to write area 00008000-0013FEFF...
[11:46:31.517] erasing area 00008000-0013FEFF...
[11:46:37.110] writing area 00008000-0013FEFF...
[11:48:15.121] interface close

Did I avoid a brick by leaving the ignition on and just doing another write? Or is ecuflash smart enough that it would just been able to write the ROM again regardless of what I did with the ignition?

You will probably never know.

but always safer to try writing again before turning ignition off as you can always try again after turning ignition off.

The ECU is still in program mode from previous write attempt, till ignition is turned off.

Their are three ROM area in the ECU

1. SH Boot area (very low level boot area) need serial communication to access ie soldering wires to ECU
2. USER BOOT Area can be accessed via OBD port
3. USER ROM area - the area flashing devices read/erase/write/talk to.

Appears all flashing devices only write to the third area USER ROM area.
So you connect your flashing device, it initially tries to communicate with the software code in the USER ROM area via OBD communication method. If no response the Tactrix and other system can try communicating with the USER BOOT area code. This is your get out of jail free card if flash fails part way through.

Main causes of failed flash are bad connection to obd port, low or flat car battery or laptop issues.



As I understand it Tactrix tries to communicate with the ECU via the OBD communication method first . I believe this is communicating via the software thats contained in the rom you flash. You only get one go at this method as USER ROM area is ERASED before write takes place.

I suspect what happened was

1. Initial flash failed part way through for unknown reason.
2. USER ROM area now erased or partial write
3. Second time tectrix tries to talk to ecu via code in USER ROM area which is trashed it fails
4. Tectrix tries comms via USER BOOT code, comms established , USER ROM area erased and written successfully.


The big problem occurs when you write complete rubbish code, or for some reason the partially written rom cause the ecu to loop or go into some other weird state where you have no communication via the OBD port.

Check your obd connection by either READING ROM or LOGGING and wiggle connection if it drops out during READ or you get heaps of short log files you have connection issues.

[dave-]

Yeah I suspect it was bad connection, though I always do a read first and that was fine. Possibly the port/pins are damaged from constantly unplugging a scangauge and connecting a BT dongle or tactrix at the track to collect data. Haven't tried a write since but logging has been fine.

[steve99]

Originally Posted by dave-

Yeah I suspect it was bad connection, though I always do a read first and that was fine. Possibly the port/pins are damaged from constantly unplugging a scangauge and connecting a BT dongle or tactrix at the track to collect data. Haven't tried a write since but logging has been fine.

I use a short obd extension cable for this reason and leave thet plugged in all the time so i dont wear out port on car.

even better buy one with an inbuilt switch

[ame="http://www.amazon.com/gp/product/B00UR5XBMW/"]Amazon.com: OBD 2 16pin Male to Female Right Angle Diagnostic Extension Cable with Power Switch: Automotive[/ame]

[dave-]

Originally Posted by steve99

I use a short obd extension cable for this reason and leave thet plugged in all the time so i dont wear out port on car.

Yeah hindsight and all.

[burdickjp]

Originally Posted by steve99

I use a short obd extension cable for this reason and leave thet plugged in all the time so i dont wear out port on car.

even better buy one with an inbuilt switch

Amazon.com: OBD 2 16pin Male to Female Right Angle Diagnostic Extension Cable with Power Switch: Automotive

Oh, that's clever.

[toyota_86]

Hi All,

Just wondering Has anyone got a rom raider logging definition made yet?

Also about almost bricking the ECU, My laptop battery (was faulty and showing wrong battery level) has died before during a write and i turned ignition off and then on and was able to write the flash again fine. Its also happened on my WRX before (i know need a new laptop battery) and same thing it was able to write fine on retry.

[steve99]

Originally Posted by toyota_86

Hi All,

Just wondering Has anyone got a rom raider logging definition made yet?

Also about almost bricking the ECU, My laptop battery (was faulty and showing wrong battery level) has died before during a write and i turned ignition off and then on and was able to write the flash again fine. Its also happened on my WRX before (i know need a new laptop battery) and same thing it was able to write fine on retry.

No romraider logging available for brz/86 other than basic obd stuff.

The RR guys busy on 2015wrx ecu, best talk to them re any work on rr logging for brz/86

only option with tactrix is the SD card logging at present

Re batterys , I would not push your luck, best to plug laptop into mains power , only have ecuflash running and disable wifi . Also make sure car battery is good.

Tactrix/ecuflash has OEM recovery mode (user boot) if normal obd mode (user rom) fails but its still possible to get ecu into a state where it wont recover when laptops or car battery dies mid flash if the user rom area loops or goes into a weird state due incomplete flash Same with any other flashing system.

[steve99]

added ZA1JA02J rom for middle east region

[Sportsguy83]

@steve99 was able to flash a friend's auto 15' FRS with Stg. 1 93 pumpgas ROM.

I let Ecuflash correct the checksum.

The Ecu did not want to accept the key (like it was an Ecutek/BRZEdite, etc. locked ECU but it was not, he bought the car brand new fresh from the lot), until it finally accepted it and successfully flashed the ROM.

I can't thank you enough for this post. It helped tremendously!!

He has a D00D ROM.

[steve99]

Originally Posted by Sportsguy83

@steve99 was able to flash a friend's auto 15' FRS with Stg. 1 93 pumpgas ROM.

I let Ecuflash correct the checksum.

The Ecu did not want to accept the key (like it was an Ecutek/BRZEdite, etc. locked ECU but it was not, he bought the car brand new fresh from the lot), until it finally accepted it and successfully flashed the ROM.

I can't thank you enough for this post. It helped tremendously!!

He has a D00D ROM.

thanks

usually that sort of thing is caused by bad connectio, tactrix adapter has thin pins ,i bent mine inwards slightly.

or you hit go to flash without waiting 15 secs

i always do a read first and wiggle cable to see i have a soild connection the obd ports in thes cars can be a intermittent.

[EAGLE5]

I always do a full read before doing a write.