openecu.org

Hello,

I have a question, it has been months since i have tried reading my ECU, but i was never able to, now i have a question would a low battery prevent me from reading my ECU? cause my car now has low battery and i want to try again but should i wait until i have a full new battery?

I only want to read my ECU rom to verify which model i have...

Below i will post my old logs of me trying to read my ECU, it just will not, which is pretty boring since i really want to be able to tune my ECU

[02:30:29.193] Version 1.29.906
[02:30:29.193] 8 memory models read.
[02:30:31.456] 140 ROM metadata models read.
[02:30:31.456] checksum module "subarudbw" loaded.
[02:30:31.456] flashing tool "wrx02" loaded.
[02:30:31.456] flashing tool "wrx04" loaded.
[02:30:31.456] flashing tool "sti04" loaded.
[02:30:31.456] flashing tool "sti05" loaded.
[02:30:31.456] flashing tool "mitsukernel" loaded.
[02:30:31.456] flashing tool "mitsukernelocp" loaded.
[02:30:31.456] flashing tool "mitsubootloader" loaded.
[02:30:45.857] denso02_bootloader_cmd_start
[02:30:47.058] denso02_bootloader_cmd_start
[02:30:48.260] denso02_bootloader_cmd_start
[02:30:49.462] denso02_bootloader_cmd_start
[02:30:50.664] denso02_bootloader_cmd_start
[02:30:51.084] kernel get version
[02:31:09.591] ssm2_init
[02:31:09.761] ECU ID is 3D FFFFFFA4 58 30 05
[02:31:09.761] ssm2_cmd_0x81
[02:42:43.899] Version 1.29.906
[02:42:43.909] 8 memory models read.
[02:42:46.162] 140 ROM metadata models read.
[02:42:46.162] checksum module "subarudbw" loaded.
[02:42:46.162] flashing tool "wrx02" loaded.
[02:42:46.162] flashing tool "wrx04" loaded.
[02:42:46.162] flashing tool "sti04" loaded.
[02:42:46.162] flashing tool "sti05" loaded.
[02:42:46.162] flashing tool "mitsukernel" loaded.
[02:42:46.162] flashing tool "mitsukernelocp" loaded.
[02:42:46.162] flashing tool "mitsubootloader" loaded.
[02:43:20.382] ssm2_init
[02:43:20.552] ECU ID is 3D FFFFFFA4 58 30 05
[02:43:20.552] ssm2_cmd_0x81
[02:43:37.026] denso02_bootloader_cmd_start
[02:43:38.227] denso02_bootloader_cmd_start
[02:43:39.429] denso02_bootloader_cmd_start
[02:43:40.631] denso02_bootloader_cmd_start
[02:43:41.833] denso02_bootloader_cmd_start
[02:43:42.273] kernel get version
[02:43:53.579] denso02_bootloader_cmd_start
[02:43:54.781] denso02_bootloader_cmd_start
[02:43:55.983] denso02_bootloader_cmd_start
[02:43:57.185] denso02_bootloader_cmd_start
[02:43:58.386] denso02_bootloader_cmd_start
[02:43:58.807] kernel get version
[02:44:12.797] ssm2_init
[02:44:12.957] ECU ID is 3D FFFFFFA4 58 30 05
[02:44:12.967] ssm2_cmd_0x81
[02:44:27.759] ssm2_init
[02:44:27.919] ECU ID is 3D FFFFFFA4 58 30 05
[02:44:27.929] ssm2_cmd_0x81
[02:44:39.776] ssm2_init
[02:44:39.936] ECU ID is 3D FFFFFFA4 58 30 05
[02:44:39.946] ssm2_cmd_0x81
[02:44:54.527] ssm2_init
[02:44:54.687] ECU ID is 3D FFFFFFA4 58 30 05
[02:44:54.697] ssm2_cmd_0x81

ghosttown hello ghosttown hello

anyone?

Reflashing- maybe. Reading- no. I've read a Subaru ECU down to 7.5V at the pins... if your battery voltage is that low, you have other problems to deal with first.

What type of car is it and which protocol are you using?

It appears you have a 2005 WRX with an ECU calibrated for the South America market. You can confirm this by hooking up an OBD-II scan tool and going to the Vehicle Information section. The calibration ID (CID) should be A4RM200K if I am correct.

In order to read or write this ECU, you need to install this flash block connector: