Embedded IDE Link™ TS

Embedded IDE Link TS Pane

Embedded IDE Link TS Pane Overview

Parameters for controlling Embedded IDE Link TS build configuration, export handles, and processor-in-the-loop verification.

Configuration

This pane appears if you add the Embedded IDE Link TS configuration options to a model with any system target file. To do this, select the menu item Tools > Embedded IDE Link TS > Add Embedded IDE Link TS Configuration to Model.

See Also

Working with Configuration Sets

Back to Top

Build Action

Set what action to take after the Real-Time Workshop build process completes. You can create application and library projects in the TASKING EDE and then stop, or you can also choose to build, execute, or debug.

Settings

Default: Create Application Project

Create Application Project

Generate code for the model or subsystem, create a TASKING application project for the selected TASKING configuration, connect to the TASKING EDE, and open the application project (in addition to the required Real-Time Workshop and Signal Processing Blockset Library projects, if required) in the TASKING EDE. This option does not build or execute the application.

Create Library Project

Performs the same actions as Create Application Project, but this option archives the generated code into a library in TASKING. No main.c file is generated.

Create and Build Application Project

Performs the same actions as Create Application Project, but also instructs TASKING to build the application project.

Create and Build Library Project

Performs the same actions as Create Library Project, but also instructs TASKING to build the Library project.

Create, Build and Execute Application Project

Performs the same actions as Create and Build Application Project and also downloads the executable file to your CrossView Target and runs the executable. No debugging information is downloaded into the target with this option.

Create, Build and Debug Application Project

Performs the same actions as Create, Build and Execute Application Project but also downloads debugging information to the target. This option behaves the same way as the Debug Application icon in the TASKING EDE.

Tip

To manually debug the executable from the application project, use the Create and Build Application Project option, then click the Debug Application icon in the TASKING EDE

Dependency

This parameter is disabled by Configure model to build PIL algorithm object code.

Command-Line Information

Recommended Settings

See Also

Setting Build Action

Back to Top

Target Preference Configuration

Select a configuration description, as defined in the Target Preferences, to be used by the build action.

Settings

Default: 'Target Preference Configuration Not Set'

After you have set up target preferences for particular configurations, you can select them here (e.g., 'c166'). The names in the list correspond to the Configuration Description for each configuration in the Embedded IDE Link TS Target Preferences dialog box. Click Edit Configuration to open the Target Preferences dialog box for the currently selected configuration. For instructions, see Using Configuration Sets to Specify Your Target.

Command-Line Information

See Also

• Using Configuration Sets to Specify Your Target

• Setting Target Preferences

Back to Top

Add build directory suffix

Specify whether to add a model-specific suffix to the regular Real-Time Workshop build directory suffix.

Settings

Default: Off

On

Specify a model-specific suffix to be added the regular Real-Time Workshop build directory suffix. This setting is useful to avoid "shared utility function" code generation errors which occur because of conflicts over Real-Time Workshop utility functions shared between different models. A typical conflict is between with models with floating-point number support and those without. To resolve this conflict, you can add an 'fp' suffix for floating-point models, and an 'int' suffix for non-floating-point models.

Off

Use the default Real-Time Workshop build directory suffix — not using an additional suffix may result in rebuilding shared libraries unnecessarily.

Dependencies

This parameter enables Build directory suffix.

Command-Line Information

Recommended Settings

See Also

Shared Libraries

Back to Top

Build directory suffix

Specify a model-specific suffix to be added the regular Real-Time Workshop build directory suffix.

Settings

No Default

Enter a model-specific suffix to be added the build directory name. This setting is useful to avoid "shared utility function" code generation errors which occur because of conflicts over Real-Time Workshop utility functions shared between different models.

Dependencies

This parameter is enabled by Add build directory suffix.

Command-Line Information

See Also

Shared Libraries

Back to Top

Export EDE handle to MATLAB base workspace

Specify whether to export the EDE object handle to the workspace.

Settings

Default: On

On

Export a TASKING EDE object handle to the MATLAB base workspace after the build process completes.

Off

Do not export the EDE object handle to the workspace.

Dependencies

This parameter enables EDE handle name.

Command-Line Information

See Also

Automation Interface

Back to Top

EDE handle name

Specify a name for the exported handle.

Settings

Default: 'EDE_Obj'

Specify the MATLAB base workspace variable name to export the handle to.

Dependencies

This parameter is enabled by Export EDE handle to MATLAB base workspace.

Command-Line Information

See Also

Automation Interface

Back to Top

Export CrossView Pro handle to MATLAB base workspace

Specify whether to export the CrossView Pro object handle to the workspace.

Settings

Default: On

On

Export the TASKING CrossView Pro object handle to the MATLAB base workspace after the build process completes.

The handle is only exported if the build action launches CrossView Pro.

Off

Do not export the CrossView Pro object handle to the workspace.

Dependencies

This parameter enables CrossView Pro handle name.

Command-Line Information

See Also

Automation Interface

Back to Top

CrossView Pro handle name

Specify a name for the exported handle.

Settings

Default: 'XView_Obj'

Specify the MATLAB base workspace variable name to export the handle to.

Dependency

This parameter is enabled by Export CrossView Pro handle to MATLAB base workspace.

Command-Line Information

See Also

Automation Interface

Back to Top

Configure model to build PIL algorithm object code

Specify whether to build Processor-in-the-Loop (PIL) algorithm code.

Settings

Default: Off

On

Configure the model to build PIL algorithm code that is suitable for use with the PIL block.

Off

Do not build PIL algorithm code.

Dependency

This parameter enables PIL block action.

This parameter disables Build action.

See Also

Processor-in-the-Loop (PIL) Cosimulation

Back to Top

PIL block action

Select a PIL block action to take after the Real-Time Workshop build process completes

Settings

Default: 'None'

'None'

Do not create a PIL block. Choose this to avoid creating a PIL block, for instance if you have already built a PIL block and do not want to repeat the action.

'Create PIL block, then build and download PIL application'

Create the PIL block, then automatically build and download the PIL application. This is the default when you select the option to configure the model for PIL.

'Create PIL block'

Create the PIL block, and then stop without building. You can build manually from the PIL block.

Dependency

This parameter is enabled by Configure model to build PIL algorithm object code. When enabled, the default changes to 'Create PIL block, then build and download PIL application'.

Command-Line Information

See Also

Processor-in-the-Loop (PIL) Cosimulation

Back to Top

Configuration Parameters

Limitations and Tips