Errors : dumping MY04 EU WRX ECU with Openport 1.2

[itanium]

Hi everyone

Whilst I've been able to read the realtime values from my ECU, I've been unable to dump my stock ECU. shorted the white connector and connected up the green connectors. Did the quick ignition trick but still unable to dump my ECU for archival purposes. The error message is as follows:

1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
kernel flash disable
rkrv: preamble 1 no response

Thanks for all pointers in advance!

[Thumper]

I had the same problem not long ago. Turned out ECUflash loaded a version of Openport drivers that wouldn't work with my Enginuity...strange. I reloaded version 1.0.2154.1 of Tetrix 1.2 Open port driver and things worked again. I don't know why the newer version didn't work. Hope this works for you.

[cboles]

your log is very strange to me. the first 3 lines seem to be part of a successful kernel loading log. the remaining lines appear to be from a second attempt at loading a kernel where a 02 WRX has been selected, not the MY04 that you mention in the posting subject line. are you selecting a 04 WRX?

colby

Hi everyone

Whilst I've been able to read the realtime values from my ECU, I've been unable to dump my stock ECU. shorted the white connector and connected up the green connectors. Did the quick ignition trick but still unable to dump my ECU for archival purposes. The error message is as follows:

1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
kernel flash disable
rkrv: preamble 1 no response

Thanks for all pointers in advance!

[itanium]

Thanks! Will surely give that a try!

I had the same problem not long ago. Turned out ECUflash loaded a version of Openport drivers that wouldn't work with my Enginuity...strange. I reloaded version 1.0.2154.1 of Tetrix 1.2 Open port driver and things worked again. I don't know why the newer version didn't work. Hope this works for you.

[itanium]

yup! selected the option for a 04 WRX. Tried selecting the option for a 02 WRX. Same error. If I can't dump my stock ecu's rom, I'm sure I can't flash it with a modified one. Haven't tried though...I have obtained a modified rom for my model with the boost and fueling adjusted. Was really hoping to flash it to my ecu...been itching to take out my fuel cut defender.

your log is very strange to me. the first 3 lines seem to be part of a successful kernel loading log. the remaining lines appear to be from a second attempt at loading a kernel where a 02 WRX has been selected, not the MY04 that you mention in the posting subject line. are you selecting a 04 WRX?

colby

Hi everyone

Whilst I've been able to read the realtime values from my ECU, I've been unable to dump my stock ECU. shorted the white connector and connected up the green connectors. Did the quick ignition trick but still unable to dump my ECU for archival purposes. The error message is as follows:

1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
kernel flash disable
rkrv: preamble 1 no response

Thanks for all pointers in advance!

[cboles]

could i see what your log contains when you just make a single attempt selecting 04 wrx?

[whitescooby]

I have been like you for the first time to read my ECU. After try many procedure, I success to read/flash my ECU. I'll show you the following....

To read/flash please follow this procedure
---Turn off ingnition
---Open Ecuexplorer program (or ecuflash)
---Click menu for reading ecu and name the hex file
---It will show "action required window": please connect green and white connector
---click the ok button and too quick turn on the ignition immediately
---program start to read (no radiator fan run and no CEL flash)

this work for MY05 WRX EU every time

[itanium]

Hi

Tried your method. Still no go...really don't have an idea what could be wrong. Could it be that I have a fuel cut defender device spliced into my ECU that tricks the ECU into thinking that it's nowhere near the boost cut limit of 1.27bar? Could that be interfering with the reading of the ECU rom? I get the live readings just fine. Just that I still can't dump my rom...Any ideas?

I have been like you for the first time to read my ECU. After try many procedure, I success to read/flash my ECU. I'll show you the following....

To read/flash please follow this procedure
---Turn off ingnition
---Open Ecuexplorer program (or ecuflash)
---Click menu for reading ecu and name the hex file
---It will show "action required window": please connect green and white connector
---click the ok button and too quick turn on the ignition immediately
---program start to read (no radiator fan run and no CEL flash)

this work for MY05 WRX EU every time

[RICK SCHU]

Some wrxs seem to have the diagnostic connectors on the passenger side disconnected from the factory. Does your radiator fan start going crazy when you turn on the ignition and have the driver side diagnostic connectors connected?

[itanium]

on the passenger side? hmm...will try to look for it then. What do they look like?

After connecting the green connectors, my fans do start spinning after a short while after the ignition is turned on. THat is the normal behaviour right??:?:

Some wrxs seem to have the diagnostic connectors on the passenger side disconnected from the factory. Does your radiator fan start going crazy when you turn on the ignition and have the driver side diagnostic connectors connected?