Why the TLC based customizations made does not affect the generated A2L file when using "coder.asap2.export" ?

I am using MATLAB R2022b version. I am generating an A2L file as part of my code generation workflow, and I apply certain TLC based customizations using the workflow described in https://www.mathworks.com/help/rtw/. However, I do not see my customizations in the generated A2L file when using "coder.asap2.export".

Answer 1

[MathWorks Support Team]

There are two ASAP2 generation workflows and two methods of customization:

1. Old TLC based workflow: This is the workflow that generates ASAP2 as part of code generation when the configuration setting GenerateASAP2 is set to 'on'. You can refer to the following documentation for more information: https://www.mathworks.com/help/rtw/. The TLC based customizations that correspond to this workflow are explained in the following documentation: https://www.mathworks.com/help/rtw/. Also, the customizable TLC files are clearly explained in the documentation.
2. New coder.asap2.export workflow: This is the new workflow introduced since R2021a that generates ASAP2 using the command 'coder.asap2.export' or the corresponding GUI as shown in the following documentation: https://www.mathworks.com/help/rtw/ug/asap2-cdf-calibration.html. The TLC based customizations given the following documentation: https://www.mathworks.com/help/rtw/ does not apply to or affect this workflow. To customize the generated ASAP2 file, refer to the following documentation: https://www.mathworks.com/help/ecoder/ug/a2l-custom-cd.html. The APIs available for customizations in this workflow (such as 'getEcuDescriptions' and 'coder.asap2.Function') are mentioned in the following documentation pages.
   • 'coder.asasp2.Function': https://www.mathworks.com/help/rtw/ref/coder.asap2.function.html
   • 'getEcuDescriptions': https://www.mathworks.com/help/ecoder/ref/coder.asap2.getecudescriptions.html  

These two customizations cannot be mixed as they correspond to totally different ASAP2 generation workflows. Therefore, it is expected that the customizations made using the TLC based workflow do not take affect when using the new 'coder.asap2.export' workflow.