Here's something so we can start sharing ECU flash images

OpenECU software executables and source code

Moderator: Freon

Postby cmj » Thu Jun 23, 2005 9:09 pm

cboles wrote: Also, the app will only work with OpenPort hardware, unless you are using a FTDI232BM based USB to serial adapter along with an appropriate ISO9141 interfaace. The reason for this is that there are parts of the 04-05 firmware and my kernel use obscure baud rates which normal UARTs won't hit.


So i should not waste my time trying this with the Delta Dash obd2 connector and IOGear serial to usb adapter?
cmj
 
Posts: 5
Joined: Mon Apr 25, 2005 10:43 am

Postby cboles » Thu Jun 23, 2005 9:32 pm

cmj wrote:
cboles wrote: Also, the app will only work with OpenPort hardware, unless you are using a FTDI232BM based USB to serial adapter along with an appropriate ISO9141 interfaace. The reason for this is that there are parts of the 04-05 firmware and my kernel use obscure baud rates which normal UARTs won't hit.


So i should not waste my time trying this with the Delta Dash obd2 connector and IOGear serial to usb adapter?


that depends. what MY do you have? for the 04/05 you need to hit something close to 15.6k baud for the init sequence. right now, my kernel is running at 39,471 baud for faster download speed (i couldn't hit 38.4k...). if the ioport can do these, you might be in luck, assuming the DD hardware can handle the speed. eventually i'll make my kernel have adjustable baud rates, but this still won't help you for the 15.6k baud issue.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby calvinc » Thu Jun 23, 2005 11:02 pm

just to confirm - my test was using the tactrix wrx hardware and with the green connectors connected.

colby (or anybody)...know where to get the flash block? then i can do some more testing on this side.

calvin.
calvinc
 
Posts: 163
Joined: Sun Apr 24, 2005 10:18 am
Location: south africa

Postby cboles » Fri Jun 24, 2005 9:33 am

Is your STi drive-by-wire? If so, it probably uses a newer ECU which has a different init sequence and kernel requirements. The utility I released doesn't cover this yet, but I will be working on that soon. I just need to get access to an STi around Seattle for a little bit to test.

calvinc wrote:hi colby,

i tried the app and didnt get any success with the dumping. my car is a MY05 AUS/SA STI, ecu type is AJ870-8840.

initially i tried the sti2004 parameter but as neverlies said, its not coded for it. i then tried the wrx2004 parameter and got some different responses but still no dump. then i tried the wrx2002 parameter and it seemed as if the app just queried but couldnt go any further than the 4D command.

i've attached both the console requests/responses and portmon logs for both the wrx2002 and wrx2004 parameters.

let me know if i'm the village idiot that isnt using it right or my ecu type is different. if its different and you want some more detail i'll do whatever i can to help.

regards,
calvin.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby Nemis » Sat Jun 25, 2005 3:28 pm

i have a similar problem as calvinc (i have an bug eye STI)

with "ecuflash /c com1 /m wrx2004 /k kernel.hex /dq test " portmonitor show:

0.00000258 ecuflash.exe IOCTL_SERIAL_SET_QUEUE_SIZE Serial0 SUCCESS InSize: 16384 OutSize: 16384
235 0.00000109 ecuflash.exe IOCTL_SERIAL_GET_BAUD_RATE Serial0 SUCCESS
236 0.00000117 ecuflash.exe IOCTL_SERIAL_GET_LINE_CONTROL Serial0 SUCCESS
237 0.00000089 ecuflash.exe IOCTL_SERIAL_GET_CHARS Serial0 SUCCESS
238 0.00000092 ecuflash.exe IOCTL_SERIAL_GET_HANDFLOW Serial0 SUCCESS
239 0.00000087 ecuflash.exe IOCTL_SERIAL_GET_BAUD_RATE Serial0 SUCCESS
240 0.00000093 ecuflash.exe IOCTL_SERIAL_GET_LINE_CONTROL Serial0 SUCCESS
241 0.00000085 ecuflash.exe IOCTL_SERIAL_GET_CHARS Serial0 SUCCESS
242 0.00000084 ecuflash.exe IOCTL_SERIAL_GET_HANDFLOW Serial0 SUCCESS
243 0.00000126 ecuflash.exe IOCTL_SERIAL_SET_BAUD_RATE Serial0 INVALID PARAMETER Rate: 15625
244 0.00000147 ecuflash.exe IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
245 0.00000277 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 0:
246 0.00003622 ecuflash.exe IRP_MJ_WRITE Serial0 SUCCESS Length 13: 80 10 F0 08 34 02 00 00 04 00 00 04 C6
247 0.00000295 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 0:
248 0.00000280 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 0:
249 0.00000322 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 1: 80
250 0.00000346 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 1: 10
251 0.00000311 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 1: F0
252 0.00000287 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 1: 08
253 0.00000432 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 1: 34
254 0.00000308 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 3: 02 00 00
255 0.00000466 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 4: 04 00 00 04
256 0.00000339 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 1: C6
257 0.00003622 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 0:
258 0.00000356 ecuflash.exe IRP_MJ_READ Serial0 SUCCESS Length 0:
...

so my ecu reply at "80 10 F0 08 34 02 00 00 04 00 00 04 C6 " but dont give the file
i know that now it work with UK WRX, but this means that it will work with my interface (on next relase of ecuflash.exe) or this means that my interface don't work ?
thank you for you job cboles
Nemis
 
Posts: 66
Joined: Thu Dec 30, 2004 3:58 am
Location: italy

Postby calvinc » Sun Jun 26, 2005 12:27 am

Is your STi drive-by-wire? If so, it probably uses a newer ECU which has a different init sequence and kernel requirements. The utility I released doesn't cover this yet, but I will be working on that soon. I just need to get access to an STi around Seattle for a little bit to test.
i'm in south africa, so we get AUS/SA spec vehicles. mine is a MY05 spec STI but ours are all cable throttle and 2.0lt. the 05's differ from the 03/04 in that they are the first to come with DCCD so i suspect there are some ECU changes too.

let me know if i can do any remote testing for you. i'll be trying your app again but with the flash block connected 'home made' style.

calvin.
calvinc
 
Posts: 163
Joined: Sun Apr 24, 2005 10:18 am
Location: south africa

Postby NeverLies » Sun Jun 26, 2005 12:43 am

I can successfully dump my ECU also but needed to connect the block connector with a home made connector. Otherwise, ECU was not communicating with Colby application.
NeverLies
 
Posts: 179
Joined: Tue Apr 12, 2005 1:49 am

Postby Spiider » Sun Jun 26, 2005 12:07 pm

I have my "flash block" connector permently jumpered, maybe thats why I had no trouble dumping my ecu. (Not the green plugs, the white one.)
Spiider
 
Posts: 191
Joined: Thu Mar 10, 2005 4:16 pm

Postby Nemis » Sun Jun 26, 2005 12:43 pm

Spiider wrote:I have my "flash block" connector permently jumpered, maybe thats why I had no trouble dumping my ecu. (Not the green plugs, the white one.)


what is this connector ?
Nemis
 
Posts: 66
Joined: Thu Dec 30, 2004 3:58 am
Location: italy

Postby calvinc » Sun Jun 26, 2005 10:52 pm

now the question remains with colby...during your initial testing, did you have the flash block connected?

calvin.
calvinc
 
Posts: 163
Joined: Sun Apr 24, 2005 10:18 am
Location: south africa

Postby calvinc » Mon Jun 27, 2005 3:46 am

excellent work colby! well done!

my ecu image now joins the list. it seems the flash block connector has to be connected for anything to happen.

another strange thing is that i had to use the wrx2002 (4D FF B4) parameter and not the wrx2004. might i make a suggestion to label them as dbc (drive by cable) and dbw (drive by wire). mine is a 2005 spec but dbc. if the 2004 wrx you tested on is dbw then it might be a valid point...if not then i dont know who said it :-)

