Evo X ROM patching for logging

Evo X ROM patching for logging

Postby cboles » Fri Mar 26, 2010 4:46 pm

Just wanted everyone to know that the latest beta on the site now supports simple checkbox patching of the EVO X (and probably other Mitsu CAN ROMs) ROMs for the "mode23" RAM logging feature. This "smart" patching system is a much easier / safer way to do this patch without having to have a specific patch for your particular ROM.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Evo X ROM patching for logging

Postby Tephra » Mon Apr 05, 2010 10:29 pm

Hi Colby,

I tried this with ecuflash_1433000_win_beta.exe on 53040013...

You got the mode05 -> mode23's right BUT EcuFlash didn't update the jump to mode23 call properly. (at all)

so 2/3 :)

Cheers
D>
Tephra
 
Posts: 59
Joined: Mon Aug 27, 2007 2:16 am

Re: Evo X ROM patching for logging

Postby cboles » Mon Apr 05, 2010 10:43 pm

Tephra wrote:Hi Colby,

I tried this with ecuflash_1433000_win_beta.exe on 53040013...

You got the mode05 -> mode23's right BUT EcuFlash didn't update the jump to mode23 call properly. (at all)

so 2/3 :)

Cheers
D>


Oops. The third jump part was missing from the XML I was referencing from. The ECU / ROM I was testing on already had it, so I didn't notice. I'll get something out pretty quick.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Evo X ROM patching for logging

Postby Tephra » Mon Apr 05, 2010 10:53 pm

Hi Colby,

No dramas

are you tracing the code or just looking for a specific pattern?

also (and I guess in continuation of that question) for the jump replacement, do you know its sometimes 0x42 OR 0x4D offset... ie its variable...
Tephra
 
Posts: 59
Joined: Mon Aug 27, 2007 2:16 am

Re: Evo X ROM patching for logging

Postby cboles » Mon Apr 05, 2010 11:01 pm

Yeah - I have the variable jump worked out... It should even work for new unseen offsets assuming some other aspects of this function don't change (In which case it will just stop giving you the patch option).

Tephra wrote:Hi Colby,

No dramas

are you tracing the code or just looking for a specific pattern?

also (and I guess in continuation of that question) for the jump replacement, do you know its sometimes 0x42 OR 0x4D offset... ie its variable...
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Evo X ROM patching for logging

Postby SiC » Wed Apr 07, 2010 6:11 am

This is great, will have to give it a try :)

BTW, is there any way we can log by the MUT number such as MUT21 for RPM instead of the actual address such as 23808746? This would make things so much easier so we don't have to find the actual addresses for all the different year, model, region, etc. ROMs since they all have different addresses. Currently, everytime we have to log a different year vehicle, we have to rewrite or swap out the configuration file.
SiC
 
Posts: 4
Joined: Thu Aug 14, 2008 5:11 am

Re: Evo X ROM patching for logging

Postby Tephra » Wed Apr 07, 2010 6:33 am

Acamus had some info on unlocking MUT... i havn't tried it yet..
Tephra
 
Posts: 59
Joined: Mon Aug 27, 2007 2:16 am

Re: Evo X ROM patching for logging

Postby SiC » Wed Apr 07, 2010 7:31 pm

This is one ROM that I couldn't find the last 2 mode23 addresses for since I only look at the specific pattern and not tracing the code :oops:
Attachments
56190002.hex
2010 JDM EVOX SST
(1 MiB) Downloaded 197 times
Last edited by SiC on Wed Apr 07, 2010 7:58 pm, edited 1 time in total.
SiC
 
Posts: 4
Joined: Thu Aug 14, 2008 5:11 am

Re: Evo X ROM patching for logging

Postby Tephra » Wed Apr 07, 2010 7:45 pm

the code path ALWAYS starts at 0x13c

its about 4 jumps from there until the OBD Mode lookup's..
Tephra
 
Posts: 59
Joined: Mon Aug 27, 2007 2:16 am


Return to Openport Stand-Alone Logging Beta

Who is online

Users browsing this forum: No registered users and 2 guests