Posted: Sat Apr 15, 2006 4:31 pmColby, this was a different ECU, the original for the car. Car has an immobilizer so I'm hesitant to drop in the spare ECU in case the BIU locks me out. I have an idea, will run it by you in email.
openecu.org
Forums for ECU reverse engineering and modification
http://forums.openecu.org/
Get newest versions of EcuFlash from the tactrix.com website
Page 3 of 7
Posted: Sat Apr 15, 2006 4:31 pmPosted: Fri Apr 21, 2006 7:13 amGonna try this on my buddies 04 USDM STi tonight... do I need to connect the green connectors and jump the white one to read and flash on the STi or is it just the green ones ?
Posted: Fri Apr 21, 2006 9:28 amjust the green...
Posted: Fri Apr 21, 2006 10:41 amcboles wrote:just the green...
Even to flash? wow cool thanks
Posted: Fri Apr 21, 2006 4:07 pmThere's no white connector in the STIs.
Posted: Mon Apr 24, 2006 7:58 amYeah, found that out... Saturday night, we successfully copied an 04 USDM STi ECU thanks for all the help / expertise guys 
Posted: Mon Apr 24, 2006 8:01 amHas anyone successfully flashed an STi ECU yet??? Cause we are going to try this soon *insert nervous emoticon here* 
Posted: Tue Apr 25, 2006 4:34 amOk, tried flashing a "special map" and got some errors:
[00:29:09.265] kernel blank flash page: addr: 00020000
[00:29:10.286] kernel error: programming failure
[00:29:10.296] WARNING: failed to erase page at 00020000!
tried again and same problem so we then tried to flash it back to stock... no problems...
I've sent Colby a copy of the ROMs and error log in hopes that he can help me figure this out
[00:29:09.265] kernel blank flash page: addr: 00020000
[00:29:10.286] kernel error: programming failure
[00:29:10.296] WARNING: failed to erase page at 00020000!
tried again and same problem so we then tried to flash it back to stock... no problems...
I've sent Colby a copy of the ROMs and error log in hopes that he can help me figure this out
Posted: Tue Apr 25, 2006 11:54 amI'm looking into it now. To be safe, I wouldn't suggest anyone reflash an '04 again until I'm sure things are OK.
Colby
Colby
Posted: Thu Apr 27, 2006 12:56 amThere definitely was a problem in that version with erasing / writing a couple of blocks on '04 DBW ECUs. It has been fixed in V1.23 on the site now. Everyone should discard any version from 1.20 to 1.22 and switch to 1.23
Colby
Colby
Posted: Thu Apr 27, 2006 4:06 amcboles wrote:There definitely was a problem in that version with erasing / writing a couple of blocks on '04 DBW ECUs. It has been fixed in V1.23 on the site now. Everyone should discard any version from 1.20 to 1.22 and switch to 1.23
Colby
Colby, you are the MAN!!!
I'll be trying to flash my buddies 04 STi shortly. I will post the results immediately afterwards!
Posted: Thu Apr 27, 2006 5:45 amUmm, just wanted to let you know that some of the maps in ecuFlash for the GD10C map are not the same as they are in ecuEdit. Not even close. Also, I noticed you have some xml files for like a 300F map, but none of the maps are displayed in it. Haven't had any time to dig through the xmls, but they look really small for what they should be. Anyway, since I don't use ecuFlash to do map editing I won't worry about it at this time, but I wanted to see why there are big differences in the layouts of what ecuFlash and ecuEdit can read out of the GD10C map. The xml files I use in ecuEdit are made with xmlwrite. For example, in ecuEdit for EGT limit I get a 2x2 grid, but in ecuFlash it's an entire map range similar to fuel or timing. What's up with that? Which one is right and which one is wrong. I ask this because if there's an issue with the way the xmls are in ecuEdit I want to know.
Posted: Thu Apr 27, 2006 9:18 amSUCCESS!!!!
Great job Colby! Worked like a charm
Great job Colby! Worked like a charm
Posted: Sat Apr 29, 2006 8:30 pmI believe I found a bug, if you open two roms and close them both, it throws an error, could just be my system ?
Posted: Sun Apr 30, 2006 8:27 amI just duplicated that error. It only happens if you open 2 or more ROMs and close them in the reverse order that you opened them. For example, if you open ROM1 and ROM2 and then close ROM2 and then close ROM1 it will not error, but if you open ROM1 and ROM2 and then close ROM1 and then close ROM2 it will error out.
To add to this, it seems that if you open more then 2 ROMs it becomes evident that if you close them in any order other then the order you opened them in you will get an error. You can close 1 ROM file, but if it's out of order then very next one you try and close will generate the error message.
To add to this, it seems that if you open more then 2 ROMs it becomes evident that if you close them in any order other then the order you opened them in you will get an error. You can close 1 ROM file, but if it's out of order then very next one you try and close will generate the error message.