Pages: [1]
Print
Author Topic: MY99 2.5RS USDM Romid  (Read 3601 times)
Hito
*
Offline Offline

Posts: 11


View Profile
« on: August 05, 2009, 10:58:22 PM »

All,

I have been hoping for a place to get involved in disassembly for a long time!  This is great!!

I have not seen anyone post this yet, so I am not sure if you know but it is very easy to get the ROM off MY99-01 2.5RS ecu with the latest 3.0.25 version of ecuexplorer that was posted just before the project got abandoned by its creator.  Lucky for us it is all on code.google.com now!!  Just before the end he implemented a function called ecuQuery where the program would query the ecu starting at an address of your choice and with a defined length.  I used this tool to extract the following ROM from my MY99 2.5RS.

I am using a tactrix cable openport 1.2 I believe.

You can find the 3.0.25 Ecuexplorer here: http://code.google.com/p/ecuexplorer/downloads/list

I queried the ECU from 0x0000 to 0xFFFF, but stopped at 0xA000 because I got all zeros from 0x5000 to 0xA000.

I also tried with the Polaris Select Monitor tool, but all I got was 32k of Zeros.

I am new at this but want to learn!  How does this compare to the datasheet mentioned M32 Processor for OBD2 Ecus?

I will get a picture of the ecu soon.  I also have a spare MY00 RS ecu that I will hook up and get a dump off asap.  From MY99 to MY00 the car changed from MAFS to MAP so it will be interesting.

Is there any need for me to continue from 0xA000 to 0xFFFF??
« Last Edit: August 12, 2009, 05:59:53 PM by RoadRunner » Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #1 on: August 05, 2009, 11:08:37 PM »

http://www.renesas.com/fmwk.jsp?cnt=m32r_family_landing.jsp&fp=/products/mpumcu/m32r_family/

??
Logged
b3lha
*
Offline Offline

Posts: 198



View Profile WWW
« Reply #2 on: August 06, 2009, 04:53:05 PM »

Quote from: orthomong
The software in the ECU blocks access to major areas of the ROM (namely the firmware) They don't however block the higher addresses. If you try and read memory above 0x700000 the cpu ignores the high address bits and returns the rom.

Read memory from 0x700000 to 0x740000
Logged

See my Subaru ECU and TCU website.
http://www.alcyone.org.uk/ssm
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #3 on: August 07, 2009, 08:11:49 PM »

Working..  but it's going to take hours with ecuexplorer to get 256k

is the rom really that big?
Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #4 on: August 08, 2009, 11:36:26 AM »

Alright Here it is!!  Hopefully we can get orthomong to help us identify some of it!

the outside of the ECU reads

B5
22611  AE550
A18-000 D72 stamped 9304
Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #5 on: August 08, 2009, 11:38:16 AM »

And the rest

but its all zeros up until the last 3 bytes

9c 66 FF
Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #6 on: August 08, 2009, 11:39:44 AM »

I also have a MY00 RS ecu that I could hook up it it would be helpfull, but if we can flash one we can flash them all..
Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #7 on: August 10, 2009, 12:55:17 AM »

a couple questions?

Is what we have here a M32R as some a eluded to?  I have to pull my case off and see if its 144pin.  In that case M32R is supported by IDA Pro advanced?  If so where would the "entry point" be?  0x4000?

!!

Todd
Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #8 on: August 10, 2009, 02:46:30 AM »



Does this look right at all?  IDA Pro Advanced set to M32R : M32176F2
there is also the option for M32176F3,F4 as well

I chose F2 bc its the older model and has 256k ram 144pin slot.

so does the above code make any sense?

obviously I am a newb here
Logged
oman
*
Offline Offline

Posts: 8


View Profile
« Reply #9 on: August 10, 2009, 06:29:31 PM »

That looks like a good rom dump to me. also the m32 code there that you disassembled seems to make sense.

Try using this pre-processing script that I wrote.

Start a new disassembly in IDA Pro...   
select CPU mitsubishi m32rx
don't add a ram segment or anything.. just load it with the default rom segment.
when it gives you a list of known m32 processors just select [cancel]

when the file is loaded then run this idc script.   It attempts to do some register tracing.  It's not perfect but it should still help a ton.
Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #10 on: August 10, 2009, 09:56:05 PM »

HOLY COW!!

thanks!
Logged
myto8
*
Offline Offline

Posts: 1


View Profile
« Reply #11 on: August 15, 2009, 01:16:50 AM »

It looks like reference to dtc are located at 04185 -05030
 
« Last Edit: August 15, 2009, 01:38:31 AM by myto8 » Logged
Hito
*
Offline Offline

Posts: 11


View Profile
« Reply #12 on: August 17, 2009, 05:33:03 PM »

Getting more and more into learning the m32 and assembler.

Some questions:

what are the named addresses that are shown in pink?

for example:
CAN0CNT
COGMSKS0

are the A/D inputs? or something?
did the script define these?

You mentioned that once we had the rom started you would point us towards the code that "does the flashing"  Is it not like the denso stuff where you have to write a kernal that gets loaded in?  Is the code already there?

Is it possible to flash just the calibration section of the rom rather than the entire code section as well?
Logged
franck
*
Offline Offline

Posts: 3


View Profile
« Reply #13 on: February 22, 2010, 04:26:41 AM »

im interresed for read impreza 99/2000
Which connectors do I have to Swith on/off to let software down/up load the ECU maps?

blacks?
Greens?
Both?

ecuexplorer ,tools,ecuQuery
Logged
franck
*
Offline Offline

Posts: 3


View Profile
« Reply #14 on: October 03, 2010, 12:25:24 AM »

im interresed for read impreza 99/2000
Which connectors do I have to Swith on/off to let software down/up load the ECU maps?

blacks?
Greens?
Both?

ecuexplorer ,tools,ecuQuery
up
Logged
Pages: [1]
Print
Jump to: