It is my car and it is making huge flames 
GT innovations done great work on this ECU, as a ST10 ME7 isn't the easiest to add code!

Does the code have to be on mpc or can you branch out to flash?

I see...

Are you using tsrldyn for cutting ignition?

I'm interested in making some code for ME7.5.20/30 which come with ST10Fxx. I wonder how different this ECU is from those.

Initially i was trying to load flash at 0x800000 and ida was not translating the address bytes correctly and in such a case i can not rename those addresses appropriately. Then i switched to 0x80000 and everything was fine.As for mpc checksums i would prefere to not interfere at all what i understood from this is that you don`t need to put the ecu on TEST mode if you are running the mpc cksum off patch.

Giving that St10f27x has not Direct documentation what so over it is harder to match all things as on me7.5 or other well documented ecus. Tkmwl is way off at some points... As i said before it looks like a hybrid me7/me9 ecu.

As far as I can tell only the TT have things like no MLHFM, mk5 R32, A3 3.2 8P all have it from what I've seen so far, wondered why that was as it looks like older TT's had some of these changes too but A3 matches mk5 Golf so don't think it's an ST10 only thing, seems to be TT?

You have MSHFMU which is actually not described on all or most of the a2l files out there.But if you check some other engines like
s4 v8 you will find it.It is just not called MLHFM but it looks like one only sorter.If you took like 5 seconds to look at my definitions you would have seen it...Have defined it myself using another damos from a v8 engine.

Then someone will say there is no MLMIN or MLMAX and/or other maps/limits.. Look below at the attached image..
There are tons of maps and things that are not defined from most a2ls and i am really curious in what they all do so...

There is a point in the code checking the first byte of the MSHFMU(MLMIN) and the last byte of MSHFMU(MLMAX) like a hardcoded check without any kind of actual declaration in any document or a2l.

i have posted all this things and if anyone likes to understand he only needs to put the names and the enums i have posted to a freshly made ida project using the loading details i published on the first page.

Anyway there are too many things and i am still trying to work on those so i can have a good FI solution in the future.

address mlmin 0x8fe490
address mlmax 0x8fe592

Yeah I went through such changes a while back in the definition files area regarding Jim's TT mk2 3.2T, covered it then, I generally used Porsche files if I remember right, just trying to rescue data at mo to help out;

997 TT Defining by Rick B, on Flickr

I think the mk1 TT DAMOS file knocking about has it too doesn't it? The MLHFM map is way off which I think I assumed it used an MSHFMU map too, hence mentioning the TT based changes only regardless of ST10 or not? Didn't have much call to investigate further though at the time.

Took a look at your binary and I can assure you that flash resides at 0x800000.
Let me give you one more hint - you can't directly use a KTAG readout for the MPC. Data has to be shifted a bit. Take a look at Porsche 997TT A2L&hex, it's public and has a very similar data arrangement. Or you can read MPC with flashit or minimon, then it'll come out at correct addresses.