The TDP Editor is made up of four main sections:
A Navigation Tree: Use the navigation tree on the left to select customization points.
A Help Window: Provides direct reference information for the selected customization point.
An Edit Window: The format of the Edit Window depends on the nature of the customization point.
A Comment Window: Lets you to enter a personal comment for each customization point.
In the Navigation Tree, you can click on any customization point to obtained detailed reference information for that parameter in the Help Window.
The Navigation Tree covers all the customization points of the TDP. There are four main sections:
Basic Settings: This section specifies default file extensions, default compilation and link flags, environment variables and custom variables required for your target environment. This section allows you to set all the common settings and variables used by OneTest Embedded and the different sections of the TDP. For example, the name and location of the cross compiler for your target is stored in a Basic Settings variable, which is used throughout the compilation, preprocessing and link functions. If the compiler changes, you only need to update this variable in the Basic Settings section.
Build Settings: This section configures the functions required by the OneTest Embedded GUI integrated build process. It defines compilation, link and execution Perl scripts, plus any user-defined scripts when needed. This section is the core of the TDP, as it drives all the actions needed to compile and execute a piece of code on the target.
Library Settings: This section describes a set of source code files as well as a dedicated customization file (custom.h), which adapt the TDP to target platform requirements. This section is definitively the most complex and usually only requires customization for specialized platform TDPs (unknown RTOS, no RTOS, unknown simulator, emulator, etc.)
Parser Settings: This section modifies the behavior of the parser in order to address non-standard compiler extensions, such as for example, non-ANSI extensions. This section allows OneTest Embedded to properly parse your source code, either for instrumentation or code generation purposes.
On the right hand side of the TDP Editor window, the embedded Help provides contextual reference information for the part of the TDP that is selected in the tree-view pane.
To Edit the new TDP:
Use the TDP Editor's tree pane to navigate through the customization points of the TDP, and make the following changes:
Under Basic Settings: Change the ENV_PATH and STD_INCLUDE customization points in both the For C and For C++ nodes. ENV_PATH updates the PATH environment variable in order to invoke the gcc compiler directly. STD_INCLUDE specifies the location of the standard GCC libraries. For example:
Note When you change a customization point in the TDP Editor, it is generally a good idea to add a note in the Comment box. This makes later modification and TDP sharing much easier.
In the same manner, check all the other Basic Settings customization points to ensure that they reflect the correct paths and filenames used with the MinGW distribution.
Build Settings: No changes should be required here, but
have a look at the Compilation Function.
Locate the corresponding Perl script and have a look at the Help window to understand how the atl_cc routine works.
Next, look at the Link Function to understand the alt_link Perl routine.
Note All the parameters used by these Perl routines are set in the Basic Settings section of the TDP.
Under Library Settings: No changes are required at this point.
Under Parser Settings: In this section, you must tell the Test RealTime code parser where the std GCC libraries are located. Do this as required for each of the features that you plan to use with this TDP.
Save the TDP.
Any changes made to the Basic Settings section of a TDP are read from the OneTest Embedded GUI and applied to the project. For this reason, whenever you modify the Basic Settings of a TDP that is currently used in a OneTest Embedded project, you must reload the TDP into the project.
To reload the TDP in OneTest Embedded:
In the From the Project menu, select Configurations.
Select the TDP and click Remove.
Click New, select the TDP and click OK.
You have created your first TDP. The next step is to validate the new TDP in OneTest Embedded.
Move on the next section: Validating a New TDP