Mystery maps in A4SGD10C

Developer topics relating to software that provides a tuning UI to alter ECU code and data

Moderator: Freon

Mystery maps in A4SGD10C

Postby Kha0S » Fri Jan 27, 2006 2:52 pm

I found these two 3D maps embedded in the A4SGD10C ROM... any ideas what they are?
Attachments
mystery-maps.png
mystery-maps.png (605.74 KiB) Viewed 6127 times
Kha0S
 
Posts: 106
Joined: Tue Jan 11, 2005 12:30 pm
Location: MY02 USDM WRX / Nashua, NH

Postby Kha0S » Mon Jan 30, 2006 12:21 pm

C'mon guys... someone out there has to have some clue of what these are...
Kha0S
 
Posts: 106
Joined: Tue Jan 11, 2005 12:30 pm
Location: MY02 USDM WRX / Nashua, NH

Postby Freon » Mon Jan 30, 2006 1:30 pm

I've found one (or more) of these maps in most of the ROMs I've looked at. I have no idea what it is for. It looks like more of a mask than a real map.
Freon
 
Posts: 700
Joined: Thu Nov 17, 2005 5:50 pm
Location: Indianapolis, IN

Postby silverpike » Thu Feb 02, 2006 11:50 pm

Perhaps it's knock detection? I know that in most cases, the knock sensor isn't used at high load and high RPM. It almost looks like this in the table.

The best way to discover what a table's used for is to find out where in the code it's referenced (dissassembly) and then find out if there's an IO port being accessed nearby in the code. Once the IO ports have been mapped, you can tell what output is being controlled by that code, and from there the table gets much easier to figure out.
User avatar
silverpike
 
Posts: 15
Joined: Tue Aug 16, 2005 4:48 pm
Location: Los Angeles, CA

Postby MRF582 » Fri Feb 03, 2006 5:31 am

silverpike wrote:Perhaps it's knock detection? I know that in most
cases, the knock sensor isn't used at high load and high RPM. It almost
looks like this in the table.

The best way to discover what a table's used for is to find out where in
the code it's referenced (dissassembly) and then find out if there's an IO
port being accessed nearby in the code. Once the IO ports have been
mapped, you can tell what output is being controlled by that code, and
from there the table gets much easier to figure out.


this can't be the knock detection map b/c the reason the stock sensor
doesn't read above 5000 or 6200rpms depending on what you believe is
because it runs out of space. To save 'bytes' this system of hexadecimal
is used in the ECU which is makes it so confusing.

There are two other maps in the ECU which control Knock detection and
learning. Knock Learning is only done up to 5000rpms only. But Knock
Detection is done over a range upto 6200rpms or so. You'll see your
'Ignition Correction' or "Dynamic Advance' still work. Meaning it'll
decrease when the ECU pulls timing for knock.
MRF582
 
Posts: 34
Joined: Thu May 19, 2005 11:25 am

Postby Spiider » Fri Feb 03, 2006 8:08 pm

MRF582 wrote:To save 'bytes' this system of hexadecimal
is used in the ECU which is makes it so confusing.


No offense intended but what do you think microcontrollers are programmed with?

Hex / assembly langage mnemonics are the only tools that I and many others program them with.

I don't know what those mystery maps are yet, I have been meaning to sit down with IDA and the datasheet and take a look.
Spiider
 
Posts: 191
Joined: Thu Mar 10, 2005 4:16 pm

Postby MRF582 » Fri Feb 03, 2006 10:42 pm

I understand that. I didn't mean what i said earlier in a bad way. I just couldn't think of the correct words to describe why the situation occurs in the factory ECU.
MRF582
 
Posts: 34
Joined: Thu May 19, 2005 11:25 am

Postby Spiider » Sat Feb 04, 2006 6:02 am

I didn't mean it to be insulting, sometimes people have funny ideas that high level (ie. man readable) code is what is being executed inside the microcontroller.
Spiider
 
Posts: 191
Joined: Thu Mar 10, 2005 4:16 pm

Postby MRF582 » Sat Feb 04, 2006 5:29 pm

Oh yeah I see what you mean.

But i'm sure the frequent posters of this board are 'slightly' above average in intelligence to say the least.
MRF582
 
Posts: 34
Joined: Thu May 19, 2005 11:25 am


Return to Tuning Software

Who is online

Users browsing this forum: No registered users and 6 guests