Simulink/Autosar: Unsupported m3iType class M3I.Object for addReferencedType

I try to build a Simulink/Autosar system with SystemComposer.

During "Code and ARXML export" I get the following error message:

The call to autosar_make_rtw_hook, during the after_tlc hook generated the following error:

Unsupported m3iType class M3I.Object for addReferencedType.

The build process will terminate as a result.

Caused by:

Unsupported m3iType class M3I.Object for addReferencedType.

What does this error message mean?

Is there any information available to what this error relates to?

What are situations where such an error might occure?

To what part of Simulink/Autosar is this related?

What is a m3iType and where is it used?

[Attila]

Update:

It seems as if at some point Simulink saved inconsistend data to the used Simulink DataDictonary for one/multiple stored DataTypes.

In contrast to Matlab/Simulink in the past, where everything could be fixed by just manually correcting the file in an text editor, this inconsistency cannot be fixed easily anymore, since the sldd file format, despite only beeing an archive with xml files, is not actually human readable and therefore not "human fixable".

My "solution" was to recreate the entire DataDictonary.

It is sad to see, that Mathworks seems to try more and more to prevent users from finding workarounds for the many issues Matlab/Simulink has.

Answer 1

[Kausthub]

Hi Attila,

A workaround for this issue would be to remove the synthesized AUTOSAR datatypes from the dictionary. For this you can use "AUTOSARProperties" to delete references that could not be removed.

arProps = autosar.api.getAUTOSARProperties("Interfaces.sldd")
arProps.delete("referencePath")

Hope this help!

Answer 2

[Eloi]

sldd is a compressed file, if you open it with 7z (for example) you can access the files inside