Embedded IDE Link™ TS

Issues Using Real-Time Workshop^® Software Without Real-Time Workshop^® Embedded Coder™ Software

Real-Time Workshop^® grt.tlc-Based Targets Not Supported for PIL

Real-Time Workshop^® "grt.tlc"-based targets are not supported for PIL.

To resolve this issue, use a Real-Time Workshop "ert.tlc"-based target.

Back to Top

"Save data to workspace" Causes Error

Simulink^® scope blocks with the "Save data to workspace" option checked cause a link error when building with GRT. This error occurs because this setting causes GRT to log data to a MAT-file during execution. However, MAT-file logging is not supported by Embedded IDE Link™ TS software.

When using ERT, Embedded IDE Link TS software makes sure the MAT-file logging configuration set option under Real-Time Workshop > Interface is not checked, and therefore this error is avoided.

Back to Top

DSP563xx Toolset Support Limitations

Only 16-bit mode for the DSP563xx Family is supported. Real-Time Workshop grt.tlc-based targets and the "GRT Compatible Call interface" option in the Real-Time Workshop Interface settings are not supported. This limitation is because of the nonstandard size of single- and double-precision floating-point datatypes on this architecture (tmwtypes.h does not compile).

You must use 16–bit mode.

Back to Top

Use ERT Target for Memory-Constrained Targets

Some targets such as the TASKING TriCore^® 1766B have memory constraints that can cause errors if you use the GRT target.

The 1766b has no external memory. You should use ERT rather than GRT when targeting this board, due to memory resource constraints. If you use the GRT target you may see compilation errors similar to the following example:

ltc E117: conflicting restriction for sections ".text.libc" and
".text.trapvec.000": absolute restrictions overlap

This problem occurs because the ERT (embedded real time) target is optimized for size and speed, while the GRT (generic real time) target is designed for ease of prototyping which incurs extra memory usage.

Use the ERT target for memory-constrained targets such as the TASKING TriCore 1766B.

See also Linker Errors Due to Limited Memory.

Back to Top

8051 GRT Limitations

Working with the 8051 has some limitations when using GRT.

CrossView Pro Parameters

GRT application builds link against an example main (grt_main.c) file which includes a main function with argc and argv parameters for handling command-line arguments. When executing the application in CrossView Pro, these parameters are uninitialized and application execution terminates early. This behavior differs from that of other toolsets, where these parameters are initialized to 0 (argc) and the null pointer (argv).

To work around this issue on 8051, you can manually set argc to 0 in CrossView Pro before beginning execution.

Alternatively, you can create a library project for algorithm export that does not link against grt_main.c — see Setting Build Action for more detail.

Signal Processing Blockset™ Software

The Signal Processing Blockset™ library fails to build for GRT models with the 8051 toolset. Certain datatypes required by the Signal Processing Blockset software, for example, real64_T, are not defined by Real-Time Workshop software for this configuration.

Use a Real-Time Workshop^® Embedded Coder™, ERT-based target, rather than a GRT-based target.

Back to Top

Processor-in-the-Loop Issues