Page 1 of 1

2002 WRX MTX - 22611AF421

PostPosted: Tue Aug 02, 2005 3:30 pm
by Jeramie
2002 WRX MTX - This one thows a CEL in a 2004 car. (Code - P0340)

More Info about it here. Secondly, this ECU refuses to flash (in an 04 car) any image but the stock image. Odd?

http://forums.nasioc.com/forums/showthread.php?t=803560

Don't know if any of this info will help (but it can't hurt either).

PostPosted: Tue Aug 02, 2005 6:58 pm
by cboles
Can you elaborate on what you mean by "refuses to flash"?

PostPosted: Tue Aug 02, 2005 7:13 pm
by Jeramie
Image

Something Just like this. If you like I'm sure I could swap it back in and get some screen shots for ya? I've been wanting to try it with the new cable.

PostPosted: Wed Aug 03, 2005 10:06 am
by cboles
I believe this is due to a communication error, not something specific to the what is in the flash memory. Once the kernel is loaded, that is all that is running inside the ECU, so assuming you can load the kernel, what is in the flash is irrelevant at that point. It is possible that the communications rate is too fast for the ECU and there are communication errors. I will be lowering the baud rate in my next release, or at least be making it adjustable just in case.

PostPosted: Wed Aug 03, 2005 11:46 am
by Jeramie
That still doesn't make any sense, as the image I dumped from the ecu will flash back onto the ecu no problem. When trying to use other 02 images (which should be possible as I understand it) they just won't flash. If the commmunications speed was the problem, then I shouldn't be able to flash the dumped image? right :?:

PostPosted: Wed Aug 03, 2005 3:39 pm
by cboles
I follow what you are saying. It's possible that the other ROMs have bit patterns that are more likely to get an error at a higher data rate (e.g. 0xAA or 0x55), but you should see errors occasionally all of the time if you were running this close to the "edge".

PostPosted: Wed Aug 03, 2005 3:41 pm
by cboles
From you log, the point at which the reflash is choking, it's not even reflashing at that moment - it's just receiving data to build a buffer to reflash with...

PostPosted: Wed Aug 03, 2005 6:36 pm
by Jeramie
That was just an example. I will swap it in again and log to see what happens. Possibly this weekend.

PostPosted: Tue Nov 15, 2005 5:36 pm
by qoncept
What is this car from? It looks like a JDM STi or something.. I came up with these offsets for timing and fuel

TIMING_RPM_START = 0x29BB0;
TIMING_RPM_STOP = 0x29BD3;
TIMING_LOAD_START = 0x29BD5;
TIMING_LOAD_STOP = 0x29BF4;
TIMING_START = 0x29BF7;
TIMING_STOP = 0x29D16;

FUEL_RPM_START = 0x2935D;
FUEL_RPM_STOP = 0x29380;
FUEL_LOAD_START = 0x29382;
FUEL_LOAD_STOP = 0x293A1;
FUEL_START = 0x293A4;
FUEL_STOP = 0x294C3;

RPMs go up to 7600 in each, as opposed to 6400 like all the other maps I've looked at.

PostPosted: Thu Dec 22, 2005 2:00 pm
by Jeramie
LOL. This was supposed to be a 2002 WRX ecu. I purchased it off someone on NASIOC.

That info is interesting. I still have the ecu sitting in a box doing nothing.

PostPosted: Sat Dec 24, 2005 8:35 am
by NeverLies
What is written on the ECU sticker ?

PostPosted: Sat Dec 24, 2005 10:09 am
by crazymikie
We checked yesterday- according to the sticker, it's an af421.

Sounds like it should be a USDM ECU. Very odd....