In an external mode simulation, you can tune parameters in real time and monitor target application signals. Using the Run on Hardware Board app, you can set up and run external mode simulations (Simulink Coder) that use an XCP communication channel.
For an external mode simulation, you:
Build the target application on your development computer.
Deploy the target application to the target hardware.
Connect Simulink® to the target application that runs on the target hardware.
Start execution of generated code on the target hardware.
Configure and run an external mode simulation (Simulink Coder) that uses the XCP communication protocol. During the simulation:
Monitor a signal by using a Scope block, a Dashboard block, and the Simulation Data Inspector.
Tune a parameter by using a Dashboard block.
Create a folder for this example.
mkdir ext_mode_xcp_example cd ext_mode_xcp_example
Open Simulink and create a simple model,
xcpExample, which contains
Double-click the Sine Wave block. Set Sample time to 0.1, and then click OK.
Connect the Sine Wave block to the Scope block and
name the connection, for example,
Configure the signal for logging:
From the context menu, select
Log Selected Signals.
If you do not enable signal logging, you cannot view the signal by using the
Scope block or stream signal data to the Simulation Data
Configure the Half Gauge block to monitor the value of
Double-click the Half Gauge block.
In the Simulink Editor, select
In the Block Parameters dialog box:
Connect the block to
In the Maximum field, enter a value, for example,
Configure the Knob block to tune the Amplitude parameter of the Sine Wave block:
Double-click the Knob block.
In the Simulink Editor, select the Sine Wave block.
In the Block Parameters dialog box:
Connect the block to the Amplitude parameter of the Sine Wave block.
In the Minimum and Maximum fields, enter values, for example, 0.1 and 1 respectively.
Save the model as
From the Apps tab on the Simulink toolstrip, click Run on Hardware Board.
In the Run on Hardware Board pop-up, set Hardware board to a supported ARM® Cortex®-A QEMU emulator.
On the Hardware tab, in the Prepare section, click Hardware Settings. The Configuration Parameters dialog box opens, displaying Hardware Implementation settings that are determined by the hardware board.
On the Solver pane:
In the Type field, specify
Under Solver details, in the Fixed-step size field, specify a value, for example, 0.1.
On the Hardware Implementation > Hardware board settings > External Mode pane, set Communication interface to
Click OK. Then save the model.
Specify a nondefault value for the simulation stop time. On the
Hardware tab, in the Run on Hardware
section, set Stop Time field to
The software builds, deploys and starts the model as an application on the connected hardware board.
Connects Simulink to the target application.
Runs the generated model code.
You can also perform the steps separately.
On the Hardware tab, in the Deploy section, click Build, Deploy & Start .
In the Run on Hardware section, expand the Monitor & Tune drop-down.
Under Step By Step Commands, click Connect
You can monitor
Test Signal through the:
Scope block –– Double-click the block.
Simulation Data Inspector –– Click the Simulation Data Inspector button. When the Simulation Data Inspector opens, select the Test Signal check box, which displays streamed data.
To change the amplitude of the sine wave, rotate the pointer on the Knob block to the required value.
To tune tunable (Simulink) block parameters during a simulation, you can also use these methods:
If a block parameter is a variable in the MATLAB® workspace, in the Command Window, assign a new value to the variable. Then, in the Simulink Editor, update the diagram by pressing Ctrl+D. Simulink downloads the new value to the target application.
Open the Block Parameter dialog box. In the parameter field, specify the required value. When you click Apply or OK, Simulink downloads the new parameter value to the target application.
To change multiple tunable parameters simultaneously:
In the Prepare section, click Batch Mode.
In your model, modify the required parameters.
Click Update All Parameters. The software modifies the parameter values on the target application simultaneously.
For more information about parameter tuning with generated code, see Create Tunable Calibration Parameter in the Generated Code. If your model contains a Stateflow® chart, you can view state activity. For more information, see Animate Stateflow Charts (Stateflow).
To stop the execution of generated model code before
StopTime is reached and disconnect the target application, on the Simulink Editor toolbar, click the Stop button .
If you want to disconnect the target application from Simulink without stopping code execution, click . Then, under Step By Step Commands, click Disconnect.
You can control an XCP external mode simulation through:
The Hardware tab on the Simulink Editor toolbar. To display the Hardware tab, from the Apps tab on the Simulink toolstrip, click Run on Hardware Board.
The External Mode Control Panel. To open this dialog box, on the Hardware tab, in the Prepare section, click . Then, under Signal Monitoring & Tracing, click Control Panel.
This table lists the controls that you can use for an XCP external mode simulation.
|External Mode Action||Toolstrip||External Mode Control Panel|
Build target application and run on hardware.
Run on Hardware > Build, Deploy & Start
Connect Simulink to a waiting or running target application.
Run on Hardware > Connect
When Simulink is connected to the target application, Connect appears dimmed and Disconnect is active.
When Simulink is connected to the target application, Connect changes to Disconnect.
Start real-time execution of generated code in the target environment.
Run on Hardware > Start
Start Real-Time Code
When the generated code starts executing, the button changes to Stop Real-Time Code.
Disconnect Simulink from the target environment, but do not stop real-time execution of code.
Run on Hardware > Disconnect
When Simulink is disconnected from the target application, Disconnect appears dimmed and Connect is active.
Stop target application execution and disconnect Simulink from the target environment.
In Run on Hardware section, Stop button .
Stop Real-Time Code
Tune batch of block parameters.
In Prepare section, Batch Mode and Update All Parameters buttons.
To tune a batch of block parameters:
To run these commands, you must have a Simulink model open and a target application running.
Set the model simulation mode to external mode.
Connect Simulink to the target application.
Run generated model code.
To tune a parameter, change its workspace variable value through a line command. For example, if a block parameter value is specified as a
Simulink.Parameter object, assign the new value to the
myParamObj.Value = 5.23;
To download the new value to the target application, update the model.
Stop the target application and disconnect Simulink from the target environment.
To disconnect Simulink from the target application without stopping execution of generated code, use this command:
This table describes limitations that apply to external mode simulations that use XCP communication.
Parameter updates that change model structure
You cannot change:
If you make parameter updates that change the model structure, you must rebuild the target application.
You can change numerator and denominator polynomial parameters for the Transfer Fcn, Discrete Transfer Fcn, and Discrete Filter blocks if the number of states does not change.
You cannot change zero entries in the State-Space, Zero-Pole, and Discrete Zero-Pole blocks in the user-specified or computed parameters, that is, the A, B, C, and D matrices obtained by a zero-pole to state-space transformation.
In the State-Space block, if you specify the matrices in the controllable canonical realization, then changes to the A, B, C, and D matrices that preserve this realization and the dimensions of the matrices are allowed.
If the Simulink block diagram does not match the target application, Simulink produces an error stating that the checksums do not match. The checksums take into account the top models, but not referenced models. To rebuild the target application, use the updated block diagram.
Signal value display
The graphical display of signal values during a simulation is not supported. For example, you cannot use the Data Display in Simulation menu items Show Value Labels When Hovering, Toggle Value Labels When Clicked, and Show Value Label of Selected Port. For more information, see Display Signal Values in Model Diagrams (Simulink).
Signal triggering and data archiving
The Signal & Triggering, Arm Trigger, Cancel Trigger, and Data Archiving features available on the External Mode Control Panel are not supported.
Dynamic selection of signals for streaming is not supported. To select different signals for streaming, rebuild the model.
|Overriding signal logging settings||Overriding signal logging settings by using the Signal Logging Selector is not supported.|
Compiler debug symbol format
Your toolchain must generate debug information in one of these formats:
If you set
Signals, parameters, and states must be specified as global variables. The target memory locations where the variables are stored must lie in the range 0 – 4294967295.
You cannot tune parameters that are structures.
Pure integer code
Pure integer code is supported. For code generation, if
If you do not specify
If you specify
Uploading of variable-size signals is not supported.
Scope and Floating Scope blocks, and Scope Viewer
Some signal data types are not supported. The simulation produces a warning.
Scopes in referenced models
In a model hierarchy, if the top model runs in external mode and a referenced model runs in normal or accelerator mode, scopes in the referenced model are not displayed.
Nonzero simulation start time
Nonzero simulation start times are not supported. Use the default value for Solver > Start time,
File-scoped data is not supported. For example, data items to which you apply the built-in custom storage class
Row-major code generation
Code generated with the row-major format is not supported.