Before using IBM Rational Test RealTime as a Rose RealTime plug-in, you must first open or create a model within Rose RealTime.
Test RealTime can perform Source Code Insertion (SCI) instrumentation on several components.
Note If you installed Rose RealTime after Test RealTime, you must manually install the plug-in. Please refer to the IBM Rational Test RealTime Installation Guide for further information.
To activate Runtime Analysis tools:
From Rose RealTime, open the Component Specification of the components that you want to observe and select the C++ TestRT tab.
Add Target Deployment Port Object Files: Disable this option if the Test RealTime TDP is already included in the application or if you have multiple definitions of the Test RealTime symbols.
Enable the option if you want to link the selected Rose RealTime component with the TDP. This is required when producing an executable. For a library component, this depends on whatever components are linked to the library.
This option also adds a new version of cmdCommand.obj to the object file list if such a file exists in <InstallDir>\bin\intel\RoseRT\<TDP>, where <InstallDir> is the Test RealTime installation directory and <TDP> is the name of the current TDP. This object file dumps SCI traces when the user clicks on the Stop button in Rose RealTime.
Compile Runtime using Target Deployment Port: Enable this option if the TDP runtime must be compiled using the TDP > Build settings > Compilation function. Disable this option to compile the TDP using the makefile rules of all other generated source code.
Enable Component Instrumentation: Select this option to enable instrumentation of the component for runtime analysis features. If this option is cleared, runtime analysis features are not available.
Coverage: Select the code coverage type. See Coverage types for more information.
Enable Memory Profiling, Enable Performance Profiling and Enable Runtime Tracing: Select the runtime analysis tools that you want to activate for the current component.
Additional Options: Add any other command line options for the Instrumentation Launcher (attolcc). For example, you can use the -notdp option to avoid generating env_attolcc.pl. Refer to C and C++ Instrumentation Launcher - attolcc for details on command line options.
Support Multi-threaded Code Generation: Select this option if the application is multi-threaded.
Output Trace File Name: If your embedded application has no direct access to the host machine, you can set the file path and name of the result file for the view result menu. By default, <model directory>\atlout.spt is used.
Override TDP directory: Select this option if your TDPs are not located in the Test RealTime installation directory.
TDP Directory: If the Override TDP directory option is selected, specify the path to the targets directory where the TDP was generated by the TDP Editor.
Create static file directory: Select this option to create a directory for static files if it does not already exist.
Path to static file directory: Specify the directory where .fdc and .tsf files will be written during the instrumentation. The default location is <model directory>\Cov.
Use One fdc per source: Select this option if you want the only one .fdc or .tsf file with multiple sections for each C or C++ instrumented source file. This option uses more space disk but only one file per source file.
Temp directory: Specify whether you want to store temporary .i and _aug.cpp files in a directory. If empty, temporary files are removed after instrumentation. The temporary directory also stores products.h and env_attolcc.pl.
Click OK. The changes do not immediately affect the build and the CompilationMakeInsert function.
In Rose RealTime, from the Tools menu, select Rational Test RealTime > Refresh Instrumentation to update the build and CompilationMakeInsert function. You must repeat this operation whenever you change any of the options described above.
To run a build with the runtime analysis tools:
In Rose RealTime, click the Build Component button, or from the Build menu, select Build or Rebuild.
These commands generate the code and makefile, and launch the product instrumentation with the selected options.
To run the instrumented binary:
Just like a standard Rose RealTime application, from the Build menu, select Run or click the Run button.
Then, click Start and, when appropriate, Stop.
Related Topics
Generating Trace Dumps | Collecting Trace Dump Data in Rose RealTime