05 STi cant read rom
Posted: Thu Mar 26, 2009 8:35 pm
Forums for ECU reverse engineering and modification
http://forums.openecu.org/
radsdau wrote:ECUFlash is finding the OpenPort2, which indicates to me that the drivers are installed ok. On my PC (XP), OpenPort2 comes up in the ports section of device manager.
The fact that ECUFlash is getting as far as it is indicates the hardware is working ok. It looks more like the ECU is locked and is not granting security access to the key provided by ECUFlash/OpenPort2.
Please confirm the ECU is factory and has not been Ecutek or Cobb tuned.
dookie wrote:I believe that device manager has to show 2 instances of the OP2. One in Ports and the other in USB Controllers. I can not get the one in USB Controllers to show(install?).
radsdau wrote:dookie wrote:I believe that device manager has to show 2 instances of the OP2. One in Ports and the other in USB Controllers. I can not get the one in USB Controllers to show(install?).
Mine doesn't show up there (I just checked). I'm guessing it uses a totally different drive set from the FTDI-based OpenPort1.x.
If ECUFlash finds the device and displays 'OpenPort2' at the bottom right of the screen, then the USB drivers must be installed; they're needed to read that text out, and also to read the capabilities of the device.
Your OpenPort2 firmware is the same as mine, so it's not that.
My guess is that you're using the wrong hookup method; I see you've chosen 05-07 DBW models, but I think for your car you may want the 04 DBW one. Give that a try anyway. Otherwise, take the lid off your ECU and read what the MCU is; it will be either 7055 or 7058. 7055 = 04DBW, 7058 = 05-07DBW.
Double check you're in test mode too; fans should cycle with ignition on.
radsdau wrote:Glad you sorted that one out. That sounds like the sort of thing I'd suspect, but I wouldn't have guessed a bad connection. Well found.