Variant handled port interfaces in ARXML

3 次查看（过去 30 天）
Dinesh Kathir Raj Mohan Kumar
回答： Arun 2023-10-27
In the bottom up AUTOSAR development approach, where the Simulink model is created first and ARXML is generated out of it with the AUTOSAR blockset - I am using a variant based model development where the subset of Input and output interfaces are used for one variant and another subset is used for another variant. Much like the example mentioned in - https://se.mathworks.com/help/autosar/ug/configure-autosar-variants-in-ports-and-runnables.html
The generated code works perfectly, no trace of other variant2 related implementation in variant1 code and vice versa
However, the ARXML file generated has the interfaces from both the variants and when the ARXML is imported into DaVinci tools, all the interfaces are visible irrespective of the variant selection. Is there any settings to be changed to generate a variant based ARXML ?

请先登录，再回答此问题。

回答（1 个）

Arun
Arun 2023-10-27
Hey Dinesh,
I understand that you want to generate a variant based ARXML file for your bottom up AUTOSAR development and you are using Variant Source blocks but are not able to generate variant based ARXML.
The model must be created by importing ARXML file containing component descriptions for Simulink to preserve the variation points.
If a model is not created by importing ARXML, then it will only contain variation point proxies which ensure correct code generation, as in your case.
Please refer the MATLAB documentation link for more information:
  1. To createComponentAsModel: https://www.mathworks.com/help/autosar/ref/arxml.importer.createcomponentasmodel.html
  2. To variant source block: https://www.mathworks.com/help/simulink/slref/manualvariantsource.html
Hope this helps.

类别

在 Help Center 和 File Exchange 中查找有关 AUTOSAR Blockset 的更多信息

标签

产品


版本

R2021b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by