cannot pull rom from 04WRX

User topics relating to software that reflashes or modifes ECU code and data

Moderator: Freon

cannot pull rom from 04WRX

Postby nix » Sat Aug 29, 2009 9:10 pm

Hi all
I have used ecuexplorer, ecuflash and the old enginuity very extensively in the past to reprogram many different models including wrx, forester GT, forexter XT, liberty (legacy) GT and many STi variants of all.
I stopped doing this for what must now be about 2 years and recently installed bigger injectors in my own WRX (ADM 2004 WRX 2.0T, ECU ID AJ420-7550). Because of the need to remap my fueling and injectors I connected as per normal with my laptop and Openport 1.2 cable. Did the white block and green connector trick and tried to download my rom to work on.
This is as far as I have been able to get and I have spent about a week now trying many different combos to get this to work.
Before I give you all the errors, here is what I have tried.
2 different laptops and three different installations of windows XP (I have tried SP2, SP3 and SP2 that was upgraded to SP3).
ECUFlash versions 1.29a, 1.30, 1.34 and 1.42.2595 I used the ftdi driver remover in between each version as well as manually deleting the folder in program files.
2 different white connector blocks, both measured 0.0ohms to 0.01ohms neither made any difference.
Hand made jumper cables for the white block which measures 0.0ohms
Disconnecting the battery and holding brake pedal for 30 seconds
removing physical wiring to installed accessories (guages, stereo, etc) incase of a voltage drain problem
connecting a battery charger to the vehicle overnight to ensure battery was fully charged

What I have right now:
The car starts and runs as expected (rich with a lot of af learning)
I can view realtime data form the ecu while the car is running with no problems whatsoever.
I cannot test write nor can I read the rom to download it for editing.
I have owned the vehicle since new and done all my own programming on it (around 70-80 writes with no problems like this). I say this to rule out the possibility of an ecutek'd rom.
A sinking feeling that something is fried.

The results I get from various attempts to read:

EcuFlash using 2001-2005 non-USDM WRX/STi (Using 2002-2003 USDM WRX results are exactly the same)
[14:48:27.567] EcuFlash Version 1.42.2595
[14:48:27.567] OS Version Windows XP
[14:48:27.567] Qt Version 4.5.0
[14:48:27.587] 56 memory models read.
[14:48:27.587] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[14:48:27.837] 343 ROM metadata models scanned.
[14:48:27.837] checksum module "subarudbw" loaded.
[14:48:27.837] checksum module "mitsucan" loaded.
[14:48:27.837] flashing tool "wrx02" loaded.
[14:48:27.837] flashing tool "wrx04" loaded.
[14:48:27.837] flashing tool "sti04" loaded.
[14:48:27.837] flashing tool "sti05" loaded.
[14:48:27.837] flashing tool "mitsukernel" loaded.
[14:48:27.837] flashing tool "mitsukernelocp" loaded.
[14:48:27.837] flashing tool "mitsubootloader" loaded.
[14:48:27.837] flashing tool "shbootmode" loaded.
[14:48:27.837] flashing tool "shaudmode" loaded.
[14:48:27.837] flashing tool "subarucan" loaded.
[14:48:27.837] flashing tool "mitsucan" loaded.
[14:53:55.228] Using interface OpenPort 1.2 ISO Interface TX145ZuT
[14:54:02.899] denso02_bootloader_cmd_start
[14:54:04.151] denso02_bootloader_cmd_start
[14:54:05.383] denso02_bootloader_cmd_start
[14:54:06.614] denso02_bootloader_cmd_start
[14:54:07.856] denso02_bootloader_cmd_start
[14:54:08.297] kernel get version
[14:54:08.647] interface close
[14:54:08.647] interface close

EcuFlash using 2004-2005 USDM WRX
[14:57:33.432] EcuFlash Version 1.42.2595
[14:57:33.432] OS Version Windows XP
[14:57:33.432] Qt Version 4.5.0
[14:57:33.462] 56 memory models read.
[14:57:33.462] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[14:57:33.742] 343 ROM metadata models scanned.
[14:57:33.742] checksum module "subarudbw" loaded.
[14:57:33.742] checksum module "mitsucan" loaded.
[14:57:33.742] flashing tool "wrx02" loaded.
[14:57:33.742] flashing tool "wrx04" loaded.
[14:57:33.742] flashing tool "sti04" loaded.
[14:57:33.742] flashing tool "sti05" loaded.
[14:57:33.742] flashing tool "mitsukernel" loaded.
[14:57:33.742] flashing tool "mitsukernelocp" loaded.
[14:57:33.742] flashing tool "mitsubootloader" loaded.
[14:57:33.742] flashing tool "shbootmode" loaded.
[14:57:33.752] flashing tool "shaudmode" loaded.
[14:57:33.752] flashing tool "subarucan" loaded.
[14:57:33.752] flashing tool "mitsucan" loaded.
[14:57:38.900] Using interface OpenPort 1.2 ISO Interface TX145ZuT
[14:57:43.106] kernel get version
[14:57:43.516] SSM2 init
[14:57:43.687] SSM2 ECU ID is 3A 54 58 40 05
[14:57:45.730] interface close
[14:57:45.730] interface close

EcuExplorer 3.0.25 using WRX International 2001-2005 (non USDM) -OR- STi international 2001-2005 (non USDM) -OR- WRX USDM 2002-2003
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
<< PROCESS COMPLETE >>

EcuExplorer 3.0.25 using WRX USDM 2004-2005
1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
denso_cmd_0x81
validating denso kernel ram area addr: 020000 len: 0008
kernel flash disable
rkrv: preamble 1 no response
<< PROCESS COMPLETE >>

These results were all achieved with the green test mode connector connected, fans were cycling as per normal however the attampts did not stop the fans asn they would if the software happily connected and began to download from the ECU.

I am hoping somebody can make sense of this for me as I think I have exhausted checking everything over.
I do have a spare Openport 1.2 cable which I will be able to text next week (its in the office) is it possible that I can read realtime data with this cable but not download a rom (sounds unlikely to me but im open to the possibility).

Any advice or suggestions would be appreciated. If I can confirm something to be at fault, I can fix or replace it but not knowing is a real pain.
Im happy to run other tests if anyone needs additional data on top of whats above.

Thanks in advance
nix
 
Posts: 6
Joined: Mon Mar 20, 2006 5:29 am

Re: cannot pull rom from 04WRX

Postby nix » Mon Aug 31, 2009 2:23 am

OK I got this working.
For me the problem did turn out to be a malfunctioning OpenPort 1.2 cable
I can use it to log from the ECU perfectly I just cannot use it to download or (obviously) upload.
I have not bothered to check with a meter but I believe this is most likely that the cable is not sending out 12V to enable programming..

To anyone experiencing this level of problems, may I suggest trying an alternative OpenPort cable. I hope this fixes your problem for you as it did for me.
nix
 
Posts: 6
Joined: Mon Mar 20, 2006 5:29 am

Re: cannot pull rom from 04WRX

Postby SubeNSiren » Sat Mar 10, 2018 12:57 pm

I'm getting similar results with my Openport 2.0, which also has an sd port, perhaps I'll using a card instead of a cord.
SubeNSiren
 
Posts: 3
Joined: Wed Feb 13, 2008 1:04 am
Location: Siren WI


Return to Reflashing Software

Who is online

Users browsing this forum: No registered users and 0 guests

cron