Hi all,
Hoping someone can help. I’m trying to read the ECU on my JDM Subaru Impreza STi with a genuine Tactrix OpenPort 2.0, and I’m stuck. RomRaider logger works perfectly — I can view live data and logs — but ECUFlash refuses to read the ROM.
Here’s everything I’ve tried and confirmed:
ECU ID: 4304594005
CAL ID: A4TJ121B
Vehicle: JDM Subaru Impreza STi, drive-by-cable, 16-bit ECU
Tactrix Firmware: 1.17.4869
Tactrix Driver: 1.02.4870
ECUFlash Version: 1.44.4870 (I’ve also tried 1.29 but had DPinst64 errors)
RomRaider: Logger works, SSM fast-K communication confirmed
Green test connectors: Connected (fans come on, test mode active)
Black 2-pin flash jumper connectors: Connected
Definitions: Confirmed correct XML for ECU ID, flash method is wrx02, memmodel 68HC16Y5
Dummy ROM loaded in ECUFlash before attempting to read
Tried 'Test Write' – fails
USB cable confirmed working, COMMS confirmed via RomRaider
Logs shows:
Quote:
[16:39:51.448] using metadata XML ID read_wrx02 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml
[16:39:55.567] using metadata XML ID read_wrx02 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml
[16:39:55.583] J2534 API Version: 04.04
[16:39:55.583] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:39:55.583] Device Firmware Version: 1.17.4869
[16:39:55.583] Device Serial Number: TAU43LV5
[16:40:00.314] denso02_bootloader_cmd_start
[16:40:01.595] denso02_bootloader_cmd_start
[16:40:02.845] denso02_bootloader_cmd_start
[16:40:04.111] denso02_bootloader_cmd_start
[16:40:05.376] denso02_bootloader_cmd_start
[16:40:05.798] kernel get version
[16:40:06.111] interface close
[16:40:06.111] interface close
Any ideas? Could it be a flashing lock or something physical I’m missing? Not 100% on the flash jumpers.
Has anyone had to do anything special for a DBC 16-bit JDM STi with this CAL ID?
Cheers in advance!
Lehog
