ECU (or PCM) information requested

Professor MSP

Member
:
2003 Black Mica Mazdaspeed Protege
There is a local R & D outfit that is interested in developing new maps for the MSP and a device for loading them through the ODB II portthey have already successfully completed this for the MSM (among other tuner cars). They want to develop a device similar to the Superchips application. Indeed, the fellow I was speaking with was part of the original team that developed the Superchips hand-held programmer.

In order to move this forward, the R & D manager would like a picture of the Mazdaspeed ECU/PCM, specifically, all of the information written on it. Can anybody please help me out?

Alternatively, maybe one of you Mazda technicians could simply reply with the pertinent information written on the ECU/PCM.

Any and all help is much appreciated.
 
here ya go its a p5 ecu but hopefully it helps
 

Attachments

  • ecu1.webp
    ecu1.webp
    19.4 KB · Views: 310
  • ecu2.webp
    ecu2.webp
    18.7 KB · Views: 290
  • ecu3.webp
    ecu3.webp
    16.8 KB · Views: 272
i sold my msp ecu awhile back. these are the only pics i have of it.

http://www.mazdas247.com/forum/showthread.php?t=123681985&page=2


what is the company name or product name?



here is some info that ken at protege garage posted in response to flashing the msp ecu(or any protege ecu for that matter):

"its not that simple and its been discussed to death here. dealers can do it because they have $10,000 units designed to do so. dealers also do not write the code, thats done overseas. many very experienced companies have tried to reflash the computers in these cars and the ones in miatas, etc etc and failed. it has taken cobb years to crack the rx8 ecu and over a year to supposedly crack the mazda3 ecu.

besides the simple fact - these cars are no longer in production, modified by a small group of people and therefore not worth the return/risk investment for 90% of the companies out there. there is a Ford tuner who was mildly (and i stress MILDLY) interested in doing a protege reflash but he is pretty sure the start up costs to do so would be extremely high.

i'm not trying to come across as an asshole here. it was discussed back in 02 and 03 when turboing the proteges was all the rage. bell engineering tried to do it. flyin miata tried to do it. ECUs were send out to companies across the country to have them do it. the information was posted long ago. the reason its not discussed any more is simply because of that, that it is a dead issue put to rest along ago. and yes i have posted this information before.

to clarify the question and the answer; can the protege ECU be reflashed with custom maps for various performance modifications in the manner that an accessport reflashes a subaru? no, it has not been successfully and cannot be done.

as for the "10,000 dollar machine", its a dealer WDS that among other things diagnoses your vehicle sensor by sensor, value by value to isolate problems faster. the machines can reflash the computer with a map loaded onto it by a mazda disc. you cannot write a map and put it on the unit. they do not even write the maps in this country. the best thing you could, in theory, do is to reflash an ECU with an MP3 or MSP map and give non turbo protege owners a cheap way to open power or allow for boost. i have yet to find a dealer or mechanic that will do this for me under the table or otherwise. some people say they have gotten thier local guy to do it for them you would also need to know the 'part number' of the individual reflash as its not going to come up in the menu as "msp ecu map" or "mp3 map"

i have tried to buy the machine to reflash the maps with mp3 or msp maps and been refused sale of it from several sources.

this of course would do nothing for msp owners. and putting an msp map on a stock protege wanting to go turbo is not the *best* way to do it."


goodluck. if they could flash it and sell for a reasonable price, they would steal soooo many sales!
 
I'll be publicly posting the MSP / MP3 binaries online in the near future.
Good luck with any tuner.... the Ford binaries are easy as hell to decode....
but the Mazda binaries are pretty much useless as far as tuning is concerned.
 
I have the binary data files for the following :
2002 LX [FS8L-18881-C]
2001 P5 [FSAE-18881-A]

I haven't had a chance to pull my MazdaSpeed ecu... or my friend's MP3 ECU.

Good luck breaking the encryption.
 
I have the binary data files for the following :
2002 LX [FS8L-18881-C]
2001 P5 [FSAE-18881-A]

I haven't had a chance to pull my MazdaSpeed ecu... or my friend's MP3 ECU.

Good luck breaking the encryption.

so you are going to have the ability to flash the lx and p5 ecu with whatever map you please?
 
so you are going to have the ability to flash the lx and p5 ecu with whatever map you please?
Yep, I'm building a library of different binary data files that I can flash onto any(manual) Ford EEC-V ECU.
HUGE THANKS Reuben Johnston Engineering [RJE] to for lending my the hardware/software.

I'll have information posted in a thread when Antoine grants me AMM status.
 
Yep, I'm building a library of different binary data files that I can flash onto any(manual) Ford EEC-V ECU.
HUGE THANKS Reuben Johnston Engineering [RJE] to for lending my the hardware/software.

I'll have information posted in a thread when Antoine grants me AMM status.

so is loading different binary data files similar to what the cobb units or diablo units do?
 
The cobb units erase the stock binary data and flash modified binaries onto the ECU via the OBD-II port.

I'm hoping to start deciphering the binaries to start flashing modified maps onto the ECU... but that'll be a long time from now.
 
Just thinking about this today; does anyone know what the actual makeup of INSIDE the ECU is? What main chips are in there? (not talking about supporting ICs for sensors and s***). Based on the level of how much a pain in the ass this whole operation is, im guessing chip markings will be covered or sanded off..

but,can't someone just get a dump off an onboard EEPROM (if there is one...) or some other memory?

I'm assuming the maps themselves aren't stored encrypted in the ECU...it would have to decrypt every time it loads, which seems like a waste of time. Plus, if you only needed to send an encrypted file, you would just need to know the WDS protocol, and then you could at least switch between various "official"maps. I could be totally wrong though; im just theorizing outloud here. I'm thinking the WDS decrypts the file and knows the proper communication protocol to get it into the ECU, thats why I'm thinking that we need to work from the other end. Start at the ECU itself, and not mess with files provided by Mazda.

Someday this b**** will be broken.
I mean, comeon, no one else is encrypting thier ECUs? Audi/VW/Subaru? All just out in the open? What does Mazda need to encrypt so bad for midlevel economy cars?
 
From what I've found, you'll need to create a script for to read the intel chip using the "Flash and burn" program. Each script is different for each chip.
If anyone wants to chip in, I'll ship a stock sedan ECU to the programmer to see if he can write a script to read our binary data via the J3 port on the ecu.

Hardware required :
-Burn1
-F2A
-F2E
-F3

http://www.moates.net/index.php?cPath=25_35

Once the binaries have been read, they can be decoded and/or modified.
Making a program to edit your settings would be the easyest part of the entire thing.
 
Last edited:
Back