Big sized autosar software component after arxml import in system composer

I created simulink models (slx) from an arxml file by using arxml importing that includes more than 10 components. After creation I checked empty model size, they are around 12MB each. That is so weird, also empty model compile time and build time is now enourmous. Each model only has SR and CS ports, no implementation, all terminated or grounded. Is there any workaround to this issue. I would expect faster build time and less sized models.

[Josh Kahn]

Hi Melih,

Can you please open a support ticket for this one and send us the ARXML file to take a look at?

https://www.mathworks.com/support/servicerequests/create.html

Josh

[Melih]

Thank you Josh, I opened a ticket; however arxml is confidential in this case.

[Josh Kahn]

Thanks Melih,

FYI, We do have a process in place for handling confidential data under NDA if that is a route you would be interested in.

Josh

Answer 1

[Josh Kahn]

When we import arxml files, it is not just the information for building the skeleton model, but also can contain the aspects of the AUTOSAR dictionary that would be imported as well.

• This can include items like interface definitions (sender receiver, client server or mode switch interfaces) that are just defined as interfaces and may not be used.
• Also may include various Application types that may map to implementation data types.
• It is also possible that the skeleton model may have many inports / outports, runnables as well as client and servers.

The last point about many inports and outports, runnables as well as clients and servers would be very visible in the skeleton model that would be created from the imported arxml file. However, other imported constructs such as imported application types also add to the size. So in summary, yes, several things can contribute to the size of the imported model but without seeing the ARXML file, it is hard to tell what exactly is contributing in your case.

Hope this helps,

Josh