How to migrate ARXML (ECU Extract) from AUTOSAR 3.2.2 to 4.3.1
Show older comments
Hello,
In my case, I already have Simulink models and ARXML files based on AUTOSAR Classic Platform version 3.2.2.
I would like to ask about the most efficient way to migrate these ARXML files to AUTOSAR 4.3.1. This migration is required to ensure compatibility with our current product package.
Any recommended tools, workflows, or best practices would be greatly appreciated.
Regards,
Nhan Phan
Answers (1)
Samhitha
on 29 Jan 2026
0 votes
In MATLAB/Simulink, the recommended way to do this is by using the AUTOSAR Toolbox. The existing AUTOSAR 3.2.2 ARXML files can be imported into Simulink, and the model can then be updated to target AUTOSAR Classic 4.3.1. After that, the ARXML can be regenerated in the 4.3.1 format directly from the model. During this process, any compatibility or validation issues can be fixed within Simulink before exporting the updated ARXML files.
Hope this helps!
4 Comments
Nhan Phan Trung
on 30 Jan 2026
Samhitha
on 30 Jan 2026
The AUTOSAR Component workflow in MATLAB/Simulink supports AUTOSAR Classic Platform 4.0 and above for native component modeling and ARXML generation. AUTOSAR 3.2.2 is not directly supported as a target version for components. However, AUTOSAR 3.2.2 ARXML files can still be imported into MATLAB/Simulink for reference, analysis, or migration purposes. To generate valid AUTOSAR 4.x ARXML, the usual approach is to import the 3.2.2 ARXML, update the model to target AUTOSAR 4.x (e.g., 4.3.1), resolve any compatibility issues, and then regenerate the ARXML in the newer format.
Thanks
Nhan Phan Trung
on 30 Jan 2026
Samhitha
on 30 Jan 2026
Yes, you need both Embedded Coder and the AUTOSAR Toolbox.
Categories
Find more on AUTOSAR Blockset in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!