| Embedded IDE Link™ CC | |
| On this page… |
|---|
Use the options in the Select tree under Real-Time Workshop to perform the following configuration tasks.
Select your processor file.
Configure your build process.
Specify whether to use custom storage classes.
Selecting the system target (ccslink_grt.tlc or ccslink_ert.tlc) in System target file enables Embedded IDE Link CC configuration options in the Embedded IDE Link CC pane.
Clicking Browse opens the processor File Browser where you select ccslink_grt.tlc as your Real-Time Workshop System target file for Embedded IDE Link CC.
If you are using Real-Time Workshop Embedded Coder software or plan to use PIL, select the ccslink_ert.tlc processor in System target file.
Embedded IDE Link CC software does not use makefiles or the build process to generate code. Code generation is project based so the options in this group do not apply.
When you generate code from a model employing custom storage classes (CSC), make sure to clear Ignore custom storage classes. This setting is the default value for Embedded IDE Link CC and for Real-Time Workshop Embedded Coder.
When you select Ignore custom storage classes,
Objects with CSCs are treated as if you set their storage class attribute to Auto.
The storage class of signals that have CSCs does not appear on the signal line, even when you select Storage class from Format > Port/Signals Display in your Simulink menus.
Ignore custom storage classes lets you switch to a processor that does not support CSCs, such as the generic real-time processor (GRT), without having to reconfigure your parameter and signal objects.
The Generate code only option does not apply to processoring with Embedded IDE Link CC. To generate source code without building and executing the code on your processor, select TI C6000 runtime from the Category list in the Select tree. Then, under Runtime, select Generate code only for Build action. You cannot use DSP/BIOS features when you use the Generate code only option for the Build action.
Two options control HTML report generation during code generation.
After you generate code, this option tells the software whether to generate an HTML report that documents the C code generated from your model. When you select this option, Real-Time Workshop writes the code generation report files in the html subdirectory of the build directory. The top-level HTML report file is named modelname_codegen_rpt.html or subsystemname_codegen_rpt.html. For more information about the report, refer to the online help for Real-Time Workshop. You can also use the following command at the MATLAB prompt to get more information.
docsearch 'Create code generation report'
In the Navigation options, when you select Model-to-code and Code-to-model, your HTML report includes hyperlinks to various features in your Simulink model.
This option directs Real-Time Workshop to open a MATLAB Web browser window and display the code generation report. If you clear this option, you can open the code generation report (modelname_codegen_rpt.html or subsystemname_codegen_rpt.html) manually in a MATLAB Web browser window or in another Web browser.
Real-Time Workshop uses the processor Language Compiler (TLC) to generate C code from the model.rtw file. The TLC debugger helps you identify programming errors in your TLC code. Using the debugger, you can
View the TLC call stack.
Execute TLC code line-by-line and analyze and/or change variables in a specified block scope.
When you select Debug from the Select tree, you see the Debug options as shown in the next figure. In this dialog box, you set options that are specific to Real-Time Workshop process and TLC debugging.
For details about using the options in Debug, refer to About the TLC Debugger in your Real-Time Workshop processor Language Compiler documentation.
On the Optimization pane in the Configuration Parameters dialog box, you set options for the code that Real-Time Workshop generates during the build process. You use these options to tailor the generated code to your needs. Select Optimization from the Select tree on the Configuration Parameters dialog box. The figure shows the Optimization pane when you select the system target file ccslink_grt.tlc under Real-Time Workshop system target file.
These are the options typically selected for Real-Time Workshop:
Conditional input branch execution
Signal storage reuse
Enable local block outputs
Reuse block outputs
Eliminate superfluous local variables (Expression folding)
Loop unrolling threshold
Optimize initialization code for model reference
For more information about using these and the other Optimization options, refer to your Real-Time Workshop documentation.
On the select tree, the Embedded IDE Link CC entry provides options in these areas:
Runtime — Set options for run-time operations, like the build action
Project Options — Set build options for your project code generation
Code Generation — Configure your code generation requirements
Link Automation — Export a ticcs object to your MATLAB workspace
Before you are able to an executable to run on any Texas Instruments processor, you must configure the run-time options for the source model.
By selecting values for the options available, you configure the operation of your processor.
To specify to Real-Time Workshop software what to do when you click Build, select one of the following options. The actions are cumulative—each listed action adds features to the previous action on the list and includes all the previous features:
Generate_code_only — Directs Real-Time Workshop software to generate ANSI C code only from the model. It does not use the Texas Instruments software tools, such as the compiler and linker, and you do not need to have CCS installed. Also, MATLAB software does not create the connection to CCS that results from the other options. This option does not build code for TI processors. You cannot use this option when you set the system target file to either ccslink_grt.tlc or ccslink_ert.tlc.
The build process for a model also generates the files modelname.c, modelname.cmd, modelname.bld, and many others. It puts the files in a build directory named modelname_linkforccs_rtw in your MATLAB working directory. This file set contains many of the same files that Real-Time Workshop software generates to populate a CCS project when you choose Create_Project for the build action.
Create_Project — Directs Real-Time Workshop software to start CCS and populate a new project with the files from the build process. This option offers a convenient way to build projects in CCS.
Archive_library — Directs Real-Time Workshop software to archive the project for this model. Use this option when you plan to use the model in a model reference application. Model reference requires that you archive your CCS projects for models that you use in model referencing.
Build — Builds the executable COFF file, but does not download the file to the processor.
Build_and_execute — Directs Real-Time Workshop software to build, download, and run your generated code as an executable on your processor.
Create_processor_in_the_loop_project — Directs the Real-Time Workshop code generation process to create PIL algorithm object code as part of the project build.
Your selection for Build action determines what happens when you click Build or press Ctrl+B. Your selection tells Real-Time Workshop software when to stop the code generation and build process.
To run your model on the processor, select Build_and_execute. This selection is the default build action; Real-Time Workshop software automatically downloads and runs the model on your board.
Note When you build and execute a model on your processor, the Real-Time Workshop software build process resets the processor automatically. You do not need to reset the board before building models. |
To enable the overrun indicator, choose one of three ways for the processor to respond to an overrun condition in your model:
None — Ignore overruns encountered while running the model.
Print_message — When the DSP encounters an overrun condition, it prints a message to the standard output device, stdout.
Call_custom_function — Respond to overrun conditions by calling the custom function you identify in Interrupt overrun notification function.
When you select Call_custom_function from the Interrupt overrun notification method list, you enable this option. Enter the name of the function the processor should use to notify you that an overrun condition occurred. The function must exist in your code on the processor.
Embedded IDE Link CC includes software that generates interrupts in models that do not have ADC or DAC blocks, or that use multiple clock rates. In the following cases, the overrun indicator does not work:
In multirate systems where the rate in the model is not the same as the base clock rate for your model. In these cases, the timer in Embedded IDE Link CC provides the interrupts for setting the model rate.
In models that do not include ADC or DAC blocks, the timer in Embedded IDE Link CC provides the software interrupts that drive model processing.
Before you run your model as an executable on any processor, you must configure the Project options for the model.
To let you determine the degree of optimization provided by the TI optimizing compiler, you enter the optimization level to apply to files in your project. For details about the compiler options, refer to your CCS documentation. When you create new projects, Embedded IDE Link CC sets the optimization to Function(-o2).
Click Get From IDE to import the compiler option setting from the current project in the IDE. To reset the compiler option to the default value, click Reset.
To let you specify the options provided by the TI linker during link time, you enter the linker options as a string. For details about the linker options, refer to your CCS documentation. When you create new projects, Embedded IDE Link CC sets no linker options.
Click Get From IDE to import the linker options string from the current project in the IDE. To reset the linker options to the default value of no options, click Reset.
Enter the amount of memory to use for the stack. For more information, refer to Enable local block outputs on the Optimization pane of the Configuration Parameters dialog box. Block output buffers are placed on the stack until the stack memory is fully allocated. After that, the output buffers go in global memory. Also refer to the online Help system for more information about Real-Time Workshop options for configuring and building models and generating code.
From this category, you select options that define the way your code is generated:
Profile real-time task execution
Inline run-time library functions
To enable the real-time execution profile capability, select Profile real-time task execution. With this selected, the build process instruments your code to provide performance profiling at the task level. When you run your code, the executed code reports the profiling information in
To allow you to specify whether the functions generated from blocks in your model are used inline or by pointers, Inline run-time library functions tells the compiler to inline each Signal Processing blockset and Video and Imaging blockset function. Inlining functions can make your code run more efficiently (better optimized) at the expense of using more memory.
As shown in the following figure, the default setting uses inlining to optimize your generated code.
When you inline a block function, the compiler replaces each call to a block function with the equivalent function code from the static run-time library. If your model use the same block four times, your generated code contains four copies of the function.
While this redundancy uses more memory, inline functions run more quickly than calls to the functions outside the generated code.
When you use Real-Time Workshop to build a model to a C6000 processor, Embedded IDE Link CC makes a connection between MATLAB and CCS. If you have used Embedded IDE Link CC, you are familiar with function ticcs, which creates objects the reference between the IDE and MATLAB. This option refers to the same object, called cc in the function reference pages. Although MATLAB to CCS is a bridge to a specific instance of the CCS IDE, what it really is an object that contains information about the IDE instance it refers to, such as the board and processor it accesses. In this pane, the Export handle to MATLAB base workspace option lets you instruct Embedded IDE Link CC to export the object to your MATLAB workspace, giving it the name you assign in IDE link handle name.
Although CCS offers two standard project configurations, Release and Debug, models you build with Embedded IDE Link CC use a custom configuration that provides a third combination of build and optimization settings—custom.
Project configurations define sets of project build options. When you specify the build options at the project level, the options apply to all files in your project. For more information about the build options, refer to your TI CCS documentation.
The default settings for custom are the same as the Release project configuration in CCS, except for the compiler options discussed in the next section. custom uses different compiler optimization levels to preserve important features of the generated code.
When you create a new project or build a model to your TI C6000 hardware, your project and model inherit the build configuration settings from the configuration custom. The settings in custom differ from the settings in the default Release configuration in CCS in the compiler settings.
For the compiler options, custom uses the Function(-o2) compiler setting. The CCS default Release configuration uses File(-o3), a slightly more aggressive optimization model.
For memory configuration, where Release uses the default memory model that specifies near functions and data, custom specifies near functions and data—the -ml1 memory model—because some custom hardware might not support far data or aggregate data. Your CCS documentation provides complete details on the compiler build options.
You can change the individual settings or the build configuration within CCS. Build configuration options that do not appear on these panes default to match the settings for the Release build configuration in CCS.
| Setting Real-Time Workshop Software Parameters for TI Processors | processor Function Library and Embedded IDE Link CC | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |