error sending kernel size

[jamk]

Hello all!

I can't read flash at MMC Galant VR-4 JDM '97 (ECU part number MD340289, OP2.0 (also try OP1.3)). EcuFlash ver. 1.42, try 1.43 and result is same on a
two cars
Here is log for 1.42
fist car:
[13:53:37.546] sending init sequence 2
[13:53:37.546] got 0x10 response instead of 0x11
[13:53:37.546] sending init sequence 3
[13:53:37.921] entering bootloader
[13:53:37.921] sending kernel size (2027)
[13:53:37.921] error sending kernel size
[13:53:37.921] interface close

second car:
[19:31:43.437] Device Firmware Version: 1.10.3020
[19:31:45.390] sending init sequence 2
[19:31:45.390] got 0x09 response instead of 0x11
[19:31:45.390] sending init sequence 3
[19:31:45.765] entering bootloader
[19:31:45.765] sending kernel size (2029)
[19:31:45.781] error sending kernel size
[19:31:45.781] interface close

try 1.43 for first car:

[15:01:56.140] J2534 API Version: 04.04
[15:01:56.140] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[15:01:56.140] Device Firmware Version: 1.11.3137
[15:01:56.140] Device Serial Number: TA8ysPe9
[15:01:58.765] sending init sequence 2
[15:01:58.765] got 0x09 response instead of 0x11
[15:01:58.765] sending init sequence 3
[15:01:59.125] entering bootloader
[15:01:59.125] sending kernel size (2029)
[15:01:59.125] error sending kernel size
[15:01:59.140] interface close
[15:02:09.515] J2534 API Version: 04.04
[15:02:09.515] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[15:02:09.515] Device Firmware Version: 1.11.3137
[15:02:09.515] Device Serial Number: TA8ysPe9
[15:02:11.875] sending init sequence 2
[15:02:11.875] got 0x09 response instead of 0x11
[15:02:11.875] sending init sequence 3
[15:02:12.218] entering bootloader
[15:02:12.265] sending kernel size (1951)
[15:02:12.265] error sending kernel size
[15:02:12.281] interface close

On a my MMC Galant VR-4 '99 (ECU MD340288) read flash and write is no problem.
Any ideas why ?

Thanks

[todd-w]

prob ecu is not flashable similar situation with 96/97 evo4 . thats why people swap to 98 evo5 ecu which are flashable

[jamk]

prob ecu is not flashable similar situation with 96/97 evo4 . thats why people swap to 98 evo5 ecu which are flashable

Thanks for answer Todd!
I'm absolutely sure, the ecu is replaced to plastic case ecu. And second car has the same plastic case ecu MD340288(MD340289 for AT) which are reflashable...

[todd-w]

check the init connector wire at ecu to connector cant remember which pin it goes to maybe ecu pin 79 or if its a H8/539FA you need to select that from the read drop down also try the unlocker

[jamk]

Thanks Todd!

check the init connector wire at ecu to connector cant remember which pin it goes to maybe ecu pin 79 or if its a H8/539FA you need to select that from the read drop down also try the unlocker

Unlocker will work exactly on version 1.28 ?? Or maybe on 1.42 1.43 ? We try on 1.42 and 1.43, no result...
And also do checking wire to ECU, all fine..
But one more thing is cause attention: all 2 cars are swaped from AT to MT(with some tricks with wires). My vr-4 is already has MT from factory and read/write perfectly...

[radsdau]

From memory, Unlocker works with 1.42 but is not relevant to the earlier ECUs (EVO7 onwards).
Haven't tried it with 1.43.

[todd-w]

can you log with evoscan ? check all the wiring in obd socket is the same as in the car that you can flash or try the other ecu in it