Page 1 of 1

04 STi ROM Read problems

PostPosted: Tue Feb 06, 2007 2:12 pm
by Tgui
I've been trying to pull a ROM image from my ECU with little success. This is an 04 STi with a UTEC. I read that having a UTEC installed won't affect ROM reading. In any case, I'm in map 0 pass through.

Here is the error I get when trying to pull the ROM. Well, here is the log from a number of attempts.

Any thoughts?

EDIT, Maybe this should be moved to the reflashing section of these forums.

Code: Select all
[13:56:50.789] Version 1.29.906
[13:56:50.799] 8 memory models read.
[13:56:51.840] 140 ROM metadata models read.
[13:56:51.840] checksum module "subarudbw" loaded.
[13:56:51.840] flashing tool "wrx02" loaded.
[13:56:51.840] flashing tool "wrx04" loaded.
[13:56:51.840] flashing tool "sti04" loaded.
[13:56:51.840] flashing tool "sti05" loaded.
[13:56:51.840] flashing tool "mitsukernel" loaded.
[13:56:51.840] flashing tool "mitsukernelocp" loaded.
[13:56:51.840] flashing tool "mitsubootloader" loaded.
[13:57:29.224] ssm2_init
[13:57:29.454] ssm2_init
[13:57:29.675] ssm2_init
[13:57:29.905] ssm2_init
[13:57:30.125] ssm2_init
[13:57:30.356] ssm2_init
[13:57:30.596] ssm2_init
[13:57:30.836] ssm2_init
[13:57:31.077] ssm2_init
[13:57:31.297] ssm2_init
[13:57:31.748] kernel get version
[13:57:32.349] validating denso kernel ram area addr: FFFF6000 len: 0008
[13:57:55.111] ssm2_init
[13:57:55.272] ECU ID is 2E 12 49 52 06
[13:57:55.272] ssm2_cmd_0x81
[13:57:55.322] ssm2_cmd_0x83
[13:57:55.382] denso challenge-response
[13:57:55.442] challenge is 7C E2 79 5A
[13:57:55.462] response is 00 47 38 2C
[13:57:55.512] ssm2_cmd_0x10
[13:57:55.942] validating denso kernel ram area addr: FFFF6000 len: 0D98
[13:58:03.764] ssm2_init
[13:58:03.994] ssm2_init
[13:58:04.214] ssm2_init
[13:58:04.445] ssm2_init
[13:58:04.685] ssm2_init
[13:58:04.905] ssm2_init
[13:58:05.126] ssm2_init
[13:58:05.356] ssm2_init
[13:58:05.576] ssm2_init
[13:58:05.797] ssm2_init
[13:58:06.267] kernel get version
[13:58:06.868] validating denso kernel ram area addr: FFFF6000 len: 0008
[13:59:26.973] ssm2_init
[13:59:27.134] ECU ID is 2E 12 49 52 06
[13:59:27.134] ssm2_cmd_0x81
[13:59:27.174] ssm2_cmd_0x83
[13:59:27.244] denso challenge-response
[13:59:27.304] challenge is A7 E7 F8 A9
[13:59:27.314] response is 09 3C AD E4
[13:59:27.374] ssm2_cmd_0x10
[13:59:27.795] validating denso kernel ram area addr: FFFF6000 len: 0D98
[13:59:41.574] ssm2_init
[13:59:41.735] ECU ID is 2E 12 49 52 06
[13:59:41.745] ssm2_cmd_0x81
[13:59:41.785] ssm2_cmd_0x83
[13:59:41.845] denso challenge-response
[13:59:41.915] challenge is 6A 33 DF C6
[13:59:41.925] response is 00 74 34 05
[13:59:41.985] ssm2_cmd_0x10
[13:59:42.426] validating denso kernel ram area addr: FFFF6000 len: 0D98
[13:59:52.730] ssm2_init
[13:59:52.961] ssm2_init
[13:59:53.201] ssm2_init
[13:59:53.431] ssm2_init
[13:59:53.672] ssm2_init
[13:59:53.912] ssm2_init
[13:59:54.142] ssm2_init
[13:59:54.373] ssm2_init
[13:59:54.603] ssm2_init
[13:59:54.833] ssm2_init
[13:59:55.284] kernel get version
[13:59:55.865] validating denso kernel ram area addr: FFFF6000 len: 0008
[14:01:09.130] ssm2_init
[14:01:09.280] ECU ID is 2E 12 49 52 06
[14:01:09.291] ssm2_cmd_0x81
[14:01:09.331] ssm2_cmd_0x83
[14:01:09.401] denso challenge-response
[14:01:09.471] challenge is C9 13 0D 5B
[14:01:09.471] response is 00 6D 5F 68
[14:01:09.531] ssm2_cmd_0x10
[14:01:09.971] validating denso kernel ram area addr: FFFF6000 len: 0D98
[14:01:52.613] ssm2_init
[14:01:52.763] ECU ID is 2E 12 49 52 06
[14:01:52.773] ssm2_cmd_0x81
[14:01:52.813] ssm2_cmd_0x83
[14:01:52.883] denso challenge-response
[14:01:52.943] challenge is 0A D7 AA B2
[14:01:52.943] response is 03 C6 6E D9
[14:01:53.003] ssm2_cmd_0x10
[14:01:53.444] validating denso kernel ram area addr: FFFF6000 len: 0D98

PostPosted: Wed Feb 07, 2007 11:49 am
by Tgui
I am such an RTARD!!!!

Remember people, connect the green connectors under the dash!!!!!

Sorry for the wasted bandwidth.

Holy monkey nuts. :(