ECUFlash 1.29 anyone?

Discussion in 'Modifications & DIY how-to' started by shiftynick, Dec 20, 2007.

  1. shiftynick

    shiftynick Member

    So this is what I'm working with here.

    I have an '01 RS with an '02 WRX swap.

    I've got my Tactrix cable, all of the software (ECUFlash 1.34, Enginuity, ecuEdit and ecuExplorer).
    I've been logging for weeks with all of the logging apps, no problems there.

    However, I am unable to read my ROM. At first it appeared I didn't have the flash block connector (not the green test connector). Well technically I don't have it, but it looks like maybe the two wires that were supposed to be in the flash block connector were actually moved to an empty spot in the green test connectors (which normally only has one wire in it), thus when you connect the two green plugs, the plugs effectively take care of test mode and the flash block at the same time. The only problem here is that these extra wires in the test connector plugs don't match the colors in the diagram for the flash block, and I haven't had time to tap in down by the ecu to see if these are the correct wires.

    So theory number 1 is that when the swap was performed, something didn't get finished with this part of the wiring. (I will eventually test this by putting a buddies '02 ECU in and seeing if I can read it, if not I probably have a wiring problem)

    Theory number 2 is that one of the previous owners had the car tuned with ecuTek and thus is blocking me from reading the ROM with tactrix/ecuFlash combo. (If i'm able to read my buddies ROM, then I will assume that the problem is with my ECU)

    Theory number 3 is that I'm having the same problem that others have had with v1.34 of ecuFlash, so I want to try the 1.29 version. I would get it off the openECU forums, but for some reason my account won't activate, and you can't download without an activated account.

    So, does anybody here have a copy of the ecuFlash 1.29 install?

    Or any other advice?
     
  2. Kokopelli

    Kokopelli Active Member

    ecuExplorer has the older version of ecuFlash built in. You can try that version but I am going to guess that the issue is with the wiring harness.

    Can you post the log that ecuflash creates when it tries to connect?
     
  3. shiftynick

    shiftynick Member

    I've given that shot too, no dice...

    I can post this tonight. I can tell you it's not so informative.
     
  4. shiftynick

    shiftynick Member

    From EcuFlash 1.34:

    [18:57:18.593] Version 1.34.1435
    [18:57:18.593] 11 memory models read.
    [18:57:18.625] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
    [18:57:19.562] 219 ROM metadata models scanned.
    [18:57:19.562] checksum module "subarudbw" loaded.
    [18:57:19.562] flashing tool "wrx02" loaded.
    [18:57:19.562] flashing tool "wrx04" loaded.
    [18:57:19.562] flashing tool "sti04" loaded.
    [18:57:19.562] flashing tool "sti05" loaded.
    [18:57:19.562] flashing tool "mitsukernel" loaded.
    [18:57:19.562] flashing tool "mitsukernelocp" loaded.
    [18:57:19.562] flashing tool "shbootmode" loaded.
    [18:57:32.187] Using interface OpenPort 1.3 Subaru TX47CB1O3088f4d5474235bff7dfb8b26a735ad4460096b8
    [18:57:45.437] denso02_bootloader_cmd_start
    [18:57:46.656] denso02_bootloader_cmd_start
    [18:57:47.875] denso02_bootloader_cmd_start
    [18:57:49.093] denso02_bootloader_cmd_start
    [18:57:50.312] denso02_bootloader_cmd_start
    [18:57:50.734] kernel get version
    [18:57:51.093] interface close
    [18:57:51.093] interface close


    From the ecuFlash built into ecuExplorer:

    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 >>


    EDIT --

    New info. I was able to get in touch with guy who performed the swap out in California, says it used to have an AccessPort on it working fine. So the wiring should be ok.
     
    Last edited: Dec 20, 2007
  5. WJM

    WJM Banned

    The EcuFlash 1.34 works just fine. The bug they had in 1.30/31/32/33 for the WRX's is worked out and gone.

    Otherwise, I do have 1.29a around somewhere....but I wouldnt use it since 1.34 is here and works fine.

    You need to go find the FSM wiring diagrams and make sure you can get the flash block wired correctly in order to read the ROM. Otherwise, it will not read. The DBW cars do not have this issue.

    Was the AP on the car before or after the swap? I am betting before...

    EcuFlash, any version, can read an AP'd ECU, whether it be married or not.

    Its pretty cool pulling a married AP map...you can see all the changes that Cobb has done.
     
  6. shiftynick

    shiftynick Member

    Good to know.

    The best I've been able to tell the flash block wires were moved to the test connector. Though the wires don't match the colors in the diagrams. I've been meaning to tap into the flash block pins at the ECU to check for continuity for between the wires in the test connector, just haven't had time yet.

    I was assuming after the swap, but now that you mention he wasn't specific. (The swap was done by Kevin at Garage Tuning out in California if that means anything.)

    Yeh that would be cool, but I'm still thinking that one of the previous owners may have switched over to EcuTek.
     
  7. WJM

    WJM Banned

    If its a later EcuTek...then you are screwed. Might as well buy easy ECU....or acquire another stock ECU.

    First thing to do is make the wiring PROPER and AS IF FACTORY for flashing...then try again.
     

Share This Page