Real-Time Workshop Pane: Tornado Target :: Configuration Parameters for Simulink Models (Real-Time Workshop®)

Real-Time Workshop Pane: Tornado Target

The Real-Time Workshop Tornado Target pane includes the following parameters when the Real-Time Workshop product is installed on your system and you specify the tornado.tlc system target file.

On this page…
Real-Time Workshop: Tornado Target Tab Overview Target function library Utility function generation MAT-file logging MAT-file variable name modifier Code Format StethoScope Download to VxWorks target Base task priority Task stack size External mode Transport layer MEX-file arguments Static memory allocation Static memory buffer size

On this page…

Real-Time Workshop: Tornado Target Tab Overview

Target function library

Utility function generation

MAT-file logging

MAT-file variable name modifier

Code Format

StethoScope

Download to VxWorks target

Static memory allocation

Static memory buffer size

Real-Time Workshop: Tornado Target Tab Overview

Control Real-Time Workshop generated code for the Tornado Target.

Configuration

This tab appears only if you specify tornado.tlc as the System target file.

Target function library

Specify a target-specific math library for your model.

Settings

Default: C89/C90 (ANSI)

C89/C90 (ANSI): Generates calls to the ISO/IEC 9899:1990 C standard math library for floating-point functions.
C99 (ISO): Generates calls to the ISO/IEC 9899:1999 C standard math library.
GNU99 (GNU): Generates calls to the GNU gcc math library, which provides C99 extensions as defined by compiler option -std=gnu99.

Tip

Before setting this parameter, verify that your compiler supports the library you want to use. If you select a parameter value that your compiler does not support, compiler errors can occur.

Command-Line Information

Parameter: GenFloatMathFcnCalls

Type: string

Value: 'ANSI_C' | 'C99 (ISO)' | 'GNU99 (GNU)'

Default: 'ANSI_C'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	Any valid library
Safety precaution	No impact

Utility function generation

Specify the location for generating utility functions.

Settings

Default: Auto

Auto

Operates as follows:

When the model contains Model blocks, place utilities within the slprj/target/_sharedutils directory.
When the model does not contain Model blocks, place utilities in the build directory (generally, in model.c or model.cpp).

Shared location

Directs code for utilities to be placed within the slprj directory in your working directory.

Command-Line Information

Parameter: UtilityFuncGeneration

Type: string

Value: 'Auto' | 'Shared location'

Default: 'Auto'

Recommended Settings

Application	Setting
Debugging	`Shared location`
Traceability	`Shared location`
Efficiency	`Shared location`
Safety precaution	No impact

MAT-file logging

Specify whether to enable MAT-file logging.

Settings

Default: off

On

Enables MAT-file logging. When you select this option, the generated code saves to MAT-files any data specified in the Configuration Parameters > Data Import/Export Pane > Save to workspace subpane, and the data specified by any To Workspace blocks. See Data Import/Export Pane and To Workspace. In simulation, this data would be written to the MATLAB workspace, as described in Exporting Data to the MATLAB Workspace, but setting MAT-file logging redirects the data to a MAT-file instead. The file is named model.mat, where model is the name of your model.

Off

Disables MAT-file logging. Clearing this option has the following benefits:

Eliminates overhead associated with supporting a file system, which typically is not needed for embedded applications
Eliminates extra code and memory usage required to initialize, update, and clean up logging variables
Under certain conditions, eliminates code and storage associated with root output ports
Omits the comparison between the current time and stop time in the model_step, allowing the generated program to run indefinitely, regardless of the stop time setting

Dependencies

This parameter only appears for ERT-based targets and the Tornado target.

Limitation

MAT-file logging does not work in a referenced model, and no code is generated to implement it.

Command-Line Information

Parameter: MatFileLogging

Type: string

Value: 'on' | 'off'

Default: 'off'

Recommended Settings

Application	Setting
Debugging	On
Traceability	No impact
Efficiency	Off
Safety precaution	Off

MAT-file variable name modifier

Select the string to add to the MAT-file variable names.

Settings

Default: rt_

rt_: Adds a prefix string.
_rt: Adds a suffix string.
none: Does not add a string.

Dependency

When an ERT target is selected, this parameter is enabled by MAT-file logging.

Command-Line Information

Parameter: LogVarNameModifier

Type: string

Value: 'none' | 'rt_' | '_rt'

Default: 'rt_'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	No impact

Code Format

Specify the code generation format.

Settings

Default: RealTime

RealTime: Specifies the Real-Time code generation format.
RealTimeMalloc: Specifies the Real-Time Malloc code generation format.

Command-Line Information

Parameter: CodeFormat

Type: string

Value: 'RealTime' | 'RealTimeMalloc'

Default: 'RealTime'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	No impact

StethoScope

Specify whether to enable StethoScope, an optional data acquisition and data monitoring tool.

Settings

Default: off

On: Enables StethoScope.
Off: Disables StethoScope.

