openecu.org

HI,

i was able to read EVO 6 ECU , and i can reflash the same file. Even if the car have ECUTEK i can Read but not write ?
(with cutting immobilisator wires)
If i try to change only one byte of the orignal file but i can´t write /reflash the new file.
Can anybody help me ?

Sorry- there is currently no write support for EVO5/6 and similar ECUs, though I believe there is some development going on.

hi, thanks for answering.

but i can´t understand because im able to reflash the original file without errors. It this only a problem of checksum or is there any other problem ?

I've actually been working on this all weekend again. I'm still running up against the same problem with the flash error bit being set before my kernel starts executing. The J2534 programmer from Mitsubishi also appears to be having the same problem, so I'm not sure what is going on. I might try to get another H8 ECU just to be sure I'm not going insane...

Colby

To answer your question, if you reflash exactly the same file, EcuFlash will not attempt to do any flashing at all and will hence get no errors.

Colby

thanks again for full explanation.

hopefull soon it will possible to reflash evo 6 too.

cboles, have you managed to work on the issue some of us have with reading a 6 ecu ?

I've noticed a couple of people (myself included) can not read the rom for a 6 ecu, with any version of ecuflash.

Just wondering if there is a bug in the software, or if it's a specific batch of ecu's that have an issue.

cossie:

I wasn't aware of any read problems with the H8 ECUs. Do you have a log from your read attempt?

I will be gone next week and away from email, but I can answer any further questions you have when I return.

Colby

cboles wrote:cossie:

I wasn't aware of any read problems with the H8 ECUs. Do you have a log from your read attempt?

I will be gone next week and away from email, but I can answer any further questions you have when I return.

Colby

I will get a log for you in the next week and past it up, but basicly it sends init sequence 2, and then fails.

There is a couple of people this has happened to.

I briefly spoke to GrayW on the MLR about it the other night, and he's come across this too, and thinks the 6 ecu needs another wire connected to get into the bootstrap of the ecu.

Anyway as I said I'll get a log at some point, so you can see exactly what it does / doesn't do.

Cheers

Hi Colby,

This is a copy of the log from the version of ECUFlash that you sent to me to do a complete log. It doesnt seem like it gets very far, just three byte pairs then it fails. Whats interesting is that it doesnt give any error message, just stops working.

------------------------------

[17:00:22.157] Version 1.33beta.1407
[17:00:22.167] 11 memory models read.
[17:00:22.167] scanning for metadata models in C:/Documents and Settings/andrew/My Documents/Rommetadata
[17:00:22.358] 81 ROM metadata models scanned.
[17:00:22.358] checksum module "subarudbw" loaded.
[17:00:22.358] flashing tool "wrx02" loaded.
[17:00:22.358] flashing tool "wrx04" loaded.
[17:00:22.358] flashing tool "sti04" loaded.
[17:00:22.358] flashing tool "sti05" loaded.
[17:00:22.358] flashing tool "mitsukernel" loaded.
[17:00:22.358] flashing tool "mitsukernelocp" loaded.
[17:00:22.358] flashing tool "shbootmode" loaded.
[17:00:42.066] Using interface OpenPort 1.3 Universal TX25*7lXb818b7c95cd3cbc851209cd1bdd5607b69903b04
[17:00:48.495] sending init sequence 2
[17:00:48.505] [W] 00
[17:00:48.535] [R] 00
[17:00:48.545] [R] 13

------------------------------

cboles wrote:cossie:

I wasn't aware of any read problems with the H8 ECUs. Do you have a log from your read attempt?

I will be gone next week and away from email, but I can answer any further questions you have when I return.

Colby

Sorry it took a little longer than I expected, but my log is similar to the one posted above.

This is what I get when I try and login to my evo6 ecu.

[16:37:50.781] Version 1.34.1435
[16:37:50.781] 11 memory models read.
[16:37:50.781] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[16:37:51.765] 253 ROM metadata models scanned.
[16:37:51.765] checksum module "subarudbw" loaded.
[16:37:51.765] flashing tool "wrx02" loaded.
[16:37:51.765] flashing tool "wrx04" loaded.
[16:37:51.765] flashing tool "sti04" loaded.
[16:37:51.765] flashing tool "sti05" loaded.
[16:37:51.765] flashing tool "mitsukernel" loaded.
[16:37:51.765] flashing tool "mitsukernelocp" loaded.
[16:37:51.765] flashing tool "shbootmode" loaded.
[16:37:56.625] Using interface OpenPort 1.3 Universal TX26pDkE6d0437d539f0b74e1f839ca8e61c0abf91fb0f09
[16:37:58.609] sending init sequence 2
[16:37:58.625] interface close
[16:37:58.625] interface close

again with the silence...

gteclass wrote:again with the silence...

Well they do say, "no news is good news"

This might be old info, but i managed to read an evo 6 stock rom as well as the Ralliart ROM with the Tactrix Openport 1.3U. This was after jumpering pins 4 (ground) and 1 of the OBDII port as well as having the programming white connector hooked up too.
Any developments on def files and reflashing of the evo6 ecu? Thanks for all the nice work