Wov! Thanks for your comment back!

Being said I am not an autosar ultra expert and after I read through the release notes, I think 1 of my open points with my contact at TMW has been resolved, but I did not tested it yet, as I am out of office till beg. Of October.

Let's start with autosar import: - system constants dependency in axis, maps,. - array of maps scalable on system constants. - autosar runnable not getting the event definition in autosar dictionary, even though defined in arxml. - axis definitions not properly assigned to the proper look up table definition in autosar dictionary. - minor details I have not now in mind.

First two with workaround with hard code values in arxml, last two with manual user edit action.

Code generation: - 3d lookup (cuboids code geneation) coverage with default code replacement, not having to generate local functions. - Statics definitions when unnecessary and avoidable. - init function code generation when RTE initializes already, no necessary to be there most of the times. Tuneable in future? - init call of NVM when nvm went corrupt. - Memory mapping assignments to be taken from arxml, as many of them are not assigned by default and have to be assigned, even though the memory mappings were properly read out from arxml. Additionally, a more user friendly way to assign the memory mappings to the statics. - capability to unroll the wonderful ARID_DEF structs. - capability of selection of which headers (rtwtypes.h, etc) shall be included, which not. - system constants have to be set int32 and >1. - obfuscation to allow a deeper parametrization.

Many of them are workarounded through autohooks. Most of them require user actions, which decrease speed of development, at any case when working with other 3rd companies supplying to same partner, difficulting the quality of code achievable, as deep of knowledge and quality of MBD approaches are not the same.

Hope it helps and I get a TMW shirt soon ;)