Calibrate Generated Code and Monitor Signals Through XCP and Third-Party Tools

When you create an external mode target application that uses an ASAM MCD-1 XCP communication channel, you can also generate an ASAP2 file that provides a description of the Simulink^® Coder™ XCP slave configuration. The description enables third-party calibration tools such as ETAS^® INCA and Vector CANape^® to connect to the external mode target application. You can use the third-party tools to calibrate generated code and monitor signals in environments supported by the third-party tools, for example, a vehicle, a test bench, or a virtual environment on a PC.

Use this workflow.

Configure your model.
1. On the Apps tab, click Run on Custom Hardware, which displays the Hardware tab.
2. In the Hardware section, in the System Target File Description field, select Embedded Coder (ert.tlc).
3. In the Prepare section, click Hardware Settings, which opens the Configuration Parameters dialog box.
4. Clear Generate code only.
5. Specify Toolchain settings for your development computer.
6. Select ASAP2 interface.
7. Select External mode.
8. Set Transport layer to XCP on TCP/IP or XCP on Serial.
9. For Mex-file arguments, specify the required arguments. For example:
  For XCP on TCP/IP, specify the IP address of the target processor and the port number of the TCP/IP server.
  For XCP on Serial, specify the serial port ID and the baud value.
10. Click OK.
Generate the target application and ASAP2 file.
1. On the Hardware tab, in the Run on Hardware section, click Monitor & Tune.
2. Under Step By Step Commands, click Build for Monitoring.
  In the code generation folder, the build process generates the XCP external mode target application modelName.exe and the ASAP2 file modelName_CoderXCPSlave.a2l. The ASAP2 file contains an IF_DATA XCP block that describes the Simulink Coder XCP slave configuration.
  … /begin IF_DATA XCP /begin PROTOCOL_LAYER … /end PROTOCOL_LAYER … /begin XCP_ON_TCP_IP … /end XCP_ON_TCP_IP /end IF_DATA …
Import the ASAP2 file into your third-party tool.
Manually run the external mode application on your target hardware.
Through XCP, connect the third-party tool to the target application.
Using the third-party tool, perform data acquisition and calibration of generated code.

If you select model configuration parameter Generate code only, then the build process does not generate the ASAP2 file. Before step 3:

Compile the generated code manually.
Use the coder.xcp.a2l.addCoderXCPInfo function to create the ASAP2 file, modelName_CoderXCPSlave.a2l.

By default, the build process:

Runs rtw.asap2MergeMdlRefs to merge the ASAP2 files generated from referenced models into a single ASAP2 file.
Runs rtw.asap2SetAddress to replace placeholder address strings with addresses extracted from the debug symbol file specified for model configuration parameter Mex-file arguments.

If you do not want to merge ASAP2 files from referenced models or perform address string replacement, run coder.xcp.a2l.addCoderXCPInfo as shown:

coder.xcp.a2l.addCoderXCPInfo(buildFolder, 'MergeMdlRefs', false, ...
                              'SetAddress', false);

If you want to specify a GRT system target file for code generation, use the manual approach.

Documentation

Calibrate Generated Code and Monitor Signals Through XCP and Third-Party Tools

See Also

Related Topics

Embedded Coder Documentation

Support