MSS60 XDF Mappings

[Martyn]

Potentially, I've had similar problems before when I've tried to purchase Femto Flasher.

[terra]

Is it a UK to Russia issue? Would US to Russia work?

[Martyn]

I tried to buy the MSS60 funktionsrahmen from JMGarage this morning but my PayPal account won't let me send money to Russian addresses

[MpowerE36]

Here MSS60 SP DATEN I found but all have EWS3 activated. Maybe someone has more MSS6x SP DATEN ?

https://1drv.ms/u/s!AoYWDjVCL5J4gSDjKsH0dOeyZ6vx?e=sRr9Lj

[terra]

Long shot, but anyone here have access to M3 GT4 software? Wondering if those have a factory EWS Delete.

[terra]

I think I've found the K_EWS_FETRAWE_WEG parameter in the injection program (see screenshot). There is no other parameters use in this subfunction but there are several parameters use in child and parent functions which are not identified in the "inj.a2l" (ex : 0x708D0 or 0x79CB7), so maybe it is a good lead. Unfortunately, I’m not yet familiar with this MPC5xx assembler language to understand what the program does in this aera.

Turning on auto comments makes it much easier to follow when you don’t have the instruction set memorized.

[MpowerE36]

this should help.
mostly in german but very easy to identify virtually everything

http://s000.tinyupload.com/index.php...49121425428317

http://s000.tinyupload.com/index.php...61709163219273

I didn't succeed in opening the "5.06.doc". It seems to be damaged. Is it the same for you ?

Strange thing : it seems to be exactly the same funktionsrahmen documents than the MSS54. Only the name of the project has changed. But when you look at the .a2l, it is clear that there have been many evolutions in the MSS60. The MSS60 funktionsrahmen documents seem to be different when I look at the preview available in this website : http://jmgarage.ru/funktionsrahmens-and-documentation/

[MpowerE36]

I think I've found the K_EWS_FETRAWE_WEG parameter in the injection program (see screenshot). There is no other parameters use in this subfunction but there are several parameters use in child and parent functions which are not identified in the "inj.a2l" (ex : 0x708D0 or 0x79CB7), so maybe it is a good lead. Unfortunately, I’m not yet familiar with this MPC5xx assembler language to understand what the program does in this aera.

[terra]

I don't believe it's public yet. I don't personally know how to do it. I've been disassembling the software and trying to wrap my mind around it. Have a couple areas that look promising, but I'm not seeing anything quite like the MSS54 where it's a single byte in the parameter space. That prototype firmware linked to above also apears to be from a point in development when the MSS60 was still EWS3, so there are some differences to work through.

[MpowerE36]

Hi everyone,

Does anyone know if the immo off for MSS60/MSS65 has not yet become public ?

I intend to look at the disassembled injection program where K_EWS_FETRAWE_WEG is used (Permitted mileage for automatically activating the production mode with the EWS-DME comparison). Maybe the EWS disable byte is used in this aera of the program...

[terra]

Sweet. That inj/ign a2l is a pre-release firmware, but should be a great starting point for generating an XDF.

[hotsd101]

also complete inj and ign a2l

http://s000.tinyupload.com/index.php?file_id=76985708348244175672

[hotsd101]

this should help.
mostly in german but very easy to identify virtually everything

http://s000.tinyupload.com/index.php?file_id=99321849121425428317

http://s000.tinyupload.com/index.php?file_id=18347161709163219273

[Locha7777]

hello i have files for M3 e92 where is make pop and bang if you can handle something with that i can give it you

[alfalfa]

There are so many variants like official MSS60 Software out there. Just the the 240e/241e share the data.
If you know how a a2l is generated you know there is no stable offset. It always depends in which address the new application data is packed. So you have a range of application data and integrate a new label it will be anywhere in this range. You have some data in front of this label with no needed offset and the data behind need the offset of the new integrated label.

I think terra's idea will be the best. Standardize 240e/241e for this thread.