openecu.org

Hello,

I read Pajero Pinin GDI 2.0 2004 with OP 2.0 1.43.3150 (Betta).
Driver - "Lancer RalliArt (512k) 2004-2005 mitsubootloader M32176F4".
(Dump and log in attachment)

1. Need this dump checksum correction and if "yes" than What kind of correction I need to do?
(may be just correct 32-bit checksum like Lancer X ???)

2. How can I write new dump?
Before now (when I didn't have *.xml for specific car) I did "File" -> "Open ROM..." and got
window "Setup ROM", selected "Use wizard to create a new definition (NOT RECOMMENDED!!! - FOR DEVELOPERS ONLY)"
-> "Next" -> got new window "Setup ROM", then selected "Inherited from the definition below" and selected car
like my car (now I have not any similar car). Then next, next, finish and I can WRITE.

Thenx

people are having the same issue with the colt ralliart. There is rumored to be a beta version of ecu flash along the lines of 1.43.770 that can write the correct checksums but its nowhere to be found and several emails to tactrix support havent turned up with anything. As soon as you change a single byte the checksum doesnt compare and the ecu goes into limo mode showing p0606. The definition will need to be created but your rom addressing will be very similar with maps to the colts. To read it properly did you need to cut pin 11 on the obd port and wire it directly to the op2 reflash connector? People has had issue with killing there adaptor if pin 11 is still connected. Theres very little info about the evox checksum info but it should be mitsucan module.

I didn't cut 11 pin to read flesh.
http://www.evoscan.com/technical-vehicl ... liart-colt
http://www.evoscan.com/technical-vehicl ... ancer-4g69

Evo X checksum is not problem to correct. You have to just correct 32bit cs.
I made simple xml to write but I'm afraid about 512k is not full dump
and if I erase all the flesh and write 512k only.
If I'll get cs error only it's not very big problem - I'll just write original.

Colt can be rewritten without problem?

not without throwing a check engine light and dtc code unless checksum is corrected. there appears to be several entries in the rom where it exists but its a very rudimentary method of correcting it. your rom size should be right. if it isnt then the last few segments of code will be empty with ffff. just looked at your rom and it seems as if it may be correct size. there is heaps of similarities between the two roms from the colt and your car. as i said there is apparently a beta version of ecuflash which isnt available that can work correctly. you can try writing the rom at that size like i have and if it doesnt work just reflash the original rom in and will go back to normal. what are you changing in your xml? something simple to try may be just to hex edit a segment of code at the start and say change ffff to fff0 or something and see if it lets you write it without error. even when you correct the 32bit checksum by balancing the bytes it has to be in a specific location

ok ecu id is 30578779 i think at offset 0000023A and model might be EMC923 @ 0003FFFA.
immob code at same address aswell as init code 0001 standard. actually very similar to other m32r roms

I wont to use simple xml to write dump:

- <rom>
- <romid>
<xmlid>EMC923</xmlid>
<internalidaddress>3fffa</internalidaddress>
<internalidstring>EMC923</internalidstring>
<make>Mitsubishi</make>
<market>JDM</market>
<model>Lancer</model>
<submodel>RalliArt (512k)</submodel>
<year>2004</year>
<flashmethod>mitsubootloader</flashmethod>
<memmodel>M32176F4</memmodel>
</romid>
</rom>

I have one dump from Lancer RalliArt (512k) 04-05 mitsubootloader M32176F4 (in attachment) that I downloaded from
http://www.evoscan.com/technical-vehicl ... ancer-4g69
It's like my one I think

xmlid should be 30578779. internal id address should be 23A. should have a checksum module as mitsucan. the emc923 is just the family i think.


- <rom>
- <romid>
<xmlid>30578779</xmlid>
<internalidaddress>23a</internalidaddress>
<internalidstring>30578779</internalidstring>
<make>Mitsubishi</make>
<market>JDM</market>
<model>Lancer</model>
<submodel>RalliArt (512k)</submodel>
<year>2004</year>
<flashmethod>mitsubootloader</flashmethod>
<memmodel>M32176F4</memmodel>
<checksummodule>mitsucan</checksummodule>
</romid>
</rom>

I tried to reflesh car. All is ok.
I delated line <checksummodule>mitsucan</checksummodule>.
When there is this line EcuFlash try to change even ori.
I calculated checksum by myself.
I did not try to write without checksum corected.

Have got a more troubles.
Used 1.43.350, dumped 2003 AT Lancer RA, made test .xml on base of coltRA xml..
Write without changes - ok. Make are few changes, car won't start. Flashed original HEX - same thing. CEL..
Tryed to use another one 2004? RA HEX, car started, but CEL (CEL 2021??) and misfired 2 cylinders (
Have you any ideas, how can i fix it? If anyone can help, i'll donate, becouse i have to go at work after tomorrow, without car i can't.

I have attached stock rom, stock rom dumped with 2006+ colt 762kb interface, 2004? ROM misfired in 2 cyl and xml..

The software is not yet compatible with the 4G69 model lancer vehicles. You are lucky, the first couple we tried we locked the ecu's up and couldn't reflash abck to them.

Your only chance is to go back to a mitsubishi dealer and get the ecu reflashed by them back to stock.

Hard to hear it..( I'm located in Wester Europe, and sure, that local dealer will be helpless for my USDM RA...
I will try to install usdm galant 4g69AT ecu in my RA for some time.. Maybe later this problem with ECU will be solved..

Today I flashed ecu a few times, and have seen, that "misfired flash" also won't start once.. hmm...

Should I try this method, http://www.evoscan.com/technical-vehicl ... ancer-4g69
I can connect OBD directly to ECU
Should i try another ROMs, or I'm just wasting time?

Thank you!

The problem is not hte roms but the flashing protocols are not setup properly yet and induce an error when flashing. The whole rom is not being loaded back to the ecu.

Using another model ECU will not work as there are inbuilt security codes which are coded to the Etac unit and your ignition key. You would need to change your ignition key, etac controller and ECU all from the same doner vehicle to sort the problem out. Thats what we had to do to our local vehicle here.

There is no ETA at this stage as to when the Ecu software will be fixed and enable people to reflash these model ecu's

perhaps try 1.43.3172. thats the model working on the colts at the moment

sherpa, yes, I had tried today 1.43.3172, but didn't helped..

Mitsiman, Thanks for advice, looks like I have no ETA when my car will start running again..

Thanks, friends

I just have not any idea...

Everything ok, it was easier than I thought, RA04-06 flashes without problems now!