ECUflash First Flashed DSM ECU! (98/99 Flashing FAQ)

[dsmgsx98]

I reset the ecu every time i reflash!!!

 

[streetdsmpwr]

Ok, just makin sure. Other than that, I'm out of ideas. If you could find someone to loan you their ECU, you could see if it's an ECU problem and not a mechanical problem.

 

[dsmgsx98]

well i have a 95 ecu but i dont think that would work

 

[Absit]

You'd have to do the standard CAS rewire or plug/injector swap, but it'd work.

 

[Heat]

sup bros,

Having a nightmare of a time getting ecuflash and evoscan working. Got the cable in today, been messing with it for the last 4 hours or so trying to track down answers.

99gsx
stock ecu
windows 7 64

Evoscan - Should I be using 2.5 or 2.7? 2.7 freezes when I hit datalog. Is 2.5 for all 2gs or just 95/96? 2.5 says some stuff about not working on a 64 bit OS, or not having the right drivers, or not having the right .dll.

Ecuflash v1.42 - Set it up. Tried reading the stock rom. Shows connected on COM 3 on my laptop. Turn key to ON. Hit the blue download rom button. Asks for car type, I select 96-01 or 99-01 mitusbishi, tried both. I get:

sending init sequence 2
interface close

that's it.

Just getting into this so sorry if I'm doing something obvious wrong. Been doing a ton of reading and can't even get my feet wet.

 

[dsmgsx98]

You have to have the flash connector plugged into read the rom or reflash if not plug it in and try again. You should be using 2.7 and make sure you have the 2.0 checked and have the mut III checked. My will freeze if I check the Dsm box

 

[Heat]

thanks for the reply.

yes I have both the openport 2.0 and the flash connector plugged in for ecuflash

I will try evoscan again tomorrow, I was using the DSM box so hopefully that will solve that end of it.

 

[colbyc]

Have you flashed the ecu yet? Or you working on your first flash, I just started having this same problem last night and I'm no stranger to ecuflash. If I figure anything out I'll post back.

 

[dsmgsx98]

thanks for the reply.

yes I have both the openport 2.0 and the flash connector plugged in for ecuflash

I will try evoscan again tomorrow, I was using the DSM box so hopefully that will solve that end of it.

Have you made any progress??? Don't try and read the image, try to flash ceddy mods To the ecu and see if that works

 

[streetdsmpwr]

I don't have the newest version of ceddymods because I have BigMaps and don't want to update. I have the one before it which is 1.9B. I saw that Ceddy updated the fuel trim switch points, and I was wondering if someone with the latest version could tell me the Hz values of their low->mid, mid->low, mid->high, and high->mid control points. Thanks.

 

[Heat]

Progress:

Tried the car this morning. Evoscan wouldn't connect, said 1.xx volts on battery even with the car running. Said F it and went to run some errands.

Got back just now, tried it again, worked fine. Went out and did a few pulls.

Got back, tried ecuflash, worked fine. Downloaded the stock rom.

To upload ceddy mods I just take the .hex file and flash it with that right? I have 680s in the car so will it run alright just uploading ceddy mods or should I at least edit the injector size to 680?

 

[colbyc]

Progress:

Tried the car this morning. Evoscan wouldn't connect, said 1.xx volts on battery even with the car running. Said F it and went to run some errands.

Got back just now, tried it again, worked fine. Went out and did a few pulls.

Got back, tried ecuflash, worked fine. Downloaded the stock rom.

To upload ceddy mods I just take the .hex file and flash it with that right? I have 680s in the car so will it run alright just uploading ceddy mods or should I at least edit the injector size to 680?

Yes change the size and latency/deadtime also. I believe mine was due to battery voltage also.

 

[dsmgsx98]

I don't have the newest version of ceddymods because I have BigMaps and don't want to update. I have the one before it which is 1.9B. I saw that Ceddy updated the fuel trim switch points, and I was wondering if someone with the latest version could tell me the Hz values of their low->mid, mid->low, mid->high, and high->mid control points. Thanks.

It goes like this 88 75 188 175 top to bottom

 

[dsmgsx98]

Progress:

Tried the car this morning. Evoscan wouldn't connect, said 1.xx volts on battery even with the car running. Said F it and went to run some errands.

Got back just now, tried it again, worked fine. Went out and did a few pulls.

Got back, tried ecuflash, worked fine. Downloaded the stock rom.

To upload ceddy mods I just take the .hex file and flash it with that right? I have 680s in the car so will it run alright just uploading ceddy mods or should I at least edit the injector size to 680?

Get your injector scaled then flash. But yes open the hex file and ceddy mods should come up on the left side

No for the low volts crap run a wire from your fuse box to the red wire with black strip on your obd 2 port under the dash and it will cure the low voltage reading

 

[streetdsmpwr]

