Specify hardware options to simulate and generate code for models of computer-based systems, such as embedded controllers.
Hardware Implementation pane parameters do not control hardware or compiler behavior. The parameters describe hardware and compiler properties for the MATLAB® software.
Specifying hardware characteristics enables simulation of the model to detect error conditions that can arise when executing code, such as hardware overflow.
MATLAB uses the information to generate code for the platform that runs as efficiently as possible. MATLAB software also uses the information to give bit-true agreement for the results of integer and fixed-point operations in simulation and generated code.
Hardware Implementation Options (Simulink Coder)
Select the hardware board upon which to run your model.
Changing this parameter updates the dialog box display so that it displays parameters that are relevant to your hardware board.
To install support for a hardware board, start the Support Package
Installer by selecting
Get Hardware Support Packages.
Alternatively, in the MATLAB Command Window, enter
After installing support for a hardware board, reopen the Configuration Parameters dialog box and select the hardware board.
the specified system target file is
autosar.tlc. Otherwise, the default is
by Code Generation system target file.
No hardware board is specified. The system target file specified
for the model is
Determine by Code Generation system target file
Specifies that the system target file setting determines the hardware board.
Get Hardware Support Packages
Invokes the Support Package Installer. After you install a hardware support package, the list includes relevant hardware board names.
Specifies the hardware board to use to implement the system this model represents.
When you select a hardware board, parameters for board settings appear in the dialog box display.
After you select a hardware board, you can select a device vendor and type.
The Device vendor and Device type parameter values reflect available device support for the selected hardware board.
When you select a hardware board, the selection potentially
Toolchain parameter value and other
configuration parameter values. For example, if you change the hardware
board selection to
ARM Cortex-A9 (QEMU), the
value changes to a supported toolchain, such as
|Type: character array|
|Safety precaution||No impact|
This parameter sets the static priority of the base rate task. However, the changes that you make in this parameter do not result in any functionality differences on the Raspberry Pi™ hardware.
Detect when a task overrun occurs in a Simulink® model running on the target hardware. Indicate when an overrun has occurred.
A task overrun occurs if the target hardware is still performing one instance of a task when the next instance of that task is scheduled to begin.
You can fix overruns by decreasing the frequency with which tasks are scheduled to run, and by reducing the number or complexity of the tasks defined by your model.
If those solutions do not fix the task overrun condition, and you are using External mode, consider disabling External mode.
|Build action||Option to specify whether you want only build or build and run actions during code generation.||Build and run|
|Build directory||Build directory for Linux running on the hardware board.||/home/pi|
|Run on boot||
Automatically starts a Simulink model deployed on the hardware every time you restart the hardware.
|CAN Bus Speed (kBit/s)||Bus speed in kilo bits per second.||500|
|Oscillator Frequency (MHz)||Oscillator frequency in mega hertz.||16|
|Interrupt Pin||Interrupt pin value to enable reading the message.||12|
|Allow All Messages||Option to allow all messages.||Off|
|Buffer 0 ID Type||Buffer 0 id type.||Normal|
|Buffer 0 Acceptance Mask (RXMO)||Value for buffer 0 acceptance mask (RXMO).||0|
|Buffer 0 Acceptance Filter (RXF0)||Value for buffer 0 acceptance filter (RXF0).||255|
|Buffer 0 Acceptance Filter (RXF1)||Value for buffer 0 acceptance filter (RXF1).||255|
|Buffer 1 ID Type||Buffer 1 id type.||Normal|
|Buffer 1 Acceptance Mask (RXM1)||Value for buffer 1 acceptance mask (RXM1).||0|
|Buffer 1 Acceptance Filter (RXF2)||Value for buffer 1 acceptance filter (RXF2).||255|
|Buffer 1 Acceptance Filter (RXF3)||Specify a value for buffer 1 acceptance filter (RXF3).||255|
|Buffer 1 Acceptance Filter (RXF4)||Value for buffer 1 acceptance filter (RXF4).||255|
|Buffer 1 Acceptance Filter (RXF5)||Value for buffer 1 acceptance filter (RXF5).||255|
|Broker Address||The address of the MQTT broker.|
|Username||User name for MQTT broker to authenticate the client.|
|Password||Password for MQTT broker to authenticate the client.|
|Client ID||A unique identifier for the client that is connected to the MQTT broker.|
|Communication interface||The transport layer External mode uses to exchange data between the host computer and the target hardware||XCP on TCP/IP|
|Run external mode in a background||The option to force the External mode engine to run the generated code in a background task.||Not selected|
|Logging buffer size (in bytes)||The buffer size for logging data in Universal Measurement and Calibration Protocol (XCP)-based External mode.||1000000|
|Port||The port the External mode uses for communications between the hardware board and host computer.||17725|
|Verbose||Option to view the External Mode execution progress and updates in the Diagnostic Viewer or in the MATLAB Command Window||Not selected|