calvin.
calvinc
 
Posts: 163
Joined: Sun Apr 24, 2005 10:18 am
Location: south africa

Postby Nemis » Mon Jun 27, 2005 7:30 am

calvinc wrote:excellent work colby! well done!

my ecu image now joins the list. it seems the flash block connector has to be connected for anything to happen.


what is this "flash block connector " ? how i must connect?
i have connect only green test mode connector and my log is very similar to your Portmon_wrx2004.txt on first page :-(
Nemis
 
Posts: 66
Joined: Thu Dec 30, 2004 3:58 am
Location: italy

Postby NeverLies » Mon Jun 27, 2005 8:27 am

You have a white connector near the 2 green ones. There are 4 wires on it. Two yellow, one red and one black. Connect yellow together and black with red.

__--__
| + + |
| | | |
| + + |
-------
NeverLies
 
Posts: 179
Joined: Tue Apr 12, 2005 1:49 am

Postby cboles » Mon Jun 27, 2005 9:52 am

yes - we may need to create more ecu/car categories on the forum. to be clear, both the USDM 02-03 WRX and USDM 04-05 WRX are drive by cable. the ECUs in these two versions use a different init sequence for reflashing and significant code changes, so i made seperate subforums. neither of these USDM models requires more than connecting the green test mode connector to read out the flash memory. both require the additional reflashing connector to actually reflash though. i need some help finding a source for these connectors for everyone (see another post of mine). it's interesting that the connector config is different for cars outside the US.

does anyone have a good breakdown of how the various WRX/STi models worldwide relate to each other in terms of engine / ECU version?


calvinc wrote:excellent work colby! well done!

my ecu image now joins the list. it seems the flash block connector has to be connected for anything to happen.

another strange thing is that i had to use the wrx2002 (4D FF B4) parameter and not the wrx2004. might i make a suggestion to label them as dbc (drive by cable) and dbw (drive by wire). mine is a 2005 spec but dbc. if the 2004 wrx you tested on is dbw then it might be a valid point...if not then i dont know who said it :-)

