openecu.org

Hi, Since I installed Ver.1.42 I cannot read, Its been a few weeks since but only had car today to try it up . The car I tried was a 2002 JDM EVO7, Im sure I have read many of them before with the older version of ECUFLASH.

it tries to intilaize a few times before it gives the error message. I got a screen shot of the problem and I hope it will be of some help. The OBD and the init socket are fine.

Some help will be greatly appreciated.

Regards,

Zakie

Can I rule out the fdti driver issues as it taking up the cable ?

I had the exact same provlem! My car is a mitsu lancer... Sending init sequence are the same as mine. I dont remember if it said interface openport 1.3 or 2.0 (because I have openport 2.0 cable).

did you try it with unlocker running ?? if yes try read with eng running .

What is unlocker?

I'm having the same issue. Can't read or flash... which sucks, since I have a valet map on my car right now. Just uninstalled and reinstalled ECUFlash, so hopefully it'll work.

It's not the cable, since I can datalog just fine.

I hate bumping up such an old topic, but has there been a resolution found for this? I am experiencing the same issues (exactly as shown by the OP). I have been trying to connect to the Ecu in my 99 Galant (Ecu is swapped to an 03 Eclipse ECU though), and I get the exact same error when trying to test write to the Ecu. When attempting to read to the Ecu I get nothing at all.

I have also tried this on my 2002 Lancer ES and got the same results. I can log, and read the Lancer Ecu on EvoScan with no issues at all. I am running a Tactrix 1.3u cable and my OS is Windows Vista with all of the current Windows updates installed.

I just double-checked this running 1.42.2595 with an old 1.3U cable I had on a USDM Evo 8, which is very similar to the Evo 7 ECU. I was able to read just fine. Most likely you are having one of two problems:

1. The ECU has a non-standard init code in it (i.e. it is locked)
2. You don't have the init connector connected, or there is some problem there like a bad connection, or a malfunctioning circuit in your 1.3. If you have a voltmeter, you should be able to see this pin go from around 5V to >12V when it tries the init sequence. You need to keep the 1.3 plugged into the OBD socket while testing this - it needs the 12V.

Colby

Code: Select all

[11:12:02.744] EcuFlash Version 1.42.2595
[11:12:02.744] OS Version Windows Vista
[11:12:02.744] Qt Version 4.5.0
[11:12:02.754] 56 memory models read.
[11:12:02.754] scanning for metadata models in C:/openecu/rommetadata
[11:12:02.937] 455 ROM metadata models scanned.
[11:12:02.937] checksum module "subarudbw" loaded.
[11:12:02.937] checksum module "mitsucan" loaded.
[11:12:02.938] flashing tool "wrx02" loaded.
[11:12:02.938] flashing tool "wrx04" loaded.
[11:12:02.938] flashing tool "sti04" loaded.
[11:12:02.938] flashing tool "sti05" loaded.
[11:12:02.938] flashing tool "mitsukernel" loaded.
[11:12:02.938] flashing tool "mitsukernelocp" loaded.
[11:12:02.938] flashing tool "mitsubootloader" loaded.
[11:12:02.938] flashing tool "shbootmode" loaded.
[11:12:02.940] flashing tool "shaudmode" loaded.
[11:12:02.940] flashing tool "subarucan" loaded.
[11:12:02.940] flashing tool "mitsucan" loaded.
[11:12:10.312] Using interface OpenPort 1.3 Universal TX29VMKC29cb74d55517ba01031e19e62f4e11b679a6d6a7
[11:12:20.926] sending init sequence 1 (0001)
[11:12:21.956] got 0x05 response
[11:12:21.956] sending init sequence 2
[11:12:21.966] got 0x1B response
[11:12:21.966] sending init sequence 3
[11:12:22.338] entering bootloader
[11:12:22.339] sending kernel size (3560)
[11:12:22.359] sending kernel load address (0xFFFF8800)
[11:12:22.380] uploading kernel
[11:12:22.952] verifying kernel checksum response
[11:12:22.953] kernel valid
[11:12:23.154] kernel get version
[11:12:23.164] kernel version is : OpenECU Mitsubishi SH7052 Kernel V1.06

Is it possible, or probable even for a completely stock Ecu to have been locked? The 2002 Lancer ES I was also testing on is completely stock with 64K miles on it.

I will have to check the pin on the cable tonight when I get home to see if it is getting the required voltage. If it is not getting correct voltage then is it simply an issue of getting the cable repaired, or upgraded to the 2.0? If the cable is bad, how would this reflect on the refund/credit I have setup through the vendor I purchased it through?

Ok, checked pin voltage now. With key "on" and cable hooked up, I get 4.68 volts. Once I do a test write and it does the init sequence voltages goes to 13.11, however I am still getting blank screen when trying to read from the Ecu.

SPD_FRK wrote:Ok, checked pin voltage now. With key "on" and cable hooked up, I get 4.68 volts. Once I do a test write and it does the init sequence voltages goes to 13.11, however I am still getting blank screen when trying to read from the Ecu.

Blank screen? Cut and paste what the log window says?

I can do that tonight for you when I am home. It basically pulls up a window that says "Read" which is grayed out and cannot be clicked, and second button is "Cancel." The window that comes up is blank like it should have something showing in it, I will get a screenshot tonight for you though.

SPD_FRK wrote:I can do that tonight for you when I am home. It basically pulls up a window that says "Read" which is grayed out and cannot be clicked, and second button is "Cancel." The window that comes up is blank like it should have something showing in it, I will get a screenshot tonight for you though.

your rommetadata directory is set to something wrong in the options. you might have changed it by accident.

you can set it to the relative path

Code: Select all

rommetadata

or the correct absolute path, e.g.

Code: Select all

c:\Program Files\OpenECU\EcuFlash\rommetadata

I changed the rommedata directory to path you specified;


Test write of a ROM file was successful;


This is the screen as it looks when trying to read the Ecu;