ECUFlash - Getting close!

[AdrianG]

Originally Posted by stugray

It is not that hard, but did you forget about all the early discussion about:
the conversions in ECU Editor being wrong
the padding or not padding the first X bytes
Checksums being wrong
More than one user "bricking their ECU"
Saving in Bin vs Hex
etc. , etc.

I guess part of my frustration about the tactrix has nothing to do with Flashing and about logging innovate data without an OBD port, so the 50 hours was mostly trying to get the unit to do that.

And I a am C&DH (command & data handling) engineer for NASA spacecraft that cost over $1 billion each. So I have not only "flashed" a LOT of expensive hardware, but I have done it to spacecraft that were a long ways away.
My primary job is writing procedures for loading flight software.
So as I said: maybe due to my job, I am overly anal about getting the instructions right instead of "just do it".

I didn't forget, I just DGAF.

- ecu editor is irrelevant, you said you wanted to flash an OTS tune
- padding etc has to do with reading, not writing. The first 0x8000 gets padded and it doesn't matter because that part of the ROM doesn't get written when you flash.
- bin and hex are number systems, not file types.
- those that were bricked were recovered from what I understand. A new ECU is less than one day's pay for a big shot like you anyways

Why don't you use your big smart NASA brain to develop your own tuning platform (or for that matter, your own maps) and then document all the steps so us laymen can follow along.

- AdrianG

[stugray]

Just for trivia, here are a couple of software errors that cost taxpayers millions:

Mars Global Surveyor - Bad Software patch (wrote to wrong portion of memory)
Result - complete mission loss - spacecraft blew up in orbit of Mars

Mars 98 Orbiter - Bad software units in "logging data"
Result - orbiter enters mars atmosphere and is destroyed

Deep Impact (ground test) - corrupt software load (still on the ground) - engineer failed to disable watchdog timer before "flashing" BOOT PROM
Result - removal of flight "bricked" ECU to be disassembled to get to JTAG port

Deep Impact (flight) - Bad software parameter results in exception in code BEFORE exception handler is operational.
Result - Constant CPU resets until power failure - complete mission failure.

I was part of every one of those "easy" operations, but it only took one misstep for complete mission failure.

So Maybe I am either stupid, or "overly cautious".

[stugray]

Originally Posted by vgi

since the community have helped you to get through with all your questions?

Oh I'm sorry, I thought that this forum was for exactly THAT - getting help.

I guess if I need any help, I will just go elsewhere.

[AdrianG]

Given that list of "easy" mistakes, "Overly Cautious" is not a phrase I would associate with you or your colleagues.

- AdrianG

[utekineir]

Originally Posted by reardrv

Lol... Well I can figure the XML part out, still can't get it to work right. It keeps saying I'm trying to read an unknown ROM image. I've run into this issue before trying to get it to work on my old 09 WRX when those definitions just came out. I'm trying to read the OFT ROM's and I can do it just fine on RomRaider, just not on ECUflash. Maybe someone more knowledgeable than myself can do a write up in the DIY section?

If I remember right what I did was

1) get definitions linked in the rom raider thread, make sure were XML files
2) put the definitions into the correct locations and direct the respective programs to use them
3) open tune .bin of choice in rom raider and save as a .bin
4) copy stock rom from car for safekeeping using ecuflash
5) write the tune file saved with rom raider with ecuflash


Not nearly as complicated or risky as reflashing the warp booster on the battle star galactica near the shoulder of Orion.

But for not being a highly paid professional i was pretty pleased with myself.

[utekineir]

Originally Posted by vgi

oh, so you only want to GET help but not GIVE help, is that right? So when you were whining there is no tutorial in a few posts and if someone could provide it, now you don't want to do write up for others? it would be easy for you since it's fresh in your memory and you are still going through the process

The cost of his time to write those instructions is more than you can afford pal.

He has race cars to build for fun.

[stugray]

Originally Posted by utekineir

The cost of his time to write those instructions is more than you can afford pal.

He has race cars to build for fun.

Instructions for installation of RomRaider ECU editor software and ECUFlash software specifically for use on BRZ:

Install RomRaider:
Retrieve Beta version of RomRaider (file: RomRaider0.5.7obdTest2-windows.zip):
https://dl.dropboxusercontent.com/s/...WWhQkeA8mqZAhg

Place contents of folder in location where you want to run from (this is NOT an install archive)
To star RR, you must execute the 'run.bat' file


Obtain desired ROM (writable) file:
Locate the proper ROM file (ex. ZA1JA01C.bin) from:
file: 2013 USDM BRZ ZA1JA01C.bin
http://www.romraider.com/forum/downl...e.php?id=20646

Have not yet found a generic website with all ROMs.
Look through this thread: http://www.romraider.com/forum/viewtopic.php?f=8&t=8475


Obtain desired RR - Defininition file:
retrieve the RR definition
file:RR_ZA1JA01C.xml
https://raw.github.com/TD-D/SubaruDe...R_ZA1JA01C.xml

Then open RR_ECU editor
Click on "ECU Definitions" tab, click "ECU definition Manager"
Click "Add" and browse to wherever you saved the RR_ZA1JAO1C.xml file, select the xml, Click "Open"
Back in Definition manager, click Save.

Now you may Open the ROM saved above.
in RR, click "File"->"Open Image"
Browse to where you saved the above file "2013 USDM BRZ ZA1JA01C.bin", select, click "Open"

This is where you may, or may not, encounter a checksum error.
It might say:
Checksum No. 1 is invalid in table: Checksum Fix
The ROM image may be corrupt.
Use of this ROM image is not advised!

Click OK

Then it might say:
Checksum No. 1 is invalid in table: Checksum Fix 2
The ROM image may be corrupt
Use of this ROM image is not advised!

