Can't flash or read the ROM from your ECU - Start Here!
#92
I just went through this for a couple weeks. I'm not sure if they changed the driver or they changed windows but i could not get evoscan running on a 1.3U cable at all... only ECUFlash.
I spent the money on the 2.0 cable and EvoScan came right to life...
I spent the money on the 2.0 cable and EvoScan came right to life...
#95
hi having problems reading rom from 2004 jdm evo 8 ecu
have attached the log
[23:24:52.543] FTDI Driver Version 2.12.12
[23:24:52.559] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.559] interface close
[23:24:52.628] FTDI Driver Version 2.12.12
[23:24:52.643] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.643] interface close
[23:24:52.697] FTDI Driver Version 2.12.12
[23:24:52.712] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.712] interface close
[23:24:52.779] FTDI Driver Version 2.12.12
[23:24:52.781] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.781] interface close
[23:24:52.844] FTDI Driver Version 2.12.12
[23:24:52.859] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.859] interface close
[23:24:52.913] FTDI Driver Version 2.12.12
[23:24:52.928] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.928] interface close
[23:24:56.635] using metadata XML ID read_evo7 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml
[23:24:56.651] FTDI Driver Version 2.12.12
[23:24:56.667] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:58.721] sending init sequence 1 (F0F0)
[23:24:58.923] interface close
[23:25:27.659] using metadata XML ID read_evo7 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml
[23:25:27.675] FTDI Driver Version 2.12.12
[23:25:27.690] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:25:29.669] sending init sequence 1 (F0F0)
[23:25:29.870] interface close
any ideas please(have tried everything on this thread)
have attached the log
[23:24:52.543] FTDI Driver Version 2.12.12
[23:24:52.559] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.559] interface close
[23:24:52.628] FTDI Driver Version 2.12.12
[23:24:52.643] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.643] interface close
[23:24:52.697] FTDI Driver Version 2.12.12
[23:24:52.712] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.712] interface close
[23:24:52.779] FTDI Driver Version 2.12.12
[23:24:52.781] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.781] interface close
[23:24:52.844] FTDI Driver Version 2.12.12
[23:24:52.859] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.859] interface close
[23:24:52.913] FTDI Driver Version 2.12.12
[23:24:52.928] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.928] interface close
[23:24:56.635] using metadata XML ID read_evo7 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml
[23:24:56.651] FTDI Driver Version 2.12.12
[23:24:56.667] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:58.721] sending init sequence 1 (F0F0)
[23:24:58.923] interface close
[23:25:27.659] using metadata XML ID read_evo7 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml
[23:25:27.675] FTDI Driver Version 2.12.12
[23:25:27.690] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:25:29.669] sending init sequence 1 (F0F0)
[23:25:29.870] interface close
any ideas please(have tried everything on this thread)
#96
new with ecuflash
I just read my ecu with openport 2.0 and I think a don't have the right definition file yet im running a lancer 2006 with a mirage ecu md351551 at first it downloaded a readimage.srf file I saved it as a .bin but it wont open any hel help will be thank full
#97
Evolving Member
iTrader: (8)
My1.3u cable isn't able to read jack! Can anyone tell me where to go to get my Rom ID so evoscan and ecuflash can get read that the cable is connected?
[14:41:35.933] Logging to file C:/Users/topgun/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20180623t144135.txt [14:41:35.933] EcuFlash Version 1.44.4799
[14:41:35.933] OS Version Windows 10
[14:41:35.933] Kernel Type winnt
[14:41:35.933] Kernel Version 10.0.16299
[14:41:35.933] CPU x86_64
[14:41:35.933] Product Name Windows 10
[14:41:35.933] Product Type windows
[14:41:35.933] Product Version 10
[14:41:35.933] Qt Version 5.6.0
[14:41:35.933] Qwt Version 6.1.2
[14:41:35.933] QwtPlot3D Version 0.2.6
[14:41:35.933] Boost Version 1.60
[14:41:35.933] FTDI Library Version 3.02.11
[14:41:35.933] Openport J2534 Library Version 1.02.4798
[14:41:35.940] 67 memory models read.
[14:41:35.940] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[14:41:36.072] 745 ROM metadata models scanned.
[14:41:36.072] checksum module "subarudbw" loaded.
[14:41:36.072] checksum module "subarudiesel" loaded.
[14:41:36.072] checksum module "subaruhitachi" loaded.
[14:41:36.072] checksum module "mitsucan" loaded.
[14:41:36.072] checksum module "mitsuh8" loaded.
[14:41:36.072] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[14:41:36.072] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[14:41:36.222] flashing tool "wrx02" loaded.
[14:41:36.238] flashing tool "wrx04" loaded.
[14:41:36.239] flashing tool "sti04" loaded.
[14:41:36.239] flashing tool "sti05" loaded.
[14:41:36.255] flashing tool "mitsucan" loaded.
[14:41:36.255] flashing tool "mitsukernel" loaded.
[14:41:36.255] flashing tool "mitsukernelocp" loaded.
[14:41:36.255] flashing tool "mitsubootloader" loaded.
[14:41:36.255] flashing tool "shbootmode" loaded.
[14:41:36.255] flashing tool "shaudmode" loaded.
[14:41:36.255] flashing tool "subarucan" loaded.
[14:41:36.255] flashing tool "subarucand" loaded.
[14:41:36.255] flashing tool "subarubrz" loaded.
[14:41:36.271] flashing tool "subaruhitachi" loaded.
[14:41:36.294] FTDI Driver Version 2.12.12
[14:41:36.325] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.327] interface close
[14:41:36.644] FTDI Driver Version 2.12.12
[14:41:36.664] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.666] interface close
[14:41:36.723] FTDI Driver Version 2.12.12
[14:41:36.741] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.742] interface close
[14:41:36.801] FTDI Driver Version 2.12.12
[14:41:36.818] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.820] interface close
[14:41:36.881] FTDI Driver Version 2.12.12
[14:41:36.898] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.900] interface close
[14:41:36.957] FTDI Driver Version 2.12.12
[14:41:36.975] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.977] interface close
[14:41:35.933] Logging to file C:/Users/topgun/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20180623t144135.txt [14:41:35.933] EcuFlash Version 1.44.4799
[14:41:35.933] OS Version Windows 10
[14:41:35.933] Kernel Type winnt
[14:41:35.933] Kernel Version 10.0.16299
[14:41:35.933] CPU x86_64
[14:41:35.933] Product Name Windows 10
[14:41:35.933] Product Type windows
[14:41:35.933] Product Version 10
[14:41:35.933] Qt Version 5.6.0
[14:41:35.933] Qwt Version 6.1.2
[14:41:35.933] QwtPlot3D Version 0.2.6
[14:41:35.933] Boost Version 1.60
[14:41:35.933] FTDI Library Version 3.02.11
[14:41:35.933] Openport J2534 Library Version 1.02.4798
[14:41:35.940] 67 memory models read.
[14:41:35.940] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[14:41:36.072] 745 ROM metadata models scanned.
[14:41:36.072] checksum module "subarudbw" loaded.
[14:41:36.072] checksum module "subarudiesel" loaded.
[14:41:36.072] checksum module "subaruhitachi" loaded.
[14:41:36.072] checksum module "mitsucan" loaded.
[14:41:36.072] checksum module "mitsuh8" loaded.
[14:41:36.072] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[14:41:36.072] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[14:41:36.222] flashing tool "wrx02" loaded.
[14:41:36.238] flashing tool "wrx04" loaded.
[14:41:36.239] flashing tool "sti04" loaded.
[14:41:36.239] flashing tool "sti05" loaded.
[14:41:36.255] flashing tool "mitsucan" loaded.
[14:41:36.255] flashing tool "mitsukernel" loaded.
[14:41:36.255] flashing tool "mitsukernelocp" loaded.
[14:41:36.255] flashing tool "mitsubootloader" loaded.
[14:41:36.255] flashing tool "shbootmode" loaded.
[14:41:36.255] flashing tool "shaudmode" loaded.
[14:41:36.255] flashing tool "subarucan" loaded.
[14:41:36.255] flashing tool "subarucand" loaded.
[14:41:36.255] flashing tool "subarubrz" loaded.
[14:41:36.271] flashing tool "subaruhitachi" loaded.
[14:41:36.294] FTDI Driver Version 2.12.12
[14:41:36.325] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.327] interface close
[14:41:36.644] FTDI Driver Version 2.12.12
[14:41:36.664] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.666] interface close
[14:41:36.723] FTDI Driver Version 2.12.12
[14:41:36.741] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.742] interface close
[14:41:36.801] FTDI Driver Version 2.12.12
[14:41:36.818] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.820] interface close
[14:41:36.881] FTDI Driver Version 2.12.12
[14:41:36.898] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.900] interface close
[14:41:36.957] FTDI Driver Version 2.12.12
[14:41:36.975] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7
[14:41:36.977] interface close
#100
This is their latest driver. I had bad issues and the same driver solved everything for me
http://www.evoscan.com/drivers/openport1.3drivers.zip
http://www.evoscan.com/drivers/openport1.3drivers.zip
#101
Evolving Member
iTrader: (8)
This is their latest driver. I had bad issues and the same driver solved everything for me
http://www.evoscan.com/drivers/openport1.3drivers.zip
http://www.evoscan.com/drivers/openport1.3drivers.zip
#102
You have to go into device manager and manually in-install the drivers then unplug the 1.3u cable, then reboot. Then install the 1.3u driver and then plug the cable back in. Open the device manager and make sure windows isnt try to install an internet driver over the 1.3u.
its tricky but it will work with the right process.. also remember to disable the firewall or allow ecu flash and evo scan through.
its tricky but it will work with the right process.. also remember to disable the firewall or allow ecu flash and evo scan through.
#103
I have a Lancer Ralliart 2009 that obviously has been tuned previously. It made around 240hp at the hubs.
I can't seem to be able to read it using my ECUFlash-stuff that normally work on the Mitsus I have tried it on... even Lancer Ralliarts.
Any ideas what can be causing this?
This is how the log from ECUFlash looks every time:
[19:07:29.080] Device Firmware Version: 1.16.4769
[19:07:29.080] Device Serial Number: TAtG2OXX
[19:07:30.918] -- loading kernel --
[19:07:30.918] -- connecting to kernel --
[19:07:30.918] kernel get version
[19:07:31.244] ECU HW part number : 1860B107
[19:07:31.269] ECU SW part number : 1860B10702
[19:07:31.289] VIN : JMBLMCX4AAU000582
[19:07:33.222] -- unlocking ECU --
[19:07:33.222] starting session...
[19:07:33.232] requesting seed...
[19:07:33.252] interface close
[19:07:33.252] interface close
Car is having a battery charger on.
I have tried running the Mitsubishi ECU Unlocker simultaneously.
I have tried switching on the ignition in various ways before/during/after having pressed the "OK" (readbutton) in ECUFlash.
I've also been reading a little here and there but not found anything that matches my problems.
Any ideas?
I can't seem to be able to read it using my ECUFlash-stuff that normally work on the Mitsus I have tried it on... even Lancer Ralliarts.
Any ideas what can be causing this?
This is how the log from ECUFlash looks every time:
[19:07:29.080] Device Firmware Version: 1.16.4769
[19:07:29.080] Device Serial Number: TAtG2OXX
[19:07:30.918] -- loading kernel --
[19:07:30.918] -- connecting to kernel --
[19:07:30.918] kernel get version
[19:07:31.244] ECU HW part number : 1860B107
[19:07:31.269] ECU SW part number : 1860B10702
[19:07:31.289] VIN : JMBLMCX4AAU000582
[19:07:33.222] -- unlocking ECU --
[19:07:33.222] starting session...
[19:07:33.232] requesting seed...
[19:07:33.252] interface close
[19:07:33.252] interface close
Car is having a battery charger on.
I have tried running the Mitsubishi ECU Unlocker simultaneously.
I have tried switching on the ignition in various ways before/during/after having pressed the "OK" (readbutton) in ECUFlash.
I've also been reading a little here and there but not found anything that matches my problems.
Any ideas?
#104
Newbie
Join Date: Nov 2019
Location: Collarenebri, NSW
Posts: 9
Likes: 0
Received 0 Likes
on
0 Posts
Hi All,
I have attached the log from a scan on my MK Triton 6g72. Can anyone point me towards a solution here. This is using 1.3U cable and ecuflash 1.44. Any help much appreciated.
[17:30:13.463] Logging to file C:/Users/pmleg/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20191117t173013.txt
[17:30:13.463] EcuFlash Version 1.44.4799
[17:30:13.463] OS Version Windows 10
[17:30:13.463] Kernel Type winnt
[17:30:13.463] Kernel Version 10.0.18362
[17:30:13.463] CPU x86_64
[17:30:13.463] Product Name Windows 10
[17:30:13.463] Product Type windows
[17:30:13.463] Product Version 10
[17:30:13.463] Qt Version 5.6.0
[17:30:13.463] Qwt Version 6.1.2
[17:30:13.463] QwtPlot3D Version 0.2.6
[17:30:13.463] Boost Version 1.60
[17:30:13.463] FTDI Library Version 3.02.11
[17:30:13.463] Openport J2534 Library Version 1.02.4798
[17:30:13.469] 67 memory models read.
[17:30:13.469] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[17:30:13.615] 745 ROM metadata models scanned.
[17:30:13.615] checksum module "subarudbw" loaded.
[17:30:13.615] checksum module "subarudiesel" loaded.
[17:30:13.615] checksum module "subaruhitachi" loaded.
[17:30:13.615] checksum module "mitsucan" loaded.
[17:30:13.615] checksum module "mitsuh8" loaded.
[17:30:13.615] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[17:30:13.615] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[17:30:13.616] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[17:30:13.695] flashing tool "wrx02" loaded.
[17:30:13.695] flashing tool "wrx04" loaded.
[17:30:13.712] flashing tool "sti04" loaded.
[17:30:13.712] flashing tool "sti05" loaded.
[17:30:13.730] flashing tool "mitsucan" loaded.
[17:30:13.730] flashing tool "mitsukernel" loaded.
[17:30:13.730] flashing tool "mitsukernelocp" loaded.
[17:30:13.730] flashing tool "mitsubootloader" loaded.
[17:30:13.730] flashing tool "shbootmode" loaded.
[17:30:13.730] flashing tool "shaudmode" loaded.
[17:30:13.730] flashing tool "subarucan" loaded.
[17:30:13.745] flashing tool "subarucand" loaded.
[17:30:13.745] flashing tool "subarubrz" loaded.
[17:30:13.745] flashing tool "subaruhitachi" loaded.
[17:30:13.788] FTDI Driver Version 2.12.12
[17:30:13.804] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:13.806] interface close
[17:30:13.861] FTDI Driver Version 2.12.12
[17:30:13.878] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:13.881] interface close
[17:30:13.939] FTDI Driver Version 2.12.12
[17:30:13.957] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:13.960] interface close
[17:30:14.029] FTDI Driver Version 2.12.12
[17:30:14.050] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:14.052] interface close
[17:30:14.130] FTDI Driver Version 2.12.12
[17:30:14.154] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:14.157] interface close
[17:30:14.215] FTDI Driver Version 2.12.12
[17:30:14.238] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:14.241] interface close
[17:30:57.226] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[17:30:57.231] FTDI Driver Version 2.12.12
[17:30:57.250] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:31:01.543] sending init sequence 2
[17:31:01.553] got 0x11 response
[17:31:01.553] sending init sequence 3
[17:31:01.929] entering bootloader
[17:31:01.930] sending kernel size (2029)
[17:31:01.951] sending kernel load address (0x0000F000)
[17:31:01.971] uploading kernel
[17:31:02.299] verifying kernel checksum response
[17:31:02.309] kernel valid
[17:31:02.518] kernel get version
[17:31:02.538] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.07
[17:31:02.538] reading kernel comm buffer size
[17:31:02.549] comm buffer size set to 256
[17:31:02.549] reading kernel flash buffer size
[17:31:02.558] flash buffer size set to 1024
[17:31:02.571] interface close
I have attached the log from a scan on my MK Triton 6g72. Can anyone point me towards a solution here. This is using 1.3U cable and ecuflash 1.44. Any help much appreciated.
[17:30:13.463] Logging to file C:/Users/pmleg/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20191117t173013.txt
[17:30:13.463] EcuFlash Version 1.44.4799
[17:30:13.463] OS Version Windows 10
[17:30:13.463] Kernel Type winnt
[17:30:13.463] Kernel Version 10.0.18362
[17:30:13.463] CPU x86_64
[17:30:13.463] Product Name Windows 10
[17:30:13.463] Product Type windows
[17:30:13.463] Product Version 10
[17:30:13.463] Qt Version 5.6.0
[17:30:13.463] Qwt Version 6.1.2
[17:30:13.463] QwtPlot3D Version 0.2.6
[17:30:13.463] Boost Version 1.60
[17:30:13.463] FTDI Library Version 3.02.11
[17:30:13.463] Openport J2534 Library Version 1.02.4798
[17:30:13.469] 67 memory models read.
[17:30:13.469] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[17:30:13.615] 745 ROM metadata models scanned.
[17:30:13.615] checksum module "subarudbw" loaded.
[17:30:13.615] checksum module "subarudiesel" loaded.
[17:30:13.615] checksum module "subaruhitachi" loaded.
[17:30:13.615] checksum module "mitsucan" loaded.
[17:30:13.615] checksum module "mitsuh8" loaded.
[17:30:13.615] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[17:30:13.615] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[17:30:13.616] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[17:30:13.695] flashing tool "wrx02" loaded.
[17:30:13.695] flashing tool "wrx04" loaded.
[17:30:13.712] flashing tool "sti04" loaded.
[17:30:13.712] flashing tool "sti05" loaded.
[17:30:13.730] flashing tool "mitsucan" loaded.
[17:30:13.730] flashing tool "mitsukernel" loaded.
[17:30:13.730] flashing tool "mitsukernelocp" loaded.
[17:30:13.730] flashing tool "mitsubootloader" loaded.
[17:30:13.730] flashing tool "shbootmode" loaded.
[17:30:13.730] flashing tool "shaudmode" loaded.
[17:30:13.730] flashing tool "subarucan" loaded.
[17:30:13.745] flashing tool "subarucand" loaded.
[17:30:13.745] flashing tool "subarubrz" loaded.
[17:30:13.745] flashing tool "subaruhitachi" loaded.
[17:30:13.788] FTDI Driver Version 2.12.12
[17:30:13.804] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:13.806] interface close
[17:30:13.861] FTDI Driver Version 2.12.12
[17:30:13.878] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:13.881] interface close
[17:30:13.939] FTDI Driver Version 2.12.12
[17:30:13.957] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:13.960] interface close
[17:30:14.029] FTDI Driver Version 2.12.12
[17:30:14.050] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:14.052] interface close
[17:30:14.130] FTDI Driver Version 2.12.12
[17:30:14.154] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:14.157] interface close
[17:30:14.215] FTDI Driver Version 2.12.12
[17:30:14.238] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:30:14.241] interface close
[17:30:57.226] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[17:30:57.231] FTDI Driver Version 2.12.12
[17:30:57.250] Using interface OpenPort 1.3 Universal TX2TcHgT5bb1b3fb2b1ee57650389f90ac8c713e81fc06f4
[17:31:01.543] sending init sequence 2
[17:31:01.553] got 0x11 response
[17:31:01.553] sending init sequence 3
[17:31:01.929] entering bootloader
[17:31:01.930] sending kernel size (2029)
[17:31:01.951] sending kernel load address (0x0000F000)
[17:31:01.971] uploading kernel
[17:31:02.299] verifying kernel checksum response
[17:31:02.309] kernel valid
[17:31:02.518] kernel get version
[17:31:02.538] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.07
[17:31:02.538] reading kernel comm buffer size
[17:31:02.549] comm buffer size set to 256
[17:31:02.549] reading kernel flash buffer size
[17:31:02.558] flash buffer size set to 1024
[17:31:02.571] interface close
#105
Newbie
Be aware also that some later (2000-02?) MK Triton's have H8/539FA (aka MH7203FA) chipsets which require using the Evo 6.5 vehicle type rather than the H8/539F (aka MH7202F) ECUs which require the Evo 5/6 vehicle type - in my opinion, unless your car is a 1999 or earlier model with the original ECU you would be well advised to actually pull the ECU out, open it and check the chip markings as getting the type wrong can cause no end of headaches
BTW: some 2002 MKs (automatics especially) may have SH2 ECUs (which can be flashed with 1.3U cables) and 2003 onwards MKs seem to have M32R ECUs which I'd be extremely cautious of trying to flash with ECUFlash.
Last edited by WytWun; Nov 20, 2019 at 03:27 AM.