Tips

You can optionally monitor and change the parameters of the executing real-time program using either StethoScope or Simulink external mode, but not both with the same compiled image.

Dependencies

Enabling StethoScope automatically disables External mode, and vice versa.

Command-Line Information

Parameter: StethoScope

Type: string

Value: 'on' | 'off'

Default: 'off'

Recommended Settings

Application	Setting
Debugging	On
Traceability	No impact
Efficiency	Off
Safety precaution	Off

Download to VxWorks target

Specify whether to automatically download the generated program to the VxWorks target.

Settings

Default: off

On: Automatically downloads the generated program to VxWorks after each build.
Off: Does not automatically download to VxWorks, you must downloaded generated programs manually.

Tips

Automatic download requires specifying the target name and host name in the makefile, as described in Configuring for Automatic Downloading.
Before every build, reset VxWorks by pressing Ctrl+X on the host console or power-cycling the VxWorks chassis. This ensures that no dangling processes or stale data exist in VxWorks when the automatic download occurs.

Command-Line Information

Parameter: DownloadToVxWorks

Type: string

Value: 'on' | 'off'

Default: 'off'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	Off

Base task priority

Specify the priority with which the base rate task for the model is to be spawned.

Settings

Default: 30

Tips

For a multirate, multitasking model, the Real-Time Workshop software increments the priority of each subrate task by one.
The value you specify for this option will be overridden by a base priority specified in a call to the rt_main() function spawned as a task.

Command-Line Information

Parameter: BasePriority

Type: integer

Value: any valid value

Default: 30

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	May affect efficiency, depending on other task's priorities
Safety precaution	No impact

Task stack size

Stack size in bytes for each task that executes the model.

Settings

Default: 16384

Command-Line Information

Parameter: TaskStackSize

Type: integer

Value: any valid value

Default: 16384

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	Larger stack may waste space
Safety precaution	Larger stack reduces the possibility of overflow

External mode

Specify whether to enable communication between the Simulink model and an application based on a client/server architecture.

Settings

Default: on

On: Enables external mode. The client (Simulink model) transmits messages requesting the server (application) to accept parameter changes or to upload signal data. The server responds by executing the request.
Off: Disables external mode.

Dependencies

Selecting this parameter enables:

Transport layer
MEX-file arguments
Static memory allocation

Command-Line Information

Parameter: ExtMode

Type: string

Value: 'on' | 'off'

Default: 'on'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	No impact

Transport layer

Specify the transport protocol for external mode communications.

Settings

Default: tcpip

tcpip: Applies a TCP/IP transport mechanism. The MEX-file name is ext_comm.

Tip

The MEX-file name displayed next to Transport layer cannot be edited in the Configuration Parameters dialog box. For targets provided by The MathWorks, the value is specified in matlabroot/toolbox/simulink/simulink/extmode_transports.m.

Dependency

This parameter is enabled by External Mode.

Command-Line Information

Parameter: ExtModeTransport

Type: integer

Value: 0 | 1

Default: 0

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	No impact

MEX-file arguments

Specify arguments to pass to an external mode interface MEX-file for communicating with executing targets.

Settings

Default: ""

For TCP/IP interfaces, ext_comm allows three optional arguments:

Network name of your target (for example, 'myPuter' or '148.27.151.12')
Verbosity level (0 for no information or 1 for detailed information)
TCP/IP server port number (an integer value between 256 and 65535, with a default of 17725)

Dependency

This parameter is enabled by External Mode.

Command-Line Information

Parameter: ExtModeMexArgs

Type: string

Value: any valid arguments

Default: ""

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	No impact

Static memory allocation

Control the memory buffer for external mode communication.

Settings

Default: off

On: Enables the Static memory buffer size parameter for allocating allocate dynamic memory.
Off: Uses a static memory buffer for external mode instead of allocating dynamic memory (calls to malloc).

Tip

To determine how much memory you need to allocate, select verbose mode on the target to display the amount of memory it tries to allocate and the amount of memory available.

Dependencies

This parameter is enabled by External Mode.
This parameter enables Static memory buffer size.

Command-Line Information

Parameter: ExtModeStaticAlloc

Type: string

Value: 'on' | 'off'

Default: 'off'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	No impact

Static memory buffer size

Specify the memory buffer size for external mode communication.

Settings

Default: 1000000

Enter the number of bytes to preallocate for external mode communications buffers in the target.

Tips

If you enter too small a value for your application, external mode issues an out-of-memory error.
To determine how much memory you need to allocate, select verbose mode on the target to display the amount of memory it tries to allocate and the amount of memory available.

Dependency

This parameter is enabled by Static memory allocation.

Command-Line Information

Parameter: ExtModeStaticAllocSize

Type: integer

Value: any valid value

Default: 1000000

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	No impact

Related Products & Applications

Get Simulink trial software

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

Get this Simulink Kit