ECU 7202F cannot be read by ECUflash?

[MarkSanne]

Well, today's the day that I finally took the time to get the ECU out of Legnum to make sure it has the 7202 'flashable' ECU. And it does!





And this is where the fun should have continued, but when I connected the laptop to the ODB using a tactrix 1.3 (not sure if 1.3 or 1.3U) the ECUflash program (version 1.42.2595) can't connect to the ECU. I've tried the first 3 options ECUflash displays:
1996-2001 Mistubishi 2nd Gen/EVO5-6
1996-2001 Mitsubishi 2nd Gen/EVO6.5 MH7203F
2001-2005 Mitsubishi 3rd Gen/EVO7-8

This is what I get back:

[20:27:59.208] Using interface OpenPort 1.3 Universal TX29Cjha6dcdf6d5472695dcb84da285ba5b5a82cf3831c7
[20:28:01.989] sending init sequence 2
[20:28:01.989] got 0x11 response
[20:28:01.989] sending init sequence 3
[20:28:02.380] entering bootloader
[20:28:02.395] sending kernel size (2029)
[20:28:02.395] sending kernel load address (0x0000F000)
[20:28:02.427] uploading kernel
[20:28:02.755] verifying kernel checksum response
[20:28:02.755] kernel valid
[20:28:02.958] kernel get version
[20:28:02.989] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.06
[20:28:02.989] reading kernel comm buffer size
[20:28:02.989] comm buffer size set to 256
[20:28:02.989] reading kernel flash buffer size
[20:28:03.005] flash buffer size set to 1024
[20:28:03.020] interface close


Any ideas anyone? I'm probably doing something stupidly wrong, but I just can't see what.

[Nutter_John]

Mark did you connect the little white connector as well , I have not had issues connecting to 7202's but I have only ever user my 2.0 cable

[MarkSanne]

I did John. Maybe I'll need to try a 2.0 cable.

[Nutter_John]

Hmm can you check which version of the cable you have as that maybe the issue

[MarkSanne]

How can I tell? There is nothing written on the cable. Can I see it in some software?

[Eurospec]

Its a cable issue, the 1.3 wont do it, you need the 2.0

Cheers,

Ben.

[MarkSanne]

That is somehow a relief to know for sure. Thanks Ben!

[Davezj]

as i under stood it you can read with a 1.3 but not flash. you need a 2.0 to write something to the ECU.

it would be worth checking the 7202 flashing thread though to confirm this.

edit:-that is an odd part number on the outside of the ECU. MD360639 what car version is that from.

[Eurospec]

Yeah, but my 1.3 would never read. Only good for logging.

Cheers,

Ben.

[Davezj]

http://www.clubvr4.com/forum/showthr...ight=ecu+flash

post 87

"Mine's a 1998 pre-facelift. Just been out to check the ECU and it's the plastic-case jobby I've been able to read the ROM from my car with the Openport 1.3 cable, which also indicates it's the 7202 rather than 7201 chip.

Openport 2.0 cable ordered!

aDe"

[Eurospec]

Wierd, mine doesnt read em! Saying that arent there different 1.3's ie 1.3 u and stuff?

Cheers,

Ben.

[Nutter_John]

Yes there are about 6 different cables in the 1,3 range , I think the u one can flash evo's

[MarkSanne]

Good find Davezj. Indeed I did found out some while ago that I probably had the 'correct' ECU but I didn't know for sure untill yesterday when I actually opened up the ECU. And my friend 'Dutch Driver' has the 2.0 openport cable at his place (but it's almost a 1 hour drive to get to him...). I'm gonna have to be a bit more patient untill we meet in a few weeks.

[raph]

So Facelift vr4s are flashable with evoscan? what about ecutek? So any car after 1998?

[Nutter_John]

late 1998 and it's ecuflash not evoscan , ecuteck is not supported on vr4's

[MarkSanne]

Just for anyone who might encounter the same problem as I initially had: the problem indeed is the older 1.3x cable as suggested by NJ and eurospec. ONLY 2.0 cables are able to read the ECU with ECUflash. Friend of mine has created a new hex file. Only alteration is upping the the maximum speed cut from 184 to 280 km/h. Gonna to flash this hew hex asap and see if all works as planned and then continue doing some more mods.