It goes like this 88 75 188 175 top to bottom

Thanks buddy!

 

[AlphaVision]

Auto-merged with previous post to prevent "bumping" within a 24 hour period Tips on avoiding the auto-merge feature - http:/y car (1G ECU) and a friend's car as well. I do that because I am a computer guy and understand thing or two. And 1G and 2G ECU's have nothing in common

For my friend's car we have already set up the speed density with the GM 3bar map and IAT. I read yesterday that I need the MAF for the initial VE tune, but since we already skipped that part what are my options? I see that the VE table is flat (all cells have value of 100) so I think that I will have to log the WB and pressure and figure it out from there.

What can you advice me?

Is it possible that I have a bricked ECU. It's a 99 GSX ecu and the car starts and idles fine with it. I can datalog it with EvoScan using the openport 1.3 and openport 2.0 cables.

the flash pin has a good connection and I tested it to make sure it is all right

Here is the log.

[22:12:28.511] EcuFlash Version 1.42.2595
[22:12:28.511] OS Version Windows Vista
[22:12:28.511] Qt Version 4.5.0
[22:12:28.524] 56 memory models read.
[22:12:28.525] scanning for metadata models in C:/Stuff/Eclipse/EcuFlash/rommetadata
[22:12:28.819] 348 ROM metadata models scanned.
[22:12:28.819] checksum module "subarudbw" loaded.
[22:12:28.819] checksum module "mitsucan" loaded.
[22:12:28.819] flashing tool "wrx02" loaded.
[22:12:28.819] flashing tool "wrx04" loaded.
[22:12:28.819] flashing tool "sti04" loaded.
[22:12:28.819] flashing tool "sti05" loaded.
[22:12:28.819] flashing tool "mitsukernel" loaded.
[22:12:28.819] flashing tool "mitsukernelocp" loaded.
[22:12:28.819] flashing tool "mitsubootloader" loaded.
[22:12:28.819] flashing tool "shbootmode" loaded.
[22:12:28.834] flashing tool "shaudmode" loaded.
[22:12:28.834] flashing tool "subarucan" loaded.
[22:12:28.834] flashing tool "mitsucan" loaded.
[22:12:37.941] J2534 API Version: 04.04
[22:12:37.941] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[22:12:37.941] Device Firmware Version: 1.11.3157
[22:12:39.744] sending init sequence 2
[22:12:41.746] interface close

 

[Ceddy]

Auto-merged with previous post to prevent "bumping" within a 24 hour period Tips on avoiding the auto-merge feature - http:/y car (1G ECU) and a friend's car as well. I do that because I am a computer guy and understand thing or two. And 1G and 2G ECU's have nothing in common

For my friend's car we have already set up the speed density with the GM 3bar map and IAT. I read yesterday that I need the MAF for the initial VE tune, but since we already skipped that part what are my options? I see that the VE table is flat (all cells have value of 100) so I think that I will have to log the WB and pressure and figure it out from there.

What can you advice me?

Is it possible that I have a bricked ECU. It's a 99 GSX ecu and the car starts and idles fine with it. I can datalog it with EvoScan using the openport 1.3 and openport 2.0 cables.

the flash pin has a good connection and I tested it to make sure it is all right

Here is the log.

[22:12:28.511] EcuFlash Version 1.42.2595
[22:12:28.511] OS Version Windows Vista
[22:12:28.511] Qt Version 4.5.0
[22:12:28.524] 56 memory models read.
[22:12:28.525] scanning for metadata models in C:/Stuff/Eclipse/EcuFlash/rommetadata
[22:12:28.819] 348 ROM metadata models scanned.
[22:12:28.819] checksum module "subarudbw" loaded.
[22:12:28.819] checksum module "mitsucan" loaded.
[22:12:28.819] flashing tool "wrx02" loaded.
[22:12:28.819] flashing tool "wrx04" loaded.
[22:12:28.819] flashing tool "sti04" loaded.
[22:12:28.819] flashing tool "sti05" loaded.
[22:12:28.819] flashing tool "mitsukernel" loaded.
[22:12:28.819] flashing tool "mitsukernelocp" loaded.
[22:12:28.819] flashing tool "mitsubootloader" loaded.
[22:12:28.819] flashing tool "shbootmode" loaded.
[22:12:28.834] flashing tool "shaudmode" loaded.
[22:12:28.834] flashing tool "subarucan" loaded.
[22:12:28.834] flashing tool "mitsucan" loaded.
[22:12:37.941] J2534 API Version: 04.04
[22:12:37.941] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[22:12:37.941] Device Firmware Version: 1.11.3157
[22:12:39.744] sending init sequence 2
[22:12:41.746] interface close

Double check the Flash Pin is connected correctly. Also make sure the battery has enough voltage if it has been sitting a while. If the car runs and you can log, I doubt the ecu is bricked.