calvin.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby Spiider » Mon Jun 27, 2005 1:22 pm

I have the ecu versions:

2002/2003
US WRX 01/02 - AF420
US WRX 01/02 - AF421
US WRX 01/02 - AF422
US WRX 01/02 - AF423
US WRX 01/02 - AF424
US WRX 01/02 - AF425
US WRX 03 - AJ030
US WRX 03 - AJ031
US WRX 03 - AJ040
US WRX 03 - AJ041
US WRX 03 - AJ052
US WRX 04 - AH791
US WRX 04 - AH792
US WRX 04 - AH801
US WRX 04 - AH802
UK WRX 01/02 - AF530 7552
UK WRX 01/02 - AF530 7554
UK WRX 01/02 - AF531 7555
UK WRX 03 - AH750 5140
UK WRX 03 - AH750 5141
UK WRX 03 - AH751 5142
AUS/SA WRX 01/02 - AF720 7566
AUS/SA WRX 01/02 - AF730 7574
AUS/SA WRX 01/02 - AH570
AUS/SA WRX 03/04 - AF770
AUS/SA WRX 03/04 - AJ420
Forester 01/02- AG200 0133
Forester 01/02- AG540 0243
UK Forester 03 - ag580 1361
UK Forester 03 - ag580 1362
JDM WRX 01/02 - af460 7072
JDM WRX 01/02 - af471 7084
JDM WRX 01/02 - af471 7085
JDM WRX 01/02 - af471 7086
JDM WRX 03/04 - ah200
STI Type UK 01/02 - ah180 2580
STI Type UK 01/02 - ah180 2581
STI Type UK 01/02 - ag820 090
STI Type UK 01/02 - ag820 2591
STI Type UK 01/02 - ag820 2592
STI Type UK 01/02 - ag821 2593
STI Type UK 03 - ah990 5511
STI Type UK 03 - ah990 5512
STI Type UK 03 - ah990 5513
STI Aus Spec 03 - aj000 5521
Legacy Twin Turbo - ag440
Legacy Twin Turbo - ag441
Legacy Twin Turbo - ag451
Legacy Twin Turbo - ag850 2581
Legacy Twin Turbo - ag850 2591

JDM STI 7 01/02 - af480 7541
JDM STI 7 01/02 - af480 7542
JDM STI 7 01/02 - af481 7545
JDM STI 7 01/02 - af481 7546
JDM STI 7 01/02 - af482 7548
JDM STI 7 03 - ah190
JDM STI 7 RA Type C 01/02 - ag970 3391
JDM STI 7 RA Type C 01/02 - ag970 3392
JDM STI 7 RA Type C 01/02 - ag971 3393
JDM STI 7 RA Type C 01/02 - ah970 5340
JDM STI S202
JDM Twin Scroll STI 03 - ah580 5121
JDM Twin Scroll STI 03 - ah581 5122
JDM Twin Scroll STI RAC 03 - ah590 5130
JDM Twin Scroll STI RAC 03 - ah591 5132

2004
US STi aj241
US STi aj242
US Forester aj470
JDM Legacy Twin Scroll ah110
JDM Legacy Twin Scroll ah111
UK/EU Forester ah690
Aus/SA Forester ah710
Spiider
 
Posts: 191
Joined: Thu Mar 10, 2005 4:16 pm

PreviousNext

Return to OpenECU Software

Who is online

Users browsing this forum: No registered users and 7 guests

cron