Click OK

ROM should open & you can look through the tables.

To fix the Checksum errors you need to use ECUFlash


Install ECUFlash BRZ Beta:
file: ecuflash_brz_beta_144040.exe
http://www.tactrix.com/downloads/ecu...ta_1444040.exe
Plug in Tactrix cable and allow drivers to be installed
(on Win 7, this worked fine, on XP I had to get the driver package from the tactrix site instead of what came with the brz beta)


Obtain desired ECUFlash - Defininition file:
file:BRZ/ZA1JA01C.xml
https://github.com/TD-D/SubaruDefs/b...Z/ZA1JA01C.xml

Place this file (ZA1JA01C.xml) in directory:
C:\Program Files\OpenECU\EcuFlash\rommetadata\subaru\BRZ\2012 \


Open ECU_Flash:
Update Firmware in Tactrix cable
In ECUFlash, click "Help" - select "Licensing"
If Tactrix firmware is out of date, it will be updated here automatically to 1.14.4010


Open ROM:
Click "FIle" -> "Open ROM"
Browse to where you saved the ROM file: 2013 USDM BRZ ZA1JA01C.bin
Click file, click "Open"

IF you had checksum errors, a message will pop up: "The ROM you have loaded has one or more incorrect checksum values.
Do you wish to correct them?
Click "Yes"
You should now be able to see the values of the tables for the ROM you selected.
If the ROM is ready to be written, the red-arrow icon "Write calibration and code area using OEM method" will be "clickable"

You are now ready to plug into your car and flash away.
Final steps TBD - havent done it yet


Yeah, that is all just obvious and "anyone" can do it in just 5 minutes.

[stugray]

Originally Posted by vgi

that's a good start, thank you

You're welcome.
Thank you as well.

What you complied above in links alone would have made my learning experience much easier to navigate.

[stugray]

Originally Posted by vgi

To get RR defininition files lookup your file here:
http://www.romraider.com/forum/viewtopic.php?f=8&t=5792

For virtual dyno you might also want to get cars_def.xml from here http://www.romraider.com/forum/viewtopic.php?f=8&t=5792 and add BRZ in there (make any necessary changes, eg tire size):

It seems you got the same link for both of the above

Originally Posted by vgi

When using EcuFLash, connect the cable, click on 'read rom' (or write), the prompt will ask you to turn on the ignition - do turn on the ignition, wait until the bipping stops (i think 5 bips), then wait another about 6 seconds, only then click on that pop up box confirming that the iginition

Did the very last of your instructions get cut off?
"confirming that the iginition"

Maybe a max chars per post thing?

[stugray]

Thanks again.

So I downloaded the ROM from my car (ZA1J700C).
It seemed to work fine.
However when I try to save the ROM Image, it doesnt matter if I select "Structured ROM files (*.srf)" or "RAW ROM Files (*.bin *.hex)" it always saves in *.srf format.

I dont want to try to write until I have saved off my stock ROM (just in case).
Is this expected?
I assume that I need to save it in *.bin or I would not have any hope of restoring it in the future.

[stugray]

Originally Posted by vgi

nope, you should be able to save in raw format.

I compared the 'read_image.srf' to a stock_rom.bin for the ZA1J700C that I downloaded from the RR thread with hex editor.
They appear to be exactly the same except the *.srf file is missing the 0x0000-8000 padding.

I tried saving as both *.srf & *.bin thinking they might just be backwards in the pulldown menu.
Both times (to different paths) the files showed up as *.srf
I tried to attach the *.srf file, but it says "Invalid file".

I'll reboot everything and try again.

[stugray]

Originally Posted by vgi

you really should start reading RR forum.
as for the raw format, are you using 'Save ROM' or 'Save ROM As'?

i just tried, saving works like a charm. used 'Save ROM As'.

I have read all 25 pages of that thread more than once. I didnt memorize it.
Yes I use: File -> Save As, and in the pullup I select "Raw ROM Files (*.bin *.hex)"
It saves it as:read_image.srf
If I select save as *.srf, it saves it as a *.srf

When you say it works: So the file gets saved as 'read_image.bin"?

Here is a video of my trying all of the options:
http://s366.photobucket.com/user/stu...55606.mp4.html

I guess I'll try to reinstall ECUFlash.
This is on an XP machine BTW

[Td-d]

Ai yai yai... anyhoo, with the pissing match now over I'll just add that the words 'Alpha' and 'Beta' are there for a reason.

Remember guys, this is open source - all of us do this in our spare time, after our day jobs. And trust me, I could also 'earn' all the donations I've received in 2 years for the 100+ definitions I've posted, and all the ecu analysis work, in a morning - it's not why I do it.

Moving right along - thanks VGI and Stugray for putting that how to up. Just a heads up, I was requested to move the BRZ definitions with the OFT LC/FFS tables into their own branch (OFT) (here: https://github.com/TD-D/SubaruDefs/tree/OFT)

If you're looking for the Ecuflash definitions, look here: https://github.com/TD-D/SubaruDefs/tree/Alpha/ECUFlash - you will also need the updated 32bitbase.xml - here: https://raw.github.com/TD-D/SubaruDe.../32BITBASE.xml

The easiest thing to do it to download the entire repository, and then point Ecuflash to the Subarudefs directory. Even better, albeit more of a learning curve, is to set up a local Github repository, and then point Ecuflash to that directory. That way, you can update the entire directory regularly (easily, using Github with a GUI) and you'll have whatever new and exciting stuff I've added recently Granted, Github is a bit of a ballache to get your head around initially...

[Acree]

Is there any way to discover CANbus definitions/addresses/data using the OpenPort or ECUFlash?