RomRaider

Hey,

I found this threat:

http://www.evoxforums.com/forums/showthread.php?t=35078

decribing using ECUFlash Recovery Mode on a Mitsubishi EVO.

Did someone tryed to recovery with openPORT 2.0 and ECUflash an Subaru CAN-based ECU too ?

For the EVO Pin 12 of OP2.0 is used and connected to Pin 80 of the ECU. Subaru doesn´t got PIN 12 used on OBD-plug. So what signal is on Pin 80 Mitsubishi ecu ?

I know SHBootmode will do the same job perfectly, but if ECUFlash will do the same job, maybe it can be used to wirte the EURO4 Diesel-ECU.

In this case a simple on-bench wire will give a comfortable wirte options

BR Jochen

So

Just found another threat in the same forum with a nice pictured describiton:

http://www.evoxforums.com/forums/showthread.php?t=29820

Here the CAN also needs to be connected ..
Is it realy needed ?

As I unterstand, SHbootmode needs a watchdog, so maybe Pin80 of the Mitsu-ECU could be watch-dog ? Doesn´t expact this signal on a OEM-plug...

But most importend question:
how to connect the recovery-mode to a Subaru ECU ...

BR

Tracing the numbers using the pinout provided here: http://roadraceengineering.com/evox/tec ... wiring.htm

It uses k-line, can hi, can low, and "Flash EP-ROM Power Supply".

This would be VERY useful for testing hacked roms on CAN cars.

If such a method exists in the Subaru CAN ECU, I would expect the SSM3 tools to reflect it as an option. Maybe someone with possession of a SSM3 can chime in.

M32R based Mitsubishi ecu has BootMode pin that stops watchdog and force bootmode negotiation protocol thru k-line. ROM code is not involved and could not do any harm being corrupted provided access keys written inside the ROM image are not lost.

This is not the case for SH based ecu's.

Ok

So, not chance to recover this comfortable way for Subaru...

Would have been nice, if it has worked.

Thanks for the info

Why not ?
Just solder an appropriate cable.

BootMode on the SH process uses a different serial port than the one connected to the OBD connector. That's why you need to open the case and solder direct to the board.
SSM3 tools as far as I can tell are not going to be able to recover a bricked ECU like EcuFlash can with it's recovery mode. In addition to the ports, it's a whole different process talking to the CPUs SH programming code for flash recovery compared to talking to the normal programming kernel to flash a edited map.

Looks like my test-ECU with AUD-SHBootMode-Piasini-all-in-one connector



I stuggle a bit..

Do I unterstand correct:
The way the Mitsubishi ECU is recovered is totaly different to SHBootMode recovery ?
That´s the reason, why Mitsubishi is able to recover with openPORT2.0 and Subaru need it´s one interface with a UART transiver and watchdog.

As you know I still searching for a opensource solution for the subaru diesel.
If recovery-mode of ECUflash would work like on the Misubishi too, it could be a way of everyone, but as I know jet, it isn´t.

I short contact to Mr. Bowle let me belive there is a chance ECUFlash will got on the devellopment of the SubaruCAN-Diesel soltions, but no more infos or news yet.

As you can read, the BRZ seem to be read and wirte with the functionality like the Diesel. ECUflash worte, they will work on BRZ..
But as long as, there is nothing new, I will "tease" you with asking stupid questions to search for every way I can see

Sorry for that, and thanks you all of your hints, help and explimentations


Jochen

Once again:

Mitsubishi M32R based ecu's I have seen:
- do have primary BootMode bootloader outside UserROM where ecu code and calibrations reside
- do not erase UserROM after BootMode bootloader is entered
- do use the same serial port for diagnostics and BootMode bootloader

Denso SH based ecu's I have seen:

- do have primary BootMode bootloader outside UserROM where ecu code and calibrations reside
- do have secondary bootloader that is used by FHI and ecuFlash software that may be corrupt by ecuFlash
- do erase UserROM after BootMode bootloader is entered
- do use different serial ports for diagnostics and BootMode bootloader

That mean that Denso ecu may need recovery on the bench.