Been reading/flashing my evo for a couple years. New laptop with Vista 64 bit seems to refuse to do anything. Using the same cable and software that was working fine before under XP 32 bit.

I've given full permissions to the ECUflash folder, run in compatability mode... done everything I could think of. I know the cable and drivers are fine, as I'm able to log with EvoScan just fine. Just can't read the rom ... which is important because I can't find the rom that I flashed on the car last time, and don't have that laptop any more.

Here's a dump of what it says when it tries to connect:

[13:41:41.172] Using interface OpenPort 1.3 Mitsubishi TX34Sgip1f93f6c90720fe98b932f8e3ddc4b036333e0ef8
[13:41:44.750] sending init sequence 1 (0001)
[13:41:45.795] got 0x05 response
[13:41:45.795] sending init sequence 2
[13:41:45.795] got 0x1B response
[13:41:45.795] sending init sequence 3
[13:41:46.185] entering bootloader
[13:41:46.201] sending kernel size (3560)
[13:41:46.217] sending kernel load address (0xFFFF8800)
[13:41:46.217] uploading kernel
[13:41:46.794] verifying kernel checksum response
[13:41:46.794] kernel valid
[13:41:46.997] kernel get version
[13:41:47.012] kernel version is : OpenECU Mitsubishi SH7052 Kernel V1.06
[13:41:47.012] reading kernel comm buffer size
[13:41:47.028] comm buffer size set to 512
[13:41:47.028] reading kernel flash buffer size
[13:41:47.043] flash buffer size set to 4096
[13:41:47.043] -- dumping ECU memory --
[13:41:47.059] kernel read area: addr: 00000000 len: 0200
[13:41:47.153] kernel read area: addr: 00000200 len: 0200
[13:41:47.246] kernel read area: addr: 00000400 len: 0200
[13:41:47.324] kernel read area: addr: 00000600 len: 0200
[13:41:47.418] kernel read area: addr: 00000800 len: 0200
[13:41:47.511] kernel read area: addr: 00000A00 len: 0200
[13:41:47.605] kernel read area: addr: 00000C00 len: 0200
[13:41:47.699] kernel read area: addr: 00000E00 len: 0200
[13:41:47.808] kernel read area: addr: 00001000 len: 0200
[13:41:47.901] kernel read area: addr: 00001200 len: 0200
[13:41:47.995] kernel read area: addr: 00001400 len: 0200
[13:41:48.073] kernel read area: addr: 00001600 len: 0200
[13:41:48.167] kernel read area: addr: 00001800 len: 0200
[13:41:48.260] kernel read area: addr: 00001A00 len: 0200
[13:41:48.354] kernel read area: addr: 00001C00 len: 0200
[13:41:48.447] kernel read area: addr: 00001E00 len: 0200
[13:41:48.557] kernel read area: addr: 00002000 len: 0200
[13:41:48.650] kernel read area: addr: 00002200 len: 0200
[13:41:48.744] kernel read area: addr: 00002400 len: 0200
[13:41:48.822] kernel read area: addr: 00002600 len: 0200
[13:41:48.915] kernel read area: addr: 00002800 len: 0200
[13:41:49.009] kernel read area: addr: 00002A00 len: 0200
[13:41:49.103] kernel read area: addr: 00002C00 len: 0200
[13:41:49.196] kernel read area: addr: 00002E00 len: 0200
[13:41:51.224] rkrv: kernel response incomplete
[13:41:51.224] invalid / no kernel response to read
[13:41:51.224] kernel read area: addr: 00002E00 len: 0200
[13:41:51.224] readback mismatch
[13:41:51.224] kernel read area: addr: 00002E00 len: 0200
[13:41:51.224] readback mismatch
[13:41:51.224] ECU memory read failure.
[13:41:51.224] can't read image.
[13:41:51.224] interface close

Anybody?

 

Thats pretty interesting using windows 7 64bit edition here with no problems. I looks like you got it to start reading though and like the cable has a weak connection breaking up the signal and interrupting the process?

Perhaps its a cable issue or a connector issue?

 

Hmm. I'll try holding it in there firmly and see if that makes a difference. Now I'm wondering if it's a voltage issue. The car starts and runs, but I haven't metered it, and it sat for about 3 months without running (but battery disconnected).

I'm setting up a 32 bit virtual box to try as well. I'll report back with what I find. Thanks for the help!

 

Just speculating here because most computer problems like this just wont work not begin then fail

 

Vista 64 bit is a bit quirky, that's for sure. I've found that 95% of the issues deal with permissions and ownership.

 

Your sig says you have an VIII? But is the car you are trying this on a IX? The IXs are more finicky with low voltage.

Anyone nearby with ECUFlash on their machine so you can test the cable on another machine? EvoScan and ECUFlash use different connectors to the ECU, so its possible for one part of the cable to work, while the other is busted.

 

Yep, I have an VIII. Got it to work. The cable is just a bit finicky. Once I held it in place, it worked fine. I might have bent the pins on the cable a bit making a crossover harness for it for another car.

I also found another problem I thought was due to Vista64, but was just user error from trying to make it do something it doesn't want to do.

Thanks!!

 

i run 64-bit vista w/o a hiccup....only problem I had was with evoscan when I first got the new laptop and that was before it was supported.

glad you figured it out.....

 

Glad it worked out. I actually used to have 2 cables just in case this happened. The first one is now dead....might be time for me to get a backup again .