After a TDP has been created or modified, the first step is to validate that it works correctly on the target.
The first step is to change the TDP used by your project.
To make sure that your TDP is working properly, you must create a Component Testing test node and run it with all the relevant Runtime Analysis tools enabled. Once the following steps are covered, you can consider that your TDP is fully functional:
Create a new Configuration OneTest Embedded
Apply the new Configuration to a project
Validate the compilation sequence with the new Configuration
In OneTest Embedded, the TDP is part of a Configuration. Each Configuration is based on a TDP, plus the particular Configuration Settings that are specific for each node of the project.
This means that you can base several slightly different Configurations on a single TDP.
To create a new Configuration in Test RealTime:
In OneTest Embedded, open the add.rtp example project.
This example project provides a series of test nodes for demonstration of Test RealTime features. For this tutorial, concentrate on the add test node, which contains a simple add.c source file as well as the corresponding add.ptu test script.
From the Project menu, select Configurations. Click New.
In the New Configuration box, enter a name for the new Configuration, and select the TDP on which it shall be based.
For our example, select your newly created MinGW TDP. Notice that two items appear in the list, one for C, another for C++ followed by the same name. Select the C version of the TDP
Click OK, Close and save the project. Update the TDP in the project.
Now that the new Configuration has been created, based on your TDP, you need to select it for use in your project.
Although a project can use multiple Configurations, as well as multiple TDPs, there must always be at least one active Configuration.
TDP is used when selected from the Build combo-box, but remember that you have to be consistent between the TDP programming language selection and the source files used within your test environment.
To change the current Configuration of a project:
From the Build toolbar, select the Configuration you wish to use in the Configuration box.
Update any project settings if necessary.
In order to validate the compilation sequence, the idea is to successfully compile the current project with the new Configuration.
To validate the compilation procedure:
In the Project Explorer, select a single source file.
From the Build toolbar, click the Build Options button and clear all Runtime Analysis features (Memory Profiling, Performance Profiling, Code Coverage and Runtime Tracing) to ensure that these do not affect the build sequence.
Select the add.c source file.
From the Build toolbar, click Build .
The compilation should end with a Passed status. If not, restart the TDP Editor and change the atl_cc Perl procedure accordingly.
You can repeat the same action for the following Perl procedures:
atl_cpp: Preprocessing routine for Source Code Insertion
atl_link: Link routine
atl_exec: Execution routine
atl_execdbg: Debugging routine
The compilation procedure is validated. You can now consider using the Test and Runtime Analysis features of Test RealTime on your project.
The next section provides help about debugging any compilation issues you may have encountered.
Move on the next section: Debugging a TDP