You are correct, you will have to log WideBand to figure out VE%.
Where WideBand / AFR_Map = VE%.
I have a few SD base maps that may help, but its much better to build your own.

 

[CurtC]

I think I'm starting to understand everything now but I did have some questions about the setup bits, mainly the ones located at the bottom.

I'm not running speed density just trying to get everything working with 680cc injectors so I have the ADC 10-Bit MAP bit set to 0, I have the CEL on Knock set to 1. I think I'm good with them but I'm wondering about the last four (Speed Density Calculations, Base Timing Terminal, 1Byte Load, and AirFlow Calculations). Should I have these enabled or do these deal with speed density?

Also to disable fuel cut, do I set the Boost Limit Disable to 1 ?

I hate fuel cut and never want to experience it again

 

[AlphaVision]

Double check the Flash Pin is connected correctly. Also make sure the battery has enough voltage if it has been sitting a while. If the car runs and you can log, I doubt the ecu is bricked.

Thank you, Ceddy. I double checked and it has a connection. Here is summary of what I have tried:

- Uninstalled and installed EcuFlash again.
- tried on 2 different laptops using Win7 (32 bit) and XP with SP3
- Tried with 1.3 and 2.0 cables
- Battery voltage is 12.8-13.1 Volt
- Tried both with ACC on and key off the car


The car has immobilizer. Can it interfere somehow?

 

[Ceddy]

I think I'm starting to understand everything now but I did have some questions about the setup bits, mainly the ones located at the bottom.

I'm not running speed density just trying to get everything working with 680cc injectors so I have the ADC 10-Bit MAP bit set to 0, I have the CEL on Knock set to 1. I think I'm good with them but I'm wondering about the last four (Speed Density Calculations, Base Timing Terminal, 1Byte Load, and AirFlow Calculations). Should I have these enabled or do these deal with speed density?

Also to disable fuel cut, do I set the Boost Limit Disable to 1 ?

I hate fuel cut and never want to experience it again

Everything has been setup to be ready by default. Fuel Cut, AirFlow, etc. are disabled by default.

You just need to edit Injector Scaling and Injector Latency and you are good to go.

Thank you, Ceddy. I double checked and it has a connection. Here is summary of what I have tried:

- Uninstalled and installed EcuFlash again.
- tried on 2 different laptops using Win7 (32 bit) and XP with SP3
- Tried with 1.3 and 2.0 cables
- Battery voltage is 12.8-13.1 Volt
- Tried both with ACC on and key off the car


The car has immobilizer. Can it interfere somehow?

The H8 ecus can only be Flashed with the OP 2.0 cable.

The key needs to be in the running position, the one right before Start/Crank.


None of the US DSMs had the immobilizer, so you may have a different hardware setup or maybe even ecu. None of the other Euro DSMs I know of had the immobilizer.

 

[CurtC]

Everything has been setup to be ready by default. Fuel Cut, AirFlow, etc. are disabled by default.

You just need to edit Injector Scaling and Injector Latency and you are good to go.

Thanks again!

 

[AlphaVision]

The H8 ecus can only be Flashed with the OP 2.0 cable.

The key needs to be in the running position, the one right before Start/Crank.


None of the US DSMs had the immobilizer, so you may have a different hardware setup or maybe even ecu. None of the other Euro DSMs I know of had the immobilizer.

I got 2 flashable ECUs I got from USA for 2 friends' project cars and we have tried both of them. Both log and both start the engine, so I rule the bad ECU scenario out.

I guess it has something to do with the hardware setup of the car. We will try to run wires from the ECU to the OBD plug directly, so any interfering hardware can be overriden. Which pins from the ECU do I need and to what OBD Diagnosis plug they should go?

I was also wondering is there some sort of grounding or something like that, which is required for flashing that the US DSMs have in their factory electrical installation and ours may be don't?

 

[magik95]

Serial interface KKL VAG-com VW/AUDI OBD-2 Cable vagcom - eBay (item 260688152325 end time Mar-05-11 08:19:07 PST)

Will this cable work? My laptop has a broken usb port so i found this cable that plugs in the dbp port/serial port. Will the program run through this. If so im ordering the software and cable tonight. I just want to log with it first then I get the other stuff to flash my ecu.

 

[kthackst]

Hey everyone,

I downloaded ceddymod v1.9 and tryed flashing my ECU for the first time. When I went to flash the 20550011.hex I got this message

An error occurred while reflashing. See the log for details.

You were in the process of reflashing your ECU and
some memory areas have already been erased / written -
Start the reflashing process again, and the software
should be able to resume where it left off. If you are
still having trouble, save the log file, and send it to
Main Page - OpenECU or [email protected] and see if
someone can help you.

With this log

