AUTOSAR types mapping in code generation

5 次查看（过去 30 天）
Francesco Dini
Francesco Dini 2021-9-1
编辑： Francesco Dini 2021-9-1
Hello,
I'm developing an AUTOSAR model following this process:
  1. Importing the model from third party .arxml file
  2. Applying modification to the model in Simulink
  3. Generating C code from Simulink
Inside the .arxml from wich I import the model I see the following lines:
<SHORT-NAME>TypeMapping_General</SHORT-NAME>
<DATA-TYPE-MAPS>
.....
<DATA-TYPE-MAP>
<APPLICATION-DATA-TYPE-REF DEST="APPLICATION-PRIMITIVE-DATA- TYPE">/DataTypes/AdtLowPowerVoting</APPLICATION-DATA-TYPE-REF>
<IMPLEMENTATION-DATA-TYPE-REF DEST="IMPLEMENTATION-DATA-TYPE">/DataTypes/IdtLowPowerVoting</IMPLEMENTATION-DATA-TYPE-REF>
</DATA-TYPE-MAP>
......
So what I expected to happen inside generated .c/.h files was that all the input/output ports defined inside the model that were declared using application data type "AdtLowPowerVoting" were replaced inside source C code with implementation data type "IdtLowPowerVoting", but this does not happen, in fact inside generated code I find a lot of AdtLowPowerVoting variables declaration (and what I've just described happens for all the Adt/Idt pairs declared in DATA-TYPE-MAP in .arxml file). Does anyone know how to let Idt data type to replace Adt type inside generated code? Which properties should I check? Thanks in advance for any help,
Francesco

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

回答（0 个）

类别

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

标签

产品


版本

R2021a

Community Treasure Hunt

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

Start Hunting!

Translated by