How to migrate from AUTOSAR data objects workflow to code mapping workflow?

I am using AUTOSAR data object such as AUTOSAR.Signal, and AUTOSAR.Parameter in my projects. The documentation page for these objects recommends migrating to the Code Mappings editor workflow. However, I am not sure what exactly I should do for each of these objects. Could you provide more guidance?

Answer 1

[MathWorks Support Team]

If you currently model AUTOSAR parameters or variables by using AUTOSAR parameter or signal objects in the base workspace or data dictionary, consider migrating to the Code Mappings editor workflow. The following tables are intended to help you identify what exact path to follow during this migration.

The left column shows the options of the AUTOSAR data objects. The right column shows the corresponding option in the code mapping workflow when using Simulink Data Objects. The entries marked as NA are cases where there is no corresponding code mapping workflow.

For more information on the code mapping workflow please see the following documentation:

https://www.mathworks.com/help/autosar/ug/map-model-elements-using-simulink-autosar-mapping-explorer.html