[12:04:28.218] EcuFlash Version 1.42.2595
[12:04:28.218] OS Version Windows XP
[12:04:28.218] Qt Version 4.5.0
[12:04:28.265] 56 memory models read.
[12:04:28.296] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[12:04:39.187] 344 ROM metadata models scanned.
[12:04:39.187] checksum module "subarudbw" loaded.
[12:04:39.187] checksum module "mitsucan" loaded.
[12:04:39.187] flashing tool "wrx02" loaded.
[12:04:39.187] flashing tool "wrx04" loaded.
[12:04:39.187] flashing tool "sti04" loaded.
[12:04:39.187] flashing tool "sti05" loaded.
[12:04:39.187] flashing tool "mitsukernel" loaded.
[12:04:39.187] flashing tool "mitsukernelocp" loaded.
[12:04:39.187] flashing tool "mitsubootloader" loaded.
[12:04:39.187] flashing tool "shbootmode" loaded.
[12:04:39.453] flashing tool "shaudmode" loaded.
[12:04:39.453] flashing tool "subarucan" loaded.
[12:04:39.453] flashing tool "mitsucan" loaded.
[12:04:51.390] 131072 byte image read.
[12:05:09.578] J2534 API Version: 04.04
[12:05:09.578] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[12:05:09.578] Device Firmware Version: 1.10.3020
[12:05:25.343] sending init sequence 2
[12:05:25.343] got 0x13 response instead of 0x11
[12:05:25.343] sending init sequence 3
[12:05:25.734] entering bootloader
[12:05:25.734] sending kernel size (2029)
[12:05:25.750] sending kernel load address (0x0000F000)
[12:05:25.796] uploading kernel
[12:05:26.125] verifying kernel checksum response
[12:05:26.125] kernel valid
[12:05:26.328] kernel get version
[12:05:26.328] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.06
[12:05:26.328] reading kernel comm buffer size
[12:05:26.343] comm buffer size set to 256
[12:05:26.343] reading kernel flash buffer size
[12:05:26.359] flash buffer size set to 1024
[12:05:26.375] -- flashing image to ECU memory --
[12:05:26.781] -- comparing ECU flash memory pages to image file --
[12:05:26.781] seg start len ecu CRC32 img CRC32 same?
[12:05:26.921] LB7 00010000 00003000 176F7357 9151178F NO
[12:05:26.953] SB0 00013000 00000200 B14BB8CF B14BB8CF YES
[12:05:26.984] SB1 00013200 00000200 4517F274 A5A451AE NO
[12:05:27.015] SB2 00013400 00000200 4C08CF43 112D1623 NO
[12:05:27.046] SB3 00013600 00000200 10508489 10508489 YES
[12:05:27.078] SB4 00013800 00000200 D8A09BDE D8A09BDE YES
[12:05:27.109] SB5 00013A00 00000200 869C5CA9 869C5CA9 YES
[12:05:27.140] SB6 00013C00 00000200 E08ADFF1 E08ADFF1 YES
[12:05:27.156] SB7 00013E00 00000200 CD0D0875 CD0D0875 YES
[12:05:27.359] LB6 00014000 00004000 44F77E3F 44F77E3F YES
[12:05:27.546] LB5 00018000 00004000 85E107DD FDABE6CC NO
[12:05:27.750] LB4 0001C000 00004000 982AC507 982AC507 YES
[12:05:27.953] LB3 00020000 00004000 341F4448 62870583 NO
[12:05:28.140] LB2 00024000 00004000 1FED30F4 0DA8A8A5 NO
[12:05:28.343] LB1 00028000 00004000 BB9DEFB8 93F4BDDC NO
[12:05:28.546] LB0 0002C000 00004000 9A7D97C7 0FD52EEA NO
[12:05:28.546] kernel flash enable
[12:05:28.562] kernel blank flash page: addr: 0002C000
[12:05:43.578] WARNING: failed to erase page at 0002C000!
[12:05:43.578] kernel flash disable
[12:05:45.593] interface close

Any info on this? Am I doing something wrong? Thanks for the help

Yeah I am having the same issues with one of my ecu's after a bad flash. Is there anyway to restore these ecus?

 

[CurtC]

My car runs, but stumbles. Im not sure if its a bricked ecu or just from not having my injectors scaled correctly. Also EvoScan pulls up and logs everything which leads me to believe the ECU isnt bricked, I could be wrong though

If your car runs and you can log with EvoScan I don't think you bricked your ECU.

Did you adjust your injector latency as well? Is your wideband giving lean readings?

I see you have PTE 680 injectors in your profile, PTE injector flow rates are usually given with a fuel pressure of 49.5 psi not the regular 43.5. You may want to check this and adjust your fuel pressure regulator accordingly.

I saw your last post about the flash, sorry can't help you with that Did you turn anything on like launch control? It's an easy way to tell if the flash worked.