EvolutionM - Mitsubishi Lancer and Lancer Evolution Community

EvolutionM - Mitsubishi Lancer and Lancer Evolution Community (https://www.evolutionm.net/forums/)
-   ECU Flash (https://www.evolutionm.net/forums/ecu-flash-179/)
-   -   Anyone recovered a Evo 5/6/DSM H8 ECU? (https://www.evolutionm.net/forums/ecu-flash/590699-anyone-recovered-evo-5-6-dsm-h8-ecu.html)

Benja Dec 28, 2011 05:27 AM

Anyone recovered a Evo 5/6/DSM H8 ECU?
 
Hey guys,

As above, something went wack during a flash today, it just halted, error'd, had to close and re-flash but the ECU is cactus.
Purchased a spare and got the guy back up and going, but wouldn't mind fixing this one.

Anyone recovered either via a bench harness or in car, or with probes a H8xxx ECU as found in Evo 5/6/TME/ 98-99 DSM etc.???

Plenty of googling hasn't turned up anything yet unless i'm not trying hard enough.

Cheers
Ben

grayw Dec 29, 2011 10:06 AM

Open ecu unlocker before ecuflash, then just make sure the XML for the rom ID you are using has the memmodel set correctly for either the 7202 (F) or 7203 (FA).
No bench flash required, the V to IX ecu can all be entered through the boot strap.

Benja Dec 29, 2011 11:03 AM

Cheers Gray, have tried that with the correct memmodule and several different Roms, all hung at the 1400000 address range.

grayw Dec 29, 2011 03:08 PM

Odd can you save a log in Ecuflash of the failed flash? I bricked lots of 7203's when testing for Colby, but all were recoverable, the 7202 has never caused issues.

XxOLIVERxX Jan 6, 2018 09:27 PM

Oops
 
So using a rom image I got from todd I have managed to get the car running on SD.

Iv had multiple issues along the way, seems to be possibly maf/injector settings. Played around using Roms I know work with the maf at least semi corrrctly to pull values from, had dramas and not able to get any kind of consistency with the ve map. Idles fine sometimes just abit rich, others it will hunt and go max lean, super rich, start idling up to 2000 rpm then drops randomly, etc

in all my testing and frustration I have now accidentally flashed a F203FA map to my evo 5 F202F ecu and bricked it. So need to unbrick if even possible.

At this point I'm happy to pay someone via PayPal who can help me sort this mess out.

XxOLIVERxX Jan 6, 2018 09:59 PM

here is a copy of the failed flash log if that helps anyone

[13:57:07.562] J2534 API Version: 04.04
[13:57:07.562] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[13:57:07.562] Device Firmware Version: 1.16.4769
[13:57:07.562] Device Serial Number: TAICL5N1
[13:57:13.406] sending init sequence 2
[13:57:13.406] got 0x11 response
[13:57:13.406] sending init sequence 3
[13:57:13.765] entering bootloader
[13:57:13.765] sending kernel size (2029)
[13:57:13.765] sending kernel load address (0x0000F000)
[13:57:13.781] uploading kernel
[13:57:14.125] verifying kernel checksum response
[13:57:14.125] kernel valid
[13:57:14.328] kernel get version
[13:57:14.328] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.07
[13:57:14.328] reading kernel comm buffer size
[13:57:14.343] comm buffer size set to 256
[13:57:14.343] reading kernel flash buffer size
[13:57:14.343] flash buffer size set to 1024
[13:57:14.359] -- flashing image to ECU memory --
[13:57:14.765] -- comparing ECU flash memory pages to image file --
[13:57:14.765] seg start len ecu CRC32 img CRC32 same?
[13:57:14.906] LB7 00010000 00003000 F1F68679 1D74E993 NO
[13:57:14.921] SB0 00013000 00000200 BD7BC39F BD7BC39F YES
[13:57:14.937] SB1 00013200 00000200 BD7BC39F BD7BC39F YES
[13:57:14.953] SB2 00013400 00000200 BD7BC39F BD7BC39F YES
[13:57:14.968] SB3 00013600 00000200 BD7BC39F BD7BC39F YES
[13:57:14.984] SB4 00013800 00000200 BD7BC39F BD7BC39F YES
[13:57:15.000] SB5 00013A00 00000200 BD7BC39F BD7BC39F YES
[13:57:15.000] SB6 00013C00 00000200 BD7BC39F BD7BC39F YES
[13:57:15.015] SB7 00013E00 00000200 BD7BC39F BD7BC39F YES
[13:57:15.218] LB6 00014000 00004000 690B37D3 4B427062 NO
[13:57:15.421] LB5 00018000 00004000 D975F16B 51F8BC8C NO
[13:57:15.609] LB4 0001C000 00004000 690B37D3 690B37D3 YES
[13:57:15.812] LB3 00020000 00004000 702FB149 702FB149 YES
[13:57:16.000] LB2 00024000 00004000 BEDF097A 2F495D12 NO
[13:57:16.203] LB1 00028000 00004000 6D3D0140 6D3D0140 YES
[13:57:16.406] LB0 0002C000 00004000 C03EE997 C03EE997 YES
[13:57:16.406] kernel flash enable
[13:57:16.406] kernel blank flash page: addr: 00024000
[13:57:16.875] erased in 2 pulse(s)
[13:57:16.875] kernel write flash buffer addr: 00024000 len: 00000100
[13:57:16.921] kernel write flash buffer addr: 00024100 len: 00000100
[13:57:16.968] kernel write flash buffer addr: 00024200 len: 00000100
[13:57:17.031] kernel write flash buffer addr: 00024300 len: 00000100
[13:57:17.078] kernel commit flash addr: 00024000 len: 00000400 crc32 3e12a994
[13:57:17.093] kernel debug:
[13:57:17.093] [B0] FF FF 00 32 F9 01 00 14 40 00 F0 00 FF FF C0 7F
71 B8 02
[13:57:17.093] kernel error: programming failure
[13:57:17.109] failed to commit flash at 00024000!
[13:57:17.109] failure in flashing block
[13:57:17.109] kernel flash disable
[13:57:17.109] interface close

Wulfen Oct 15, 2018 06:52 AM


Originally Posted by XxOLIVERxX (Post 11796480)
here is a copy of the failed flash log if that helps anyone

[13:57:07.562] J2534 API Version: 04.04
[13:57:07.562] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[13:57:07.562] Device Firmware Version: 1.16.4769
[13:57:07.562] Device Serial Number: TAICL5N1
[13:57:13.406] sending init sequence 2
[13:57:13.406] got 0x11 response
[13:57:13.406] sending init sequence 3
[13:57:13.765] entering bootloader
[13:57:13.765] sending kernel size (2029)
[13:57:13.765] sending kernel load address (0x0000F000)
[13:57:13.781] uploading kernel
[13:57:14.125] verifying kernel checksum response
[13:57:14.125] kernel valid
[13:57:14.328] kernel get version
[13:57:14.328] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.07
[13:57:14.328] reading kernel comm buffer size
[13:57:14.343] comm buffer size set to 256
[13:57:14.343] reading kernel flash buffer size
[13:57:14.343] flash buffer size set to 1024
[13:57:14.359] -- flashing image to ECU memory --
[13:57:14.765] -- comparing ECU flash memory pages to image file --
[13:57:14.765] seg start len ecu CRC32 img CRC32 same?
[13:57:14.906] LB7 00010000 00003000 F1F68679 1D74E993 NO
[13:57:14.921] SB0 00013000 00000200 BD7BC39F BD7BC39F YES
[13:57:14.937] SB1 00013200 00000200 BD7BC39F BD7BC39F YES
[13:57:14.953] SB2 00013400 00000200 BD7BC39F BD7BC39F YES
[13:57:14.968] SB3 00013600 00000200 BD7BC39F BD7BC39F YES
[13:57:14.984] SB4 00013800 00000200 BD7BC39F BD7BC39F YES
[13:57:15.000] SB5 00013A00 00000200 BD7BC39F BD7BC39F YES
[13:57:15.000] SB6 00013C00 00000200 BD7BC39F BD7BC39F YES
[13:57:15.015] SB7 00013E00 00000200 BD7BC39F BD7BC39F YES
[13:57:15.218] LB6 00014000 00004000 690B37D3 4B427062 NO
[13:57:15.421] LB5 00018000 00004000 D975F16B 51F8BC8C NO
[13:57:15.609] LB4 0001C000 00004000 690B37D3 690B37D3 YES
[13:57:15.812] LB3 00020000 00004000 702FB149 702FB149 YES
[13:57:16.000] LB2 00024000 00004000 BEDF097A 2F495D12 NO
[13:57:16.203] LB1 00028000 00004000 6D3D0140 6D3D0140 YES
[13:57:16.406] LB0 0002C000 00004000 C03EE997 C03EE997 YES
[13:57:16.406] kernel flash enable
[13:57:16.406] kernel blank flash page: addr: 00024000
[13:57:16.875] erased in 2 pulse(s)
[13:57:16.875] kernel write flash buffer addr: 00024000 len: 00000100
[13:57:16.921] kernel write flash buffer addr: 00024100 len: 00000100
[13:57:16.968] kernel write flash buffer addr: 00024200 len: 00000100
[13:57:17.031] kernel write flash buffer addr: 00024300 len: 00000100
[13:57:17.078] kernel commit flash addr: 00024000 len: 00000400 crc32 3e12a994
[13:57:17.093] kernel debug:
[13:57:17.093] [B0] FF FF 00 32 F9 01 00 14 40 00 F0 00 FF FF C0 7F
71 B8 02
[13:57:17.093] kernel error: programming failure
[13:57:17.109] failed to commit flash at 00024000!
[13:57:17.109] failure in flashing block
[13:57:17.109] kernel flash disable
[13:57:17.109] interface close

Hey, did you ever sort this out? I have the same problem with my evo 6 RS ecu.


All times are GMT -7. The time now is 03:52 PM.


© 2024 MH Sub I, LLC dba Internet Brands