|
adagnat.xdp
|
Ada - Ada83
|
Component Testing - Code Coverage
|
Sun Solaris 2.8 - Linux RedHat 7.2
|
GNAT 3.11p - GNAT 3.13p
|
GNAT Make Program 3.11p - GNAT Make Program 3.13p
|
GDB gnat.3.11p - GDB gnat.3.13p
|
Native
|
Native
|
For v7.1
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.44.4.8 $
-------------------------------------------------------------------------------
This is the Target Deployment Port for UNIX/Linux native GNAT.
- For Instructions on configuring this TDP,
please refer to the 'README.GNAT' node.
-------------------------------------------------------------------------------
Support:
-------
Language : Ada - Ada83
Features : Component Testing - Code Coverage
Tested Against:
------------
Host Machine : Sun Solaris 2.8 - Linux RedHat 7.2
Compiler : GNAT Compiler 3.11p - GNAT Compiler 3.13p
Linker : GNAT Make Program 3.11p - GNAT Make Program 3.13p
Debugger : GDB gnat.3.11p - GDB gnat.3.13p
OS : Native
Target : Native
|
|
adalinuxapex.xdp
|
Ada - Ada83
|
Component Testing - Code Coverage
|
Linux RedHat 8.0
|
Rational Apex 4.2.0 - Rational Apex 4.0.0
|
Rational Apex 4.2.0 - Rational Apex 4.0.0
|
Rational Apex 4.2.0 - Rational Apex 4.0.0
|
Native
|
Native
|
For v2003.06.13 Release
$Revision: 1.22.4.2 $
Support:
-------
Language : Ada - Ada83
Features : Component Testing - Code Coverage
Tested Against:
------------
Host Machine : Linux RedHat 8.0
Compiler : Rational Apex 4.2.0 - Rational Apex 4.0.0
Linker : Rational Apex 4.2.0 - Rational Apex 4.0.0
Debugger : Rational Apex 4.2.0 - Rational Apex 4.0.0
OS : Native
Target : Native
-------------------------------------------------------------------------------
This is the Target Deployment Port for Linux native Apex 4.x.
- This version has been validated on the Linux/Intel platform.
- It should be usable on other Apex UNIX or Linux native platforms, after making any needed
platform-specific changes in the TDP's Types and Constant definitions ('Library Settings' nodes),
and Standard and System specifications ('Parser Settings' nodes).
- The same applies to Apex cross platforms, for which additional changes may be needed in the TDP's
Execution and Debug mode functions ('Build Settings' nodes) to take into account target-specific
executable download and report upload procedures.
- For Instructions on configuring and using the Apex/TestRealTime integration after installing this TDP,
please refer to the 'README.Apex' node.
-------------------------------------------------------------------------------
|
|
adapcgnt.xdp
|
Ada95 - Ada83
|
Component Testing - Code Coverage
|
Windows
|
GNAT 3.11p - GNAT 3.14p - GNAT 5.03
|
GNAT Make Program 3.11p - GNAT Make Program 3.14p - GNAT Compiler 5.03
|
GDB version 4.16.gnat.3.11p - GDB version 4.17.gnat.3.14p - GNAT Compiler 5.03
|
Native
|
Native
|
For v7.5 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.58.4.15 $
-----------------------------------------------------------------------------------------------------------------------
This is the Target Deployment Port for windows native GNAT.
- For Instructions on configuring this TDP,
please refer to the 'README.GNAT' node.
-----------------------------------------------------------------------------------------------------------------------
Support:
-------------
Language : Ada95 - Ada83
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : GNAT Compiler 3.11p - GNAT Compiler 3.14p - GNAT Compiler 5.03
Linker : GNAT Make Program 3.11p - GNAT Make Program 3.14p - GNAT Compiler 5.03
Debugger : GDB version 4.16.gnat.3.11p - GDB version 4.17.gnat.3.14p - GNAT Compiler 5.03
OS : Native
Target : Native
|
|
adapcgnt_c_stream.xdp
|
Ada95 - Ada83
|
Component Testing - Code Coverage
|
Windows
|
GNAT 3.11p - GNAT 3.14p - GNAT 5.03
|
GNAT Make Program 3.11p - GNAT Make Program 3.14p - GNAT Compiler 5.03
|
GDB version 4.16.gnat.3.11p - GDB version 4.17.gnat.3.14p - GNAT Compiler 5.03
|
Native
|
Native
|
For v7.5 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.1.2.2 $
-----------------------------------------------------------------------------------------------------------------------
This is the Target Deployment Port for windows native GNAT.
- For Instructions on configuring this TDP,
please refer to the 'README.GNAT' node.
-----------------------------------------------------------------------------------------------------------------------
Support:
-------------
Language : Ada95 - Ada83
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : GNAT Compiler 3.11p - GNAT Compiler 3.14p - GNAT Compiler 5.03
Linker : GNAT Make Program 3.11p - GNAT Make Program 3.14p - GNAT Compiler 5.03
Debugger : GDB version 4.16.gnat.3.11p - GDB version 4.17.gnat.3.14p - GNAT Compiler 5.03
OS : Native
Target : Native
Uses Interfaces.C_Streams instead of Text.Io
=======================================
Modified sections:
Library Settings > with clauses for package specification
Library Settings > Data types > priv_file
Library Settings > User-defined function specifications
Library Settings > Function bodies > with clauses for package body
Library Settings > Function bodies > Open function
Library Settings > Function bodies > Write function
Library Settings > Function bodies > Close function
|
|
adaunxapex.xdp
|
Ada - Ada83
|
Component Testing - Code Coverage
|
Sun Solaris 2.8
|
Rational Apex 4.2.0 - Rational Apex 4.0.0
|
Rational Apex 4.2.0 - Rational Apex 4.0.0
|
Rational Apex 4.2.0 - Rational Apex 4.0.0
|
Native
|
Native
|
For v2003.06.13 Release
$Revision: 1.42.4.2 $
Support:
-------
Language : Ada - Ada83
Features : Component Testing - Code Coverage
Tested Against:
------------
Host Machine : Sun Solaris 2.8
Compiler : Rational Apex 4.2.0 - Rational Apex 4.0.0
Linker : Rational Apex 4.2.0 - Rational Apex 4.0.0
Debugger : Rational Apex 4.2.0 - Rational Apex 4.0.0
OS : Native
Target : Native
-------------------------------------------------------------------------------
This is the Target Deployment Port for UNIX native Apex 4.x.
- This version has been validated on the Solaris platform.
- It should be usable on other Apex UNIX native platforms, after making any needed platform-specific
changes in the TDP's Types and Constant definitions ('Library Settings' nodes), and Standard and
System specifications ('Parser Settings' nodes).
- The same applies to Apex cross platforms, for which additional changes may be needed in the TDP's
Execution and Debug mode functions ('Build Settings' nodes) to take into account target-specific
executable download and report upload procedures.
- For Instructions on configuring and using the Apex/TestRealTime integration after installing this TDP,
please refer to the 'README.Apex' node.
-------------------------------------------------------------------------------
|
|
adawinapex.xdp
|
Ada - Ada83
|
Component Testing - Code Coverage
|
Windows 2000
|
Rational Apex Ada 4.0.0 - Rational Apex Ada 4.2.0
|
Rational Apex Ada 4.0.0 - Rational Apex Ada 4.2.0
|
Rational Apex Ada 4.0.0 - Rational Apex Ada 4.2.0
|
Native
|
Native
|
For v2003.06.13 Release
$Revision: 1.42.4.2 $
Support:
-------------
Language : Ada - Ada83
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Rational Apex Ada 4.0.0 - Rational Apex Ada 4.2.0
Linker : Rational Apex Ada 4.0.0 - Rational Apex Ada 4.2.0
Debugger : Rational Apex Ada 4.0.0 - Rational Apex Ada 4.2.0
OS : Native
Target : Native
1 - Setup of the Apex GUI/TestRT integration
(needs product administrator permissions on Apex and TestRT installations)
- add the path of the Apex TDP's cmd directory to the Apex
%APEX_MENUS_PATH%
(so that Apex may find the ada_menus and ada_rules file in this directory).
2 - Setup of Test RealTime runtime and model views
(needs product administrator permissions on Apex installation)
Before creating test views with Apex, the appropriate set(s) of Test RealTime
runtime and model views should be setup, based on the model(s) of the Apex
views containing the units to test.
- This may be done using the 'testrtbuild' script provided with the TDP, using
the '-model' option to designate the base model from which the runtime view
should be built, and the new model (which includes an import of the runtime
view) generated.
- This may also be done by selecting in an Apex directory viewer a user view
with the appropriate base model, and using the 'TestRT> Maintenance> Build Test
runtime and model views' menu item.
3 - Component Testing / Code Coverage / Trace
- Select in the Apex directory browser the tower of views containing the units to
test.
This may be done by explicit selection of a (single) view or/and by selection of
configuration files listing the views.
- In the Apex menu, select 'TestRT> Component Testing> Create Test Tower'.
This will generate a copy (The TestRT tower) of the origin tower to be used to
build and execute IBM Rational Test RealTime tests.
Views in this new tower have a '_TestRT' suffix.
- Launch 'Studio', the IBM Rational Test RealTime GUI.
- Create a new project.
- Choose a name for your project.
- Choose the Rational Apex TDP.
- Create a new Component Testing Activity.
- Select (in the origin tower) the unit to test.
- The name of the Component Testing node should be the Ada name of the unit under
test.
- In 'Settings...> Build> Compiler', change the setting for 'User Link File for Ada' to be
the 'link.alk' file in the TestRT view containing the unit under test.
- In 'Settings...> General> Directories', change the setting for 'Temporary' directory to be
the 'TestRT' subdirectory of the TestRT view containing the unit under test.
- Then complete the creation of your project as usual.
Once the project has been generated, the user can use IBM Rational Test RealTime
with Rational Apex as usual.
Note:
- Using 'TestRT> Component Testing> Create Test Tower' when the Test
tower already exists simply re-generates the 'link file' in the existing tower.
- To force the deletion/re-creation of any existing views in the Test tower,
use 'TestRT> Component Testing> Re-create Test Tower' .
4 - Code Coverage Standalone mode
- Select in the Apex directory browser the tower of views containing the units to
instrument.
This may be done by explicit selection of a (single) view or/and by selection of
configuration files listing the views.
- In the Apex menu, select 'TestRT> Code Coverage> Code Coverage Options...'.
Enable these options and modify them as desired.
Do not forget to specify the dump point in 'Function-specific Dump'.
- In the Apex menu, select 'TestRT> Code Coverage> Create Instrumented Tower'.
This will generate a copy (The Coverage tower) of the origin tower containing
instrumented versions of the unit.
Views in this new tower have a '_TestRT_Cov' suffix.
- The instrumentation options (and name of the main procedure) used will be
those listed in the 'coverage_.opt' options file of the Coverage tower
(this file will be created if not present in the origin tower).
- Link this main procedure in the Coverage tower to generate the instrumented
executable.
- Run this executable.
- Select the 'attolcov.spt' traces file that gets generated in the same view.
- In the Apex menu, select 'TestRT> Code Coverage> View Coverage Report'. This
will launch the IBM Rational Test RealTime GUI to display the coverage results.
Note:
- Using 'TestRT> Code Coverage> Create Instrumented Tower' when the Coverage
tower already exists simply re-instruments the units in the existing tower
(with different options if the options file was modified).
- To force the deletion/re-creation of any existing views in the Coverage tower,
use 'TestRT> Code Coverage> Re-create Instrumented Tower' .
|
|
adaxgnat.xdp
|
Ada - Ada83
|
Component Testing - Code Coverage
|
|
GNAT 3.11p - GNAT 3.13p
|
GNAT Make Program 3.11p - GNAT Make Program 3.13p
|
GDB gnat.3.11p - GDB gnat.3.13p
|
Native
|
Native
|
For v7.1
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.19.4.10 $
Support:
-------
Language : Ada - Ada83
Features : Component Testing - Code Coverage
Tested Against:
--------------
TestRT Host machine : Windows or UNIX/Linux (remote mode) or UNIX/Linux (local mode)
Compiler Host Machine : Sun Solaris 2.8 - Linux RedHat 7.2
Compiler : GNAT Compiler 3.11p - GNAT Compiler 3.13p
Linker : GNAT Make Program 3.11p - GNAT Make Program 3.13p
Debugger : GDB gnat.3.11p - GDB gnat.3.13p
OS : Native
Target : Native
Notes for this "cross" TDP:
--------------------------
This variant of the standard 'adagnat' TDP is a proof of concept for a "cross" TDP, that is a TDP that drives a compiler on a remote host machine:
- all TestRT operations (studio GUI, test script pre-processing, source instrumentation, report post-processing) execute on the 'local' (typically
Windows but possibly UNIX/Linux) host.
- but all compiler operations (Ada sources compilation and link, execution) execute on the 'remote' UNIX/Linux host.
This TDP relies on file sharing between the local and remote host (typically by mounting of Samba or NFS shares from the remote host on the local host).
It uses the following specific basic settings, that have to be adapted as needed:
- REMOTE_CONNECTION : remote connection method: rsh or ssh (if not set, rsh will be used).
- REMOTE_HOST : hostname of the remote host (may be overriden by environment variable of same name).
Note: if this is not set or is the local hostname, the TDP will run in 'local' mode, and should then behave exactly as the standard 'adagnat' TDP.
In this case, the other cross specific basic settings will not be used.
- REMOTE_USER : username used for command invocation (through 'rsh') on remote host (may be overriden by environment variable of same name.)
Note: if not set, local username will be used.
- REMOTE_TARGETDIR : path where the TDP target directory is installed on the remote host.
Note: this installation does not need to be complete: only the $TARGETDIR/lib directory is needed (to access TDP library sources).
If the full TDP is installed on the remote host, it may be used in 'local' mode on this host.
- REMOTE_SYS_DIR : path of the 'system directory' (containing standard include files and libraries) on the remote host.
- LOCAL_SYS_SHARE : name of the share (Samba UNC path or drive letter, or NFS mount point) on which REMOTE_SYS_DIR is mounted on local host.
- REMOTE_USER_DIR : path of the user directory' (containing test projects and scripts and source files) on the remote host.
- LOCAL_USER_SHARE : name of the share (Samba UNC path or drive letter, or NFS mount point) on which REMOTE_USER_DIR is mounted on local host.
The changes made here to the base 'adagnat' TDP, that rely on a set of utility routines provided in the 'remoteUtils.pl' perl script,
should be applicable to any other UNIX/Linux-based Ada TDP, to turn it into a "cross" TDP.
Notes from the base UNIX/Linux version of this TDP:
---------------------------------------------
This is the Target Deployment Port for UNIX/Linux native GNAT.
- For Instructions on configuring this TDP, please refer to the 'README.GNAT' node.
|
|
cCWHCS08WinIdea.xdp
|
C
|
Component Testing - Code Coverage
|
Windows
|
CodeWarrior for Microcontrollers V5.1
|
CodeWarrior for Microcontrollers
|
WindIdea IC5000
|
None
|
HCS08
|
For v8.0.1 Release
$Revision: 1.00 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : CodeWarrior for Microcontrollers V5.1
Linker : CodeWarrior for Microcontrollers
Debugger : WindIdea IC5000
OS : None
Target : HCS08
To get this TDP working with WinIDEA debugger you need to install the isystemConnect perl interface.
goto http://isystem.com/download/winidea-testidea-apis then get the iSYSTEM.Perl.SDK.zip
extract the lib-5.8-RTRT and copy the isystemConnect.pm and isystemConnect.dll into
%TESTRTDIR%/lib/perl
|
|
cCWHiWave9S08GT.xdp
|
C - C++
|
Component Testing - Code Coverage
|
Windows
|
CodeWarrior V5.0
|
CodeWarrior V5.0
|
hiwave 6.1
|
None
|
HCS08
|
For v7.5 Release
$Revision: 1.6 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : CodeWarrior V5.0
Linker : CodeWarrior V5.0
Debugger : hiwave 6.1
OS : None
Target : HCS08
the build environment for this target MC9S08GTxx can be found for free @ http://www.freescale.com/webapp/sps/site/homepage.jsp?code=CW_HOME
This TDP has been developped for the classic IDE
to use virtualUART_address=0x107E
http://www.noicedebugger.com/help/bdm08.htm#VIRTUAL_UART
|
|
cCwHC12WinIdea.xdp
|
C
|
Component Testing - Code Coverage - trace
|
Windows
|
CodeWarrior for Microcontrollers V5.1
|
CodeWarrior for Microcontrollers V5.1
|
WindIdea IC5000
|
None
|
HCS12
|
For v8.0.1 Release
$Revision: 1.00 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage - trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : CodeWarrior for Microcontrollers V5.1
Linker : CodeWarrior for Microcontrollers V5.1
Debugger : WindIdea IC5000
OS : None
Target : HCS12
To get this TDP working with WinIDEA debugger you need to install the isystemConnect perl interface.
goto http://isystem.com/download/winidea-testidea-apis then get the iSYSTEM.Perl.SDK.zip
extract the lib-5.8-RTRT and copy the isystemConnect.pm and isystemConnect.dll into
%TESTRTDIR%/lib/perl
during the development of this TDP we have observed that right after reset the breakPoints are not active on target.
So we change the execution steps to lock execution into infinite loop (see init function availability) that is unlocked by the WinIDEA script 1 second after run.
So breakPoints becomes active and the execution break normaly on priv_writln to dump results and stop execution once 'tdp end' is met.
|
|
cCwHCS08simFs.xdp
|
C - C++
|
Component Testing - Code Coverage
|
Windows
|
CodeWarrior for Microcontrollers V6.0
|
CodeWarrior for Microcontrollers V6.0
|
hiwave 6.1
|
None
|
HCS08
|
For v7.5.0.3 Release and higer
This TDP uses File system provided by the Simulator testTerm window
So It require enough memory to include termio.c
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : CodeWarrior for Microcontrollers V6.0
Linker : CodeWarrior for Microcontrollers V6.0
Debugger : hiwave 6.1
OS : None
Target : HCS08
|
|
cCwMPC5604.xdp
|
C
|
Component Testing - Code Coverage
|
|
mwcceppc.exe
|
mwldeppc.exe
|
cwide.exe v10.6
|
|
MPC5604
|
For TestRT v8.0.1
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Target : MPC5604
Environment
------------------------
Host : Windows
Assembler : mwasmeppc.exe
Compiler : mwcceppc.exe
Linker : mwldeppc.exe
Debugger : cwide.exe v10.6
you will still have to change some basic setting to get this TDP working.
In addition you need to create an RTRT project into a dedicated workspace the path to it will be set to CW_WORKSPACE basic setting
In this project you have to create a launch configuration called TestRT_run. This is the launch configuration used by TestRT to execute the code on target.
Based on this project the cwide (DEBUGGER) can be used in one shot mode or server mode.
one shot mode: the cwide.exe is launched for each execution.
server mode the cwide.exe is started previously manually and wait for RTRT.abs to be copied into the RTRT project then execute it then wait for the next execution.
To start cwide.exe in server mode the user has to execute runServer.bat located into the dedicated workspace
To stop the server the user has to execute the same runServer.bat again.
The TDP execution function detect automatically the execution mode to use (server or one shot)
|
|
cGnuBase.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
gnu base
|
gnu base
|
gdb 6.3
|
Native
|
Native
|
For v7.5.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.2.4.9 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : gnu base
Linker : gnu base
Debugger : gdb 6.3
OS : Native
Target : Native
|
|
cGnuSTM32F411.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
arm-none-eabi-gcc.exe
|
arm-none-eabi-gcc.exe
|
OpenOCD-0.9.0
|
none
|
STM32F411RE NUCLEO board from STMicroelectronics
|
For v8.0.1.2 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
This TDP intend to enable unit testing and runtime analysis on source under test without using RTOS.
So the generated main is run in place of the RTOS.get started guide is available from TestRT support to play with this chip target with TestRT
A
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : arm-none-eabi-gcc.exe
Linker : arm-none-eabi-gcc.exe
Debugger : OpenOCD-0.9.0
OS : none
Target : STM32F411RE NUCLEO board from STMicroelectronics
for performance profiling using µCos
App_TaskSwHook should call atl_schedule_hook(OSTCBCur->OSTCBId,OSTCBHighRdy->OSTCBId);
|
|
cSTM32GnuOpenOcd.xdp
|
C - C++
|
Component Testing - Code Coverage - Trace
|
Windows
|
arm-none-eabi-gcc.exe
|
arm-none-eabi-gcc.exe
|
OpenOCD-0.8.0
|
none
|
STM32
|
For v8.0.1.1 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
This TDP intend to make enable unit testing and runtime analysis on source under test without using the µCos RTOS.
So the generated main is run n place of the RTOS.
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : arm-none-eabi-gcc.exe
Linker : arm-none-eabi-gcc.exe
Debugger : OpenOCD-0.8.0
OS : none
Target : STM32
for performance profiling using µCos
App_TaskSwHook should call atl_schedule_hook(OSTCBCur->OSTCBId,OSTCBHighRdy->OSTCBId);
|
|
carm.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows 2000
|
ARM Developer Suite 1.0.1
|
ARM Developer Suite 1.0.1
|
ARM Developer Suite 1.0.1
|
None
|
ARMulator
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.38.4.9 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : ARM Developer Suite 1.0.1
Linker : ARM Developer Suite 1.0.1
Debugger : ARM Developer Suite 1.0.1
OS : None
Target : ARMulator
|
|
clinCrossRaspiRemote.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
|
gcc version 8
|
gcc version 8
|
GNU gdb Linux (5.2.1-4 / 5.3)
|
Native
|
Native
|
For v7.0.0 Release
HCL OneTest Embedded
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2020. All Rights Reserved
$Revision: 1.33.4.7 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
--------------
TestRT Host machine : UNIX/Linux (remote mode) or Linux (local mode)
Compiler Host Machine : Linux
Compiler : gcc version 8
Linker : gcc version 8
Debugger : GNU gdb Linux (5.2.1-4 / 5.3)
OS : Native
Target : Native
Notes for this "cross" TDP:
--------------------------
This variant of the standard 'clinuxgnu' TDP is a proof of concept for a "cross" TDP, that is a TDP that drives a compiler on a remote host machine:
- all TestRT operations (studio GUI, test script pre-processing, source instrumentation, report post-processing) execute on the 'local' (typically
Windows but possibly UNIX/Linux) host.
- but all compiler operations (C/C++ sources preprocessing and compilation, link and execution) execute on the 'remote' Linux host.
This TDP relies on file sharing between the local and remote host (typically by mounting of Samba or NFS shares from the remote host on the local host).
It uses the following specific basic settings, that have to be adapted as needed:
- REMOTE_CONNECTION : remote connection method: rsh or ssh (if not set, rsh will be used).
- REMOTE_HOST : hostname of the remote host (may be overriden by environment variable of same name).
Note: if this is not set or is the local hostname, the TDP will run in 'local' mode, and should then behave exactly as the standard 'clinuxgnu' TDP.
In this case, the other cross specific basic settings will not be used.
- REMOTE_USER : username used for command invocation (through 'rsh') on remote host (may be overriden by environment variable of same name.)
Note: if not set, local username will be used.
- REMOTE_TARGETDIR : path where the TDP target directory is installed on the remote host.
Note: this installation does not need to be complete: only the $TARGETDIR/lib directory is needed (to access TDP library sources).
If the full TDP is installed on the remote host, it may be used in 'local' mode on this host.
- REMOTE_SYS_DIR : path of the 'system directory' (containing standard include files and libraries) on the remote host.
- LOCAL_SYS_SHARE : name of the share (Samba UNC path or drive letter, or NFS mount point) on which REMOTE_SYS_DIR is mounted on local host.
- REMOTE_USER_DIR : path of the user directory' (containing test projects and scripts and source files) on the remote host.
- LOCAL_USER_SHARE : name of the share (Samba UNC path or drive letter, or NFS mount point) on which REMOTE_USER_DIR is mounted on local host.
The changes made here to the base 'clinuxgnu' TDP, that rely on a set of utility routines provided in the 'remoteUtils.pl' perl script,
should be applicable to any other UNIX/Linux-based C/C++ TDP, to turn it into a "cross" TDP.
Notes from the base Linux version of this TDP:
---------------------------------------------
The attolcc launcher is migrating to a Perl script version, easier to modify. This attolcc.pl requires a perl launcher having the same baseName. So, we cannot have both: the old attolcc instrumenter launcher and the new attolcc perl launcher.
For ascendant compatibility the old attolcc instrumenter launcher is kept as the default launcher until the next version.
Usage of the attolcc launcher is still the same. Type 'attolcc -help' for more details.
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
|
|
clinuxgnu3_2.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Linux Suse 8.1 - Linux RedHat 8.0
|
gcc version 3.2 to 4.1
|
gcc version 3.2 to 4.1
|
GNU gdb Linux
|
Native
|
Native
|
For v7.0.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.108.4.7 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------
Host Machine : Linux Suse 8.1 - Linux RedHat 8.0
Compiler : gcc version 3.2 to 4.1
Linker : gcc version 3.2 to 4.1
Debugger : GNU gdb Linux
OS : Native
Target : Native
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
In order to come back to the previous TDP configuration using the old attolcc binary, the following steps are necessary:
- Manually delete the attolcc.pl script generated in /targets//cmd;
- Run the tdpeditor and open the corresponding xdp;
- Rename the attolcc.pl script to _attolcc.pl;
- Save and generate the TDP.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
|
|
clinuxgnu3breakpoint.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Linux Suse 8.1 - Linux RedHat 8.0
|
gcc version 3.2 to 4.1
|
gcc version 3.2 to 4.1
|
GNU gdb Linux (5.2.1-4 / 5.3) breakPoint mode
|
Native
|
Native
|
For v7.0.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.37.4.7 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------
Host Machine : Linux Suse 8.1 - Linux RedHat 8.0
Compiler : gcc version 3.2 to 4.1
Linker : gcc version 3.2 to 4.1
Debugger : GNU gdb Linux (5.2.1-4 / 5.3) breakPoint mode
OS : Native
Target : Native
The attolcc launcher is migrating to a Perl script version, easier to modify. This attolcc.pl requires a perl launcher having the same baseName. So, we cannot have both: the old attolcc instrumenter launcher and the new attolcc perl launcher.
For ascendant compatibility the old attolcc instrumenter launcher is kept as the default launcher until the next version.
Usage of the attolcc launcher is still the same. Type 'attolcc -help' for more details.
If you want to use the attolcc perl version:
- Run the tdpeditor and open the corresponding xdp;
- Rename the delivered _attolcc.pl to attolcc.pl;
- Save and generate the TDP.
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
In order to come back to the previous TDP configuration using the old attolcc binary, the following steps are necessary:
- Manually delete the attolcc.pl script generated in /targets//cmd;
- Run the tdpeditor and open the corresponding xdp;
- Rename the attolcc.pl script to _attolcc.pl;
- Save and generate the TDP.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
|
|
clinuxgnu3socket.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Linux Suse 8.1 - Linux RedHat 8.0
|
gcc version 3.2 to 4.1
|
gcc version 3.2 to 4.1
|
GNU gdb Linux (5.2.1-4 / 5.3)
|
Native
|
Native
|
For v7.0.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.35.4.5 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------
Host Machine : Linux Suse 8.1 - Linux RedHat 8.0
Compiler : gcc version 3.2 to 4.1
Linker : gcc version 3.2 to 4.1
Debugger : GNU gdb Linux (5.2.1-4 / 5.3)
OS : Native
Target : Native
The attolcc launcher is migrating to a Perl script version, easier to modify. This attolcc.pl requires a perl launcher having the same baseName. So, we cannot have both: the old attolcc instrumenter launcher and the new attolcc perl launcher.
For ascendant compatibility the old attolcc instrumenter launcher is kept as the default launcher until the next version.
Usage of the attolcc launcher is still the same. Type 'attolcc -help' for more details.
If you want to use the attolcc perl version:
- Run the tdpeditor and open the corresponding xdp;
- Rename the delivered _attolcc.pl to attolcc.pl;
- Save and generate the TDP.
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
In order to come back to the previous TDP configuration using the old attolcc binary, the following steps are necessary:
- Manually delete the attolcc.pl script generated in /targets//cmd;
- Run the tdpeditor and open the corresponding xdp;
- Rename the attolcc.pl script to _attolcc.pl;
- Save and generate the TDP.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
|
|
clinuxgnu64.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Linux Suse 8.1 - Linux RedHat 8.0
|
gcc version 3.2 to 4.1
|
gcc version 3.2 to 4.1
|
GNU gdb Linux
|
Native
|
Native
|
For v7.0.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.108.4.7 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------
Host Machine : Linux Suse 8.1 - Linux RedHat 8.0
Compiler : gcc version 3.2 to 4.1
Linker : gcc version 3.2 to 4.1
Debugger : GNU gdb Linux
OS : Native
Target : Native
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
In order to come back to the previous TDP configuration using the old attolcc binary, the following steps are necessary:
- Manually delete the attolcc.pl script generated in /targets//cmd;
- Run the tdpeditor and open the corresponding xdp;
- Rename the attolcc.pl script to _attolcc.pl;
- Save and generate the TDP.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
|
|
cmingw64.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 10
|
Gnu 8.1 (mingw)
|
Gnu 8.1 (mingw)
|
Gnu 8.1 (mingw)
|
Native
|
Native
|
For v8.3
HCL OneTest Embedded
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 10
Compiler : Gnu Compiler 8.1 (mingw)
Linker : Gnu Linker 8.1 (mingw)
Debugger : Gnu Debugger 8.1 (mingw)
OS : Native
Target : Native
This target deployment port is adapted for the "Minimalist Gnu for Windows". This package can be downloaded from https://sourceforge.net/projects/mingw-w64/
The installation directory must be modified in Basic Settings > For All > BASE as described in the comment window of this key.
|
|
cpcgnu.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
cygwin gcc 3.4.4
|
cygwin gcc 3.4.4
|
cygwin gdb 6.3
|
Native
|
Native
|
For v8.3.0.1 Release min
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2019 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2019. All Rights Reserved
$Revision: 1.89.4.20 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : cygwin gcc 3.4.4
Linker : cygwin gcc 3.4.4
Debugger : cygwin gdb 6.3
OS : Native
Target : Native
|
|
cpcgnu64.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
cygwin gcc 7.3.0
|
cygwin gcc 7.3.0
|
cygwin gdb 7.12
|
Native
|
Native
|
For v8.3.0.1 Release min
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2019 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2019. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : cygwin gcc 7.3.0
Linker : cygwin gcc 7.3.0
Debugger : cygwin gdb 7.12
OS : Native
Target : Native
|
|
cpic18fMPLABsim.xdp
|
C
|
Component Testing, Coverage
|
Windows XP
|
MicroTech mcc18 V3.33
|
MicroTech mplink V3.43
|
MPLAB 8.2
|
simulator
|
Pic18F4420 - Microchip
|
For RTRT v7.5.0.3
$Revision: 1.2.4.7 $
Support:
-------------
Language : C
Features : Component Testing, Coverage
Tested Against:
------------------------
Host Machine : Windows XP
Compiler : MicroTech mcc18 V3.33
Linker : MicroTech mplink V3.43
Debugger : MPLAB 8.2
OS : simulator
Target : Pic18F4420 - Microchip
Uses USART serial line for data retrieval
the simulator redirect UART IO to file:
The result file is written in c:\temp directory
This TDP require autoIT v3 installed on the host machine
|
|
cunxdiabsgstep.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Sun Solaris 2.8
|
DiabData 4.4a
|
DiabData 4.4a
|
SingleStep 7.6.6
|
None
|
PowerPC 604 Simulator
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.35.4.9 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------
Host Machine : Sun Solaris 2.8
Compiler : DiabData Compiler 4.4a
Linker : DiabData Linker 4.4a
Debugger : SingleStep Debugger 7.6.6
OS : None
Target : PowerPC 604 Simulator
|
|
cvisual1X.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
Microsoft Visual C++ 2010-2014 or Visual C++ 2010-2014 Express Edition with the Microsoft Platform SDK
|
Microsoft Visual C++ 2010-2014
|
Microsoft Visual C++ 2010-2014
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2008-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Microsoft Visual C++ 2010-2014 or Visual C++ 2010-2014 Express Edition with the Microsoft Platform SDK
Linker : Microsoft Visual C++ 2010-2014
Debugger : Microsoft Visual C++ 2010-2014
OS : Native
Target : Native
The TDP look for MSVC installation version 10 to 13 in registry automatically. The first version checked is the version psecified in MSVER key.
The Visual C++ 2010-2014 User Interface must be launched at least once before the TDP generation to have the registry updated.
When saved, the IBM Rational Target Deployment Port directory for Microsoft Visual C++ 2010-2014 will be created as cvisual1X into the \targets
All the relevant fields will be updated with the right content, checking in the machine's registry, unless this development environment is not installed.
Look at the tdpGen.log into the \targets\cvisual1X directory to make sure the install is done properly.
The TDP name '2010' will be changed accordingly to the Visual version.
PLUGIN:
In order to enable the plugin installation, please set the variable 'INSTALL_PLUGIN' to 'TRUE' in the 'Basic Settings for All' section of this xdp file.
FALSE uninstall it.
Note the uninstall will not remove the Test RealTime menus from visual studio >tools. If you want to remove them use the tool menu > custom... to remove them.
If the TDP does not install properly check the generated tdpGen.log file to get debug details.
If one os the key registry does not fit your installation you can modify or add them on top of the Build Settings > postgen.pl
|
|
cvisual2017.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
Microsoft Visual C++ 2017
|
Microsoft Visual C++ 2017
|
Microsoft Visual C++ 2017
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2008-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2020. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Microsoft Visual C++ 2017
Linker : Microsoft Visual C++ 2017
Debugger : Microsoft Visual C++ 2017
SDK : Windows 10 SDK (10.0.18362.0)
OS : Native
Target : Native
Installation
-----------------
In the Basic Settigs / For All, make sure the following variables are set correctly :
- INSTALLDIR this is the directory where Microsoft Visual Studio is installed on the host machine
- MSPACKAGE
- MSVERSION
- MSVER
- INSTALL_PLUGIN requires ADMINISTRATOR RIGHTS if Microsoft Visual Studio is installed in a protected directory.
When set to TRUE generating the TDP
- will patch the compiler and linker
- will generate the file targets\cvisual2017\cmd\VisualStudioExternalTools.vssettings
Manually import the VisualStudioExternalTools.vssettings file in the Tools menu of Microsoft Visual Studio
When set to FALSE generating the TDP
- will remove the compiler and linker patches
- will NOT remove the entried in the Tools menu
Remove those entries manually
Look at the tdpGen.log into the \targets\cvisual2017 directory to make sure the installation is done properly.
|
|
cvisual2017_64.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
Microsoft Visual C++ 2017
|
Microsoft Visual C++ 2017
|
Microsoft Visual C++ 2017
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2008-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2020. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Microsoft Visual C++ 2017
Linker : Microsoft Visual C++ 2017
Debugger : Microsoft Visual C++ 2017
SDK : Windows 10 SDK (10.0.18362.0)
OS : Native
Target : Native
Installation
-----------------
In the Basic Settigs / For All, make sure the following variables are set correctly :
- INSTALLDIR this is the directory where Microsoft Visual Studio is installed on the host machine
- MSPACKAGE
- MSVERSION
- MSVER
- INSTALL_PLUGIN requires ADMINISTRATOR RIGHTS if Microsoft Visual Studio is installed in a protected directory.
When set to TRUE generating the TDP
- will patch the compiler and linker
- will generate the file targets\cvisual2017_64\cmd\VisualStudioExternalTools.vssettings
Manually import the VisualStudioExternalTools.vssettings file in the Tools menu of Microsoft Visual Studio
When set to FALSE generating the TDP
- will remove the compiler and linker patches
- will NOT remove the entried in the Tools menu
Remove those entries manually
Look at the tdpGen.log into the \targets\cvisual2017 directory to make sure the installation is done properly.
|
|
cvisual2019.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
Microsoft Visual C++ 2019
|
Microsoft Visual C++ 2019
|
Microsoft Visual C++ 2019
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2008-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2020. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Microsoft Visual C++ 2019
Linker : Microsoft Visual C++ 2019
Debugger : Microsoft Visual C++ 2019
SDK : Windows 10 SDK (10.0.18362.0)
OS : Native
Target : Native
Installation
-----------------
In the Basic Settigs / For All, make sure the following variables are set correctly :
- INSTALLDIR this is the directory where Microsoft Visual Studio is installed on the host machine
- MSPACKAGE
- MSVERSION
- MSVER
- INSTALL_PLUGIN requires ADMINISTRATOR RIGHTS if Microsoft Visual Studio is installed in a protected directory.
When set to TRUE generating the TDP
- will patch the compiler and linker
- will generate the file targets\cvisual2019\cmd\VisualStudioExternalTools.vssettings
Manually import the VisualStudioExternalTools.vssettings file in the Tools menu of Microsoft Visual Studio
When set to FALSE generating the TDP
- will remove the compiler and linker patches
- will NOT remove the entried in the Tools menu
Remove those entries manually
Look at the tdpGen.log into the \targets\cvisual2017 directory to make sure the installation is done properly.
|
|
cvisual2019_64.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
Microsoft Visual C++ 2019
|
Microsoft Visual C++ 2019
|
Microsoft Visual C++ 2019
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2008-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2020. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Microsoft Visual C++ 2019
Linker : Microsoft Visual C++ 2019
Debugger : Microsoft Visual C++ 2019
SDK : Windows 10 SDK (10.0.18362.0)
OS : Native
Target : Native
Installation
-----------------
In the Basic Settigs / For All, make sure the following variables are set correctly :
- INSTALLDIR this is the directory where Microsoft Visual Studio is installed on the host machine
- MSPACKAGE
- MSVERSION
- MSVER
- INSTALL_PLUGIN requires ADMINISTRATOR RIGHTS if Microsoft Visual Studio is installed in a protected directory.
When set to TRUE generating the TDP
- will patch the compiler and linker
- will generate the file targets\cvisual2019_64\cmd\VisualStudioExternalTools.vssettings
Manually import the VisualStudioExternalTools.vssettings file in the Tools menu of Microsoft Visual Studio
When set to FALSE generating the TDP
- will remove the compiler and linker patches
- will NOT remove the entried in the Tools menu
Remove those entries manually
Look at the tdpGen.log into the \targets\cvisual2017 directory to make sure the installation is done properly.
|
|
cvisual6.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows 2000
|
Microsoft Visual C++ 6.0
|
Microsoft Visual C++ 6.0
|
Microsoft Visual C++ 6.0
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Microsoft Visual C++ 6.0
Linker : Microsoft Visual C++ 6.0
Debugger : Microsoft Visual C++ 6.0
OS : Native
Target : Native
The attolcc launcher is migrating to a Perl script version, easier to modify. This attolcc.pl requires a perl launcher having the same baseName. So, we cannot have both: the old attolcc instrumenter launcher and the new attolcc perl launcher.
For ascendant compatibility the old attolcc instrumenter launcher is kept as the default launcher until the next version.
Usage of the attolcc launcher is still the same. Type 'attolcc -help' for more details.
If you want to use the attolcc perl version:
- Run the tdpeditor and open the corresponding xdp;
- Rename the delivered _attolcc.pl to attolcc.pl;
- Save and generate the TDP.
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_cl.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
In order to come back to the previous TDP configuration using the old attolcc binary, the following steps are necessary:
- Manually delete the attolcc.pl script generated in /targets//cmd;
- Run the tdpeditor and open the corresponding xdp;
- Rename the attolcc.pl script to _attolcc.pl;
- Save and generate the TDP.
When saved, the IBM Rational Target Deployment Port directory for Microsoft Visual 6 will be created.
All the relevant fields will be updated with the right content, checking in the machine's registry, unless Microsoft Visual 6 development environment is not installed.
|
|
cvisual7.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows 2000
|
Microsoft Visual Studio .NET 7.0.9466
|
Microsoft Visual Studio .NET 7.0.9466
|
Microsoft Visual Studio .NET 7.0.9466
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Microsoft Visual Studio .NET 7.0.9466
Linker : Microsoft Visual Studio .NET 7.0.9466
Debugger : Microsoft Visual Studio .NET 7.0.9466
OS : Native
Target : Native
When saved, the IBM Rational Target Deployment Port directory for Microsoft Visual .NET will be created.
All the relevant fields will be updated with the right content, checking in the machine's registry, unless Microsoft Visual .NET development environment is not installed.
The Visual .NET User Interface must be launched at least once before the TDP generation to have the registry updated.
When saved, the IBM Rational Target Deployment Port directory for Microsoft Visual .NET will be created as cvisual into the \targets
All the relevant fields will be updated with the right content, checking in the machine's registry, unless this development environment is not installed.
Look at the tdpGen.log in the into the \targets\cvisual7 directory to make sure the install is done properly.
PLUGIN:
In order to enable the plugin installation, please set the variable 'INSTALL_PLUGIN' to 'TRUE' in the 'Basic Settings for All' section of this xdp file.
FALSE uninstall it.
if the TDP must be shared between multiple limited user accounts then set the Basic Settings> For All> TEMP key value to a shared directory.
|
|
cvisual8.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
Microsoft Visual C++ 2005 or Visual C++ 2005 Express Edition with the Microsoft Platform SDK
|
Microsoft Visual C++ 2005
|
Microsoft Visual C++ 2005
|
Native
|
Native
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Microsoft Visual C++ 2005 or Visual C++ 2005 Express Edition with the Microsoft Platform SDK
Linker : Microsoft Visual C++ 2005
Debugger : Microsoft Visual C++ 2005
OS : Native
Target : Native
The free compiler Visual C++ 2005 Express Edition with the Microsoft Platform SDK can be found @ http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/default.aspx
The Visual C++ 2005 User Interface must be launched at least once before the TDP generation to have the registry updated.
When saved, the IBM Rational Target Deployment Port directory for Microsoft Visual C++ 2005 will be created as cvisual into the \targets
All the relevant fields will be updated with the right content, checking in the machine's registry, unless this development environment is not installed.
Look at the tdpGen.log in the into the \targets\cvisual8 directory to make sure the install is done properly.
PLUGIN:
In order to enable the plugin installation, please set the variable 'INSTALL_PLUGIN' to 'TRUE' in the 'Basic Settings for All' section of this xdp file.
FALSE uninstall it.
Note the uninstall will not remove the Test RealTime menus from visual studio >tools. If you want to remove them use the tool menu > custom... to remove them.
migrating from TestRT version prior to 8.0 may require to manually remove TestRT menus from visual studio and re-save the TDP.
If the TDP does not install properly check the generated tdpGen.log file to get debug details.
If one os the key registry does not fit your installation you can modify or add them on top of the Build Settings > postgen.pl
|
|
cvisual9.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
Microsoft Visual C++ 2008 or Visual C++ 2008 Express Edition with the Microsoft Platform SDK
|
Microsoft Visual C++ 2008
|
Microsoft Visual C++ 2008
|
Native
|
Native
|
IBM Rational Test RealTime
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Microsoft Visual C++ 2008 or Visual C++ 2008 Express Edition with the Microsoft Platform SDK
Linker : Microsoft Visual C++ 2008
Debugger : Microsoft Visual C++ 2008
OS : Native
Target : Native
The free compiler Visual C++ 2008 Express Edition with the Microsoft Platform SDK can be found @ http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/default.aspx
The Visual C++ 2008 User Interface must be launched at least once before the TDP generation to have the registry updated.
When saved, the IBM Rational Target Deployment Port directory for Microsoft Visual C++ 2008 will be created as cvisual into the \targets
All the relevant fields will be updated with the right content, checking in the machine's registry, unless this development environment is not installed.
Look at the tdpGen.log in the into the \targets\cvisual9 directory to make sure the install is done properly.
PLUGIN:
In order to enable the plugin installation, please set the variable 'INSTALL_PLUGIN' to 'TRUE' in the 'Basic Settings for All' section of this xdp file.
FALSE uninstall it.
Note the uninstall will not remove the Test RealTime menus from visual studio >tools. If you want to remove them use the tool menu > custom... to remove them.
migrating from TestRT version prior to 8.0 may require to manually remove TestRT menus from visual studio and re-save the TDP.
If the TDP does not install properly check the generated tdpGen.log file to get debug details.
If one os the key registry does not fit your installation you can modify or add them on top of the Build Settings > postgen.pl
|
|
cvisual_64.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows AMD64
|
Microsoft Visual C++ 2010-2014 or Visual C++ 2010-2014 Express Edition with the Microsoft Platform SDK
|
Microsoft Visual C++ 2010-2014
|
Microsoft Visual C++ 2010-2014
|
Native
|
Native x86 amd64 x64 x86_amd64 amd64_x86
|
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2008-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows AMD64
Compiler : Microsoft Visual C++ 2010-2014 or Visual C++ 2010-2014 Express Edition with the Microsoft Platform SDK
Linker : Microsoft Visual C++ 2010-2014
Debugger : Microsoft Visual C++ 2010-2014
OS : Native
Target : Native x86 amd64 x64 x86_amd64 amd64_x86
The Visual C++ 2010-2014 User Interface must be launched at least once before the TDP generation to have the registry updated.
When saved, the IBM Rational Target Deployment Port directory for Microsoft Visual C++ 64 bits will be created as cvisual into the \targets
All the relevant fields will be updated with the right content, checking in the machine's registry, unless this development environment is not installed.
Look at the tdpGen.log into the \targets\cvisual_64 directory to make sure the install is done properly.
The TDP name '2010' will be changed accordingly to the Visual version.
PLUGIN:
In order to enable the plugin installation, please set the variable 'INSTALL_PLUGIN' to 'TRUE' in the 'Basic Settings for All' section of this xdp file.
FALSE uninstall it.
Note the uninstall will not remove the Test RealTime menus from visual studio >tools. If you want to remove them use the tool menu > custom... to remove them.
If the TDP does not install properly check the generated tdpGen.log file to get debug details.
If one os the key registry does not fit your installation you can modify or add them on top of the Build Settings > postgen.pl
|
|
cwin166uv2.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Trace
|
Windows 2000
|
KEIL 4.06
|
KEIL 4.06
|
µVision2
|
None
|
Infineon C166 Simulator
|
For v2003.06.12
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.18.4.8 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : KEIL Compiler 4.06
Linker : KEIL Linker 4.06
Debugger : µVision2
OS : None
Target : Infineon C166 Simulator
|
|
cwin55xgodsp.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
TMS320C55x C/C++ Shell Version 2.00
|
TMS320C55x COFF Version 2.04
|
Code Composer v2.00
|
None
|
C55x Simulator
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.33.4.9 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : TMS320C55x C/C++ Compiler Shell Version 2.00
Linker : TMS320C55x COFF Linker Version 2.04
Debugger : Code Composer v2.00
OS : None
Target : C55x Simulator
CAREFUL:
Before using Test RealTime with this TDP:
For a multiprocessor board, please modify your system configuration by bypassing (in the Code Composer Studio Setup) CPUs different from TMS320C55x. Thus, only this CPU will be visible which will allow IBM Rational Test RealTime Studio to launch Code Composer Studio without launching the Parallel Debug Manager.
|
|
cwin6xgodsp.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows
|
TMS320C6x C/C++ Shell Version 4.10
|
TMS320C6x COFF Version 4.10
|
Code Composer v3.1
|
None
|
TMS320C64XX Simulator
|
For v7.0.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.62.4.9 $
ATTENTION: This TDP (xdpName) MUST NOT be renamed because the file Rational.ocx use this name
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : TMS320C6x C/C++ Compiler Shell Version 4.10
Linker : TMS320C6x COFF Linker Version 4.10
Debugger : Code Composer v3.1
OS : None
Target : TMS320C64XX Simulator
!!! BEFORE INSTALLING THIS TDP, YOU MAY HAVE TO change the path to CCS in Basic settings For All > VARIABLE CC_APPHOME TO '\cc\bin' !!!
check with the registry as HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CCS_C:|CCStudio_Vx.x| => CC_APP
provide where the binaries are installed
This Target Deployment Port enables the use of IBM Rational Test RealTime in either of the following two modes:
- via the IBM Rational Test RealTime user interface (for both testing and runtime analysis).
- via Code Composer Studio (for runtime analysis).
By pressing the save button in the TDP Editor, you will create a "IBM Rational Test RealTime" subitem in the Code Composer Studio Tools menu. This submenu is used to set the desired runtime analysis options as well as to open the resulting reports within Test RealTime. When setting the desired levels of analysis, you must "enable" the instrumentation required by Test RealTime.
Instrumented programs use the atexit function to register the data retrieval function. This means your program must exit. If your program does not exit then, within the Runtime Analysis Options window (in Code Composer Studio), specify the name of the function that should trigger a dump of analysis data within the Function-Specific Dump section. This function should represent an end of the program or - at the very least - an end to the interaction.
You may have to modify the linker command file since runtime analysis instrumentation will require additional memory. If this is not an option, choose a lower instrumentation level.
DSP/BIOS :
For multi-threaded application, please enable the use of the CCS DSP/BIOS by setting the variable USE_DSPBIOS to 1 in the 'Basic Settings For C'. By default the TestRT application will be linked using the configuration file (c6x.cdb) attached to this xdp.
The option -cdb= added to the link flags of studio allows you to replace the default configuration file used by your own customized cdb.
|
|
cwinCrossRaspiRemote.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
|
Windows
|
gnu base
|
gnu base
|
gdb 6.3
|
Native
|
Native
|
For v8.0.2 Release
HCL OneTest Embedded
(c) Copyright IBM Corp. 2015-2017 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2020. All Rights Reserved
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : gnu base
Linker : gnu base
Debugger : gdb 6.3
OS : Native
Target : Native
This TDP aim to compile C code on Host machine using cross compiler then execute generated app on remote Raspberry Pi target.
The target is connected to network so that connection to it is done using Putty.
So
|
|
cwinKeilArmUv4.xdp
|
C
|
Component Testing - Code Coverage - trace
|
Windows 2000/XP
|
Keil ARM V4.0.677
|
Keil ARM Compiler V4.0.677
|
Uv4 (Keil uVision 4 V4.60)
|
None
|
ARM simulator
|
For v7.5.x
$Revision: 1.0 - RF 2012/12/13 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage - trace
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : Keil ARM Compiler V4.0.677
Asssembler : Keil ARM Compiler V4.0.677
Linker : Keil ARM Compiler V4.0.677
Debugger : Uv4 (Keil uVision 4 V4.60)
OS : None
Target : ARM simulator
Note:
---------
Data retrieval (RTRT_IO) mode supported with Uv4 debugger is:
- RTRT_NONE : breakpoint mode (debugger scripting based) (always available)
or - RTRT_USR : user I/O (serial I/O through debugger) (supported only on some devices). not tested yet
TDP specific basic settings:
-------------------------------------------
Note: These settings may be overriden by environment variables of same name.
This TDP is based on the Keil ARM example 'Measure' that use STMicroelectronics Cortex-M3 STM32F103RB simulator
|
|
cwinQNX.xdp
|
C - C++
|
Component Testing - Code Coverage - Memory Profiling - Trace
|
windows
|
qcc version
|
qcc version
|
|
QNX
|
QNX 6.5
|
For v8.0.0.3 Release and latest
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Memory Profiling - Trace
Tested Against:
------------
Host Machine : windows
Compiler qcc version
Linker : qcc version
Debugger :
OS : QNX
Target : QNX 6.5
Note: the compiler does not support space into the include dir path. So it is strongly recommanded to avoid space in any configuration or TDP or node name
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl
Thus, the user may change the behaviour of this launcher by modifying it.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
QNX machine account initialization
The QNX machine should have an existing user account as specified into the basic setting REMOTE_USER or the same name of the current user on host machine
This account must have password and a subdirectory named as defined into basic setting SHARED_REMOTE_DIR (rtrt)
the password must be set into the basic settings REMOTE_PASSWD ( '_user_' keyword will use the user account name as password)
CONNECTION on QNX machine
thera are 2 common ways and others
1) ssh
The prefered way is the ssh2 protocol that require to have the sshd running on the QNX machine
if the rsa key are not yet generated you have to execute
# ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
then start the deamon
# /usr/sbin/sshd
Now to be able to autmate execution order to QNX machine you need to install the last version of plink.exe from http://www.putty.org/
more details of the execution are provided into the /lib/scripts/RemoteFcts;pl
2) telnet
to use telnet protocol instead you must set basic setting REMOTE_CONNECTION="telnet.pl -l _user_ -pw _PassWd_" and make few modification to the TestRT installation as described into the lib/scripts/remoteFcts.pl around the sub telnet function (end of file)
here the atl_exec3 is used (ftp to download and upload file then telnet/plink/ssh2 to send execution order)
most of the basic setting can be overwritten by environment variable (same name) allowing to set them from your environment or from studio project.
|
|
cwinVxKernWb3.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows
|
|
|
VxWorks sim dbg
|
VxWorks 6.9
|
vxsim Kernel Process
|
For v7.5 Release
IBM Rational Test RealTime
$Revision: 1.0 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Debugger : VxWorks sim dbg
OS : VxWorks 6.9
Target : vxsim Kernel Process
This target deployment port is adapted for VxWorks 6.x running on an Intel x86 sim
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME [@hostname] (if IP is used to identify the target the proc
DEFAULT_DEFINES CPU=,.....
This TDP has been made for BUILD_SPEC = PENTIUMgnu_RTP
This TDP uses the WTX API 4.1 or 4.2 from WindRiver to download, start, stop, unload, reset the target and collect test results. The name of the program is rtrtWtx3.exe.
Usage: of rtrtwtx3.exe is provided by itself when an unknown option is found
The source code for rtrtWtx3 can be found in %TESTRTDIR%/targets/xml/attolcc
Note that when the target execute the code wdbUserEvtPost("RTRTENDS"); rtrtwtx3 will understand that application exits and so automatically close all the the result files opened and terminate the execution.
|
|
cwinVxRtpWB3.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows
|
|
|
VxWorks sim dbg
|
VxWorks 6.9
|
vxsim RealTime Process
|
For v7.5 Release
IBM Rational Test RealTime
$Revision: 1.0 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Debugger : VxWorks sim dbg
OS : VxWorks 6.9
Target : vxsim RealTime Process
This target deployment port is adapted for VxWorks 6.x running on an Intel x86 sim
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME [@hostname] (if IP is used to identify the target the proc
DEFAULT_DEFINES CPU=,.....
This TDP has been made for BUILD_SPEC = PENTIUMgnu_RTP
This TDP uses the WTX API 4.1 or 4.2 from WindRiver to download, start, stop, unload, reset the target and collect test results. The name of the program is rtrtWtx3.exe.
Usage: of rtrtwtx3.exe is provided by itself when an unknown option is found
The source code for rtrtWtx3 can be found in %TESTRTDIR%/targets/xml/attolcc
Note that when the target execute the code wdbUserEvtPost("RTRTENDS"); rtrtwtx3 will understand that application exits and so automatically close all the the result files opened and terminate the execution.
|
|
cwinVxRtpWsh.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows
|
|
|
VxWorks sim dbg
|
VxWorks 6.9
|
vxsim RealTime Process
|
For v8.0.2 Release
IBM Rational Test RealTime
$Revision: 1.0 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Debugger : VxWorks sim dbg
OS : VxWorks 6.9
Target : vxsim RealTime Process
This target deployment port is adapted for VxWorks 6.x running on an Intel x86 sim
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME [@hostname] (if IP is used to identify the target the proc
DEFAULT_DEFINES CPU=,.....
This TDP has been made for BUILD_SPEC = PENTIUMgnu_RTP
This TDP uses the WTX API 4.1 or 4.2 from WindRiver to download, start, stop, unload, reset the target and collect test results. The name of the program is rtrtWtx3.exe.
Usage: of rtrtwtx3.exe is provided by itself when an unknown option is found
The source code for rtrtWtx3 can be found in %TESTRTDIR%/targets/xml/attolcc
Note that when the target execute the code wdbUserEvtPost("RTRTENDS"); rtrtwtx3 will understand that application exits and so automatically close all the the result files opened and terminate the execution.
|
|
cwinWdcWinIdea.xdp
|
C
|
Component Testing - Code Coverage - Memory Profiling - Trace
|
Windows XP
|
wesdernDigital 3.47
|
|
winIdea 9.5.125
|
None
|
|
For v2003.06.13 Release
$Revision: 1.0-RF 2005/7/4 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows XP
Compiler : wesdernDigital 3.47
Linker :
Debugger : winIdea 9.5.125
OS : None
Target :
Note:
--------
|
|
cwinandroidarm.xdp
|
C
|
Component Testing - Code Coverage - Trace
|
Windows
|
Android NDK ARM compiler ()
|
Android NDK ARM linker ()
|
Android NDK ARM gdb ()
|
Android
|
(thru GDB debug server)
|
For v7.5.0.3
$Revision: 1.1 2014/5/23 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : Android NDK ARM compiler ()
Linker : Android NDK ARM linker ()
Debugger : Android NDK ARM gdb ()
OS : Android
Target : (thru GDB debug server)
Note:
---------
Data retrieval (RTRT_IO) modes supported with GDB debugger
- RTRT_NONE: breakpoint mode
TDP specific basic settings:
-------------------------------------------
- Paths of startup/runtime support files to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting.
- Address of debug server to use with GDB may be set through TARGET_SERVER basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinccs33c283xx.xdp
|
C
|
Component Testing - Runtime Analysis
|
Windows 2000/XP
|
TMS320C2000 C/C++ Version 5.1.2
|
TMS320C2000 COFF Version 5.1.2
|
Code Composer Studio Version 3.3
|
None
|
Spectrum Digital eZdsp F28335 board
|
For v7.5.x
$Revision: 1.6 - FL 2009/2/26 $
Support:
-------------
Language : C
Features : Component Testing - Runtime Analysis
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : TMS320C2000 C/C++ Compiler Version 5.1.2
Linker : TMS320C2000 COFF Linker Version 5.1.2
Debugger : Code Composer Studio Version 3.3
OS : None
Target : Code Composer Studio TMS320F283xx Simulator
Target : Spectrum Digital eZdsp F28335 board
Note:
---------
C++ support not implemented.
Execution through the CCS debugger supports data retrieval (RTRT_IO) modes:
- RTRT_USR: Host file I/O mode (if debugger simulated I/O is supported by target driver).
- RTRT_NONE: breakpoint mode (debugger scripting).
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting.
- Path of directives file(s) to use with linker may be set through TARGET_CONFIG basic setting;
- Path of target specific startup GEL file for debugger may be set through TARGET_GEL basic setting;
- Name of target board in Code Composer Studio setup may be set through TARGET_BOARD basic setting;
- Name of target CPU in Code Composer Studio setup may be set through TARGET_CPU basic setting;
- When set, TARGET_FLASH basic setting indicates executable needs to be flashed;
- Path of template SDFlash project file to be used for flashing may be set through TARGET_SDP basic setting;
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinccs5tms470.xdp
|
C
|
Component Testing - Runtime Analysis
|
Windows 2000/XP
|
TMS470 C/C++ v4.9.1
|
TMS470 PC v4.9.1
|
Code Composer Studio Version 5.1.0
|
None
|
ARM7TDMI CPU Cycle Accurate Simulator
|
For v7.5.0.x
$Revision: 1.1 - 2011/12/11 $
Support:
-------------
Language : C
Features : Component Testing - Runtime Analysis
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : TMS470 C/C++ Compiler v4.9.1
Linker : TMS470 Linker PC v4.9.1
Debugger : Code Composer Studio Version 5.1.0
OS : None
Target : ARM7TDMI CPU Cycle Accurate Simulator
Note:
---------
C++ support not implemented.
Execution through the CCS debugger supports data retrieval (RTRT_IO) modes:
- RTRT_USR: Host file I/O mode (if debugger 'CIO' support is supported/enabled on target).
- RTRT_NONE: breakpoint mode (debugger scripting).
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting.
- Path of directives file to use with linker may be set through TARGET_LINKER_CMD basic setting;
- Path of CCS 5 target configuration file to use for execution may be set through TARGET_CONFIG basic setting;
- Name of target board to use in target configuration may be set through TARGET_BOARD basic setting;
- Name of target CPU to use in target configuration may be set through TARGET_CPU basic setting;
To find the correct BOARD and CPU edit the ccxml from eclipse debugger then look at the advanced tab to see BOARD and CPU
usually the BAOARD is the ccxmlFile.connection.desc and CPU is ccxmlFile.cpu.desc if exist or ccxmlFile.instance.href->cpu.desc
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinccs6F28027XDS100.xdp
|
C
|
Component Testing - coverage, trace
|
Windows 7
|
TMS320 C/C++ C2000v6.4.2
|
TMS320 C2000v6.4.2
|
Code Composer Studio Version 6.1.3
|
None
|
Texas Instruments F2802x CPU
|
For v8.0.1
Support:
-------------
Language : C
Features : Component Testing - coverage, trace
Tested Against:
------------------------
Host Machine : Windows 7
Compiler : TMS320 C/C++ Compiler C2000v6.4.2
Linker : TMS320 Linker C2000v6.4.2
Debugger : Code Composer Studio Version 6.1.3
OS : None
Target : Texas Instruments F2802x CPU
Note:
---------
C++ support not implemented.
Execution through the CCS debugger supports data retrieval (RTRT_IO) modes:
- RTRT_USR: Host file I/O mode (if debugger 'CIO' support is supported/enabled on target).
- RTRT_NONE: breakpoint mode (debugger scripting).
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting.
- Path of directives file to use with linker may be set through TARGET_LINKER_CMD basic setting;
- Path of CCS 5 target configuration file to use for execution may be set through TARGET_CONFIG basic setting;
- Name of target board to use in target configuration may be set through TARGET_BOARD basic setting;
- Name of target CPU to use in target configuration may be set through TARGET_CPU basic setting;
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwince.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Microsoft eMbedded Visual Tools 4.0
|
Microsoft eMbedded Visual Tools 4.0
|
Microsoft eMbedded Visual Tools 4.0
|
Windows CE .NET
|
Windows CE 4.0 emulator
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.49.4.9 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Microsoft eMbedded Visual Tools 4.0
Linker : Microsoft eMbedded Visual Tools 4.0
Debugger : Microsoft eMbedded Visual Tools 4.0
OS : Windows CE .NET
Target : Windows CE 4.0 emulator
This TDP has been tested on Microsoft eMbedded Visual Tools 4.0 and targets Windows CE 4.0 emulator.
Some adaptations must be made in the Basic Settings for other targets. Especially, change the value for CPU in Basic Settings::For C, even if you're testing C++ code.
You may need to change the way test results are uploaded from the target to the host machine. In that case, please modify the customized usr_open, usr_writeln and usr_close functions in Library Settings::Data retrieval and Error message output::Data retrieval.
2 ways are already defined TCP/IP socket upload and file system.
the default is TCP/IP, to use file system change the FILE_SYSTEM_MODE value in the TDP Basic settings to 1 and SOCKET_UPLOAD to false
You may need to update the Execution Function in Build Settings, especially the part concerning the way to download the executable on the target.
|
|
cwince5.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Microsoft eMbedded Visual Tools 5.0
|
Microsoft eMbedded Visual Tools 5.0
|
Microsoft eMbedded Visual Tools 5.0
|
Windows CE .NET
|
Windows CE 5.0 x86 emulator
|
For v2003.06.15 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.31.4.10 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Microsoft eMbedded Visual Tools 5.0
Linker : Microsoft eMbedded Visual Tools 5.0
Debugger : Microsoft eMbedded Visual Tools 5.0
OS : Windows CE .NET
Target : Windows CE 5.0 x86 emulator
This TDP has been tested on Microsoft eMbedded Visual Tools 5.0 and targets Windows CE 5.0 x86 emulator.
Some adaptations must be made in the Basic Settings for other targets. Especially, change the value for CPU in Basic Settings::For C, even if you're testing C++ code.
You may need to change the way test results are uploaded from the target to the host machine. In that case, please modify the customized usr_open, usr_writeln and usr_close functions in Library Settings::Data retrieval and Error message output::Data retrieval.
2 ways are already defined TCP/IP socket upload and file system.
the default is TCP/IP, to use file system change the FILE_SYSTEM_MODE value in the TDP Basic settings to 1 and SOCKET_UPLOAD to false
You may need to update the Execution Function in Build Settings, especially the part concerning the way to download the executable on the target.
When using the FILE_SYSTEM_MODE, test result file (atlout.spt) must be retrieved manually from target to host. To do that, import this file in the temporary directory of the TestRT project (by default named cwince5) thanks to the Windows CE Remote File Viewer. Then the imported file will be automatically postprocessed by studio.
DEFAULT_LIBRARY_PATHS Basic Settings For C/C++ :
This setting is not specified as it is user dependant. It should be equal to the path where the sysgen tool generates the .lib files that correspond to the functionality of your customized Windows CE OS. When using studio, this path is mandatory. It is recommended to specify it for each TestRT project (Settings->Build->Linker->Library paths) instead of changing the template value of the xdp file.
|
|
cwince6.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows XP
|
Microsoft eMbedded Visual Tools 6.0
|
Microsoft eMbedded Visual Tools 6.0
|
Microsoft eMbedded Visual Tools 6.0
|
Windows CE
|
Windows CE 6.0 on ARM
|
For v2009 TDP Release 7.5.0.3
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.1.2.2 $ by RF/FL
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows XP
Compiler : Microsoft eMbedded Visual Tools 6.0
Linker : Microsoft eMbedded Visual Tools 6.0
Debugger : Microsoft eMbedded Visual Tools 6.0
OS : Windows CE
Target : Windows CE 6.0 on ARM
- This TDP has been tested on Microsoft eMbedded Visual Tools 6.0 and targets Windows CE 6.0 custom env running on ARM V4i.
Some adaptations must be made in the Basic Settings for other targets. Especially, change the value for CPU Basic Setting.
- You may need to change the way test results are uploaded from the target to the host machine.
In that case, please modify the customized usr_open, usr_writeln and usr_close data retrieval functions in Library Settings::Data retrieval and usr_error function in Library Settings::Error message output.
- 2 data retrieval modes are currently supported:
- File system mode: set SOCKET_UPLOAD Basic Setting to false and Data retrieval::RTRT_IO Library Setting to RTRT_STD.
- TCP/IP (socket) upload mode: set SOCKET_UPLOAD Basic Setting to true and Data retrieval::RTRT_IO Library Setting to RTRT_USR (this curently selects the customized Windows socket I/O based data retrieval functions).
- When using file system mode, test traces file (atlout.spt) must be retrieved manually from target to host. To do that, import this file in the temporary directory of the TestRT project (by default named cwince6) thanks to the Windows CE Remote File Viewer. Then the imported file will be automatically postprocessed by studio.
You may also need to update the Execution Function in Build Settings, especially the part handling the download of the executable to the target.
- DEFAULT_LIBRARY_PATHS Basic Settings For C/C++ :
This setting is normally not specified as it is project-dependant. It should be equal to the path where the sysgen tool generates the .lib files that correspond to the functionality of your customized Windows CE OS.
When using Studio, this path is mandatory. It is recommended to specify it for each TestRT project (Settings->Build->Linker->Library paths) instead of changing the template value in the TDP.
- MS Visual Studio 2005 /WinCE Platform builder 6.0 integration.
This TDP supports an integration with Visual Studio to allow instrumented builds (for standalone runtime Analysis) from Visual Studio,
through 2 menu items that are installed (when TDP's INSTALL_PLUGIN Basic setting is set to TRUE) as 'external tools' in the Visual Studio 'Tools' menu
- IBM Rational Test RealTime for CE 6.0 Options...
This allows to setup instrumentation options, and disable/enable instrumentation for a given build context (directory tree): when instrumentation is enabled, all makefiles found in this directory tree are setup to point to the 'instrumented' version (makefileRT.def) of the WinCE master makefile (makefile.def).
- IBM Rational Test RealTime for CE 6.0 View Reports
This allows, for a given build context (directory tree), after execution traces atlout.spt are copied to the root of the tree, to view runtime analysis reports for all instrumented files (for which static trace files were generated at build time) found in this directory tree.
|
|
cwincwhcs12x.xdp
|
C
|
Component Testing - Code Coverage - Memory profiling (standard malloc()/free()) - Performance profiling (if clock() available))
|
Windows 2000/XP
|
CodeWarrior ANSI-C/cC++ for HC12 V-5.0.32
|
CodeWarrior Smart V-5.0.29
|
CodeWarrior Hiwave Version 6.1
|
None
|
MC9S12XS128 (Full chip simulator & P&E Multilink probe)
|
For v7.0.x
$Revision: 1.28 - FL 2008/2/5 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage - Memory profiling (standard malloc()/free()) - Performance profiling (if clock() available))
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : CodeWarrior ANSI-C/cC++ Compiler for HC12 V-5.0.32
Asssembler : CodeWarrior Assembler for HC12 V-5.0.29
Linker : CodeWarrior SmartLinker V-5.0.29
Debugger : CodeWarrior Hiwave Debugger Version 6.1
OS : None
Target : MC9S12XS128 (Full chip simulator & P&E Multilink probe)
Note:
---------
C++ support not implemented.
Data retrieval (RTRT_IO) mode supported with Hiwave:
- RTRT_NONE : breakpoint mode (debugger scripting based);
- RTRT_USR : Host file I/O mode (through debugger simulated I/O - only on Simulator)
TDP specific basic settings:
-------------------------------------------
- Paths of startup/runtime support files to compile/link with executable may be set through TARGET_STARTUP basic setting.
- Path of command file to use with linker may be set through TARGET_CONFIG basic setting.
- Target for debugger execution may be set through TARGET basic setting ('sim' for Simulator, 'icd12' for P&E Multilink probe)
- Path of Hiwave "project" initialization file may be set through TARGET_INIT basic setting.
- Path of Hiwave "layout" file may be set through TARGET_LAYOUT basic setting.
-Execution timeout (maximum execution time in seconds) may be set through TARGET_TIMEOUT basic setting.
Note: These settings may be overriden by environment variables of same name.
|
|
cwindiabppcocd.xdp
|
C
|
Component Testing - Code Coverage
|
Windows 2000/XP
|
WindRiver Diab C/C++ Rel 5.5.1/5.6.0
|
WindRiver Diab Rel 5.5.1/5.6.0
|
WindRiver Workbench 3.1 OCD (hostShell gdb)
|
None
|
PowerPC (PPC8270)
|
For vv7.0.x
$Revision: 1.4 - FL 2009/3/30 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : WindRiver Diab C/C++ Compiler Rel 5.5.1/5.6.0
Asssembler : WindRiver Diab Assembler Rel 5.5.1/5.6.0
Linker : WindRiver Diab Linker Rel 5.5.1/5.6.0
Simulator : WindRiver WindISS Simulator Rel 5.5.1/5.6.0
Debugger : WindRiver Workbench 3.1 OCD (hostShell gdb)
OS : None
Target : PowerPC (PPC8270)
Note:
---------
C++ support not implemented.
Data retrieval (RTRT_IO) modes supported with WindISS:
- RTRT_USR: user I/O mode (printf-based terminal I/O);
- RTRT_STD: standard I/O mode (fprintf-based host file I/O).
Data retrieval (RTRT_IO) modes supported with OCD debugger:
- RTRT_NONE: breakpoint mode (debugger scripting).
TDP specific basic settings:
-------------------------------------------
For build with Diab toolchain:
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting.
For OCD execution:
- Type of target CPU may be set through OCD_CORE basic setting;
- Name of CPU plugin may be set through OCD_CPUPLUGIN basic setting;
- Device type ('ISS' or 'Probe') may be set through OCD_DEVICE basic setting;
- Connection style for device (not applicable for 'ISS') may be set through OCD_DEVICESTYLE basic setting;
- Connection address for device (not applicable for 'ISS') may be set through OCD_DEVICEADDR basic setting;
- Path of register file for target configuration may be set through OCD_REGFILE basic setting.
Note: These settings may be overriden by environment variables of same name.
|
|
cwindiabsgstep.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
DiabData C/C++ Version 4.4a
|
DiabData Version 4.4a
|
SingleStep for PowerPC Version 7.66
|
None
|
PowerPC 604 Simulator
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.38.4.9 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : DiabData C/C++ Compiler Version 4.4a
Linker : DiabData Linker Version 4.4a
Debugger : SingleStep Debugger for PowerPC Version 7.66
OS : None
Target : PowerPC 604 Simulator
|
|
cwinghsintppcdy179.xdp
|
C
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Runtime Trace
|
Windows 2000/XP
|
GreenHills C-POWERPC 4.0.6
|
GreenHills ELXR 4.0
|
GreenHills Multi Version 4.0.7
|
GreenHills Integrity 4.0.10
|
PPC DY-179 board
|
For v7.0.0
$Revision: 1.28 - FL 2007/06/7 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Runtime Trace
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : GreenHills C-POWERPC 4.0.6
Linker : GreenHills ELXR 4.0
Debugger : GreenHills Multi Debugger Version 4.0.7
OS : GreenHills Integrity 4.0.10
Target : PPC DY-179 board
Note:
---------
C++ support not implemented.
Execution through the Multi debugger supports retrieval (RTRT_IO) modes:
- RTRT_STD: standard I/O mode (fprintf-based host file I/O - may not be supported in some Integrity kernel configurations).
- RTRT_USR: user I/O mode (printf-based terminal I/O - may not be supported in some Integrity kernel configurations);
- RTRT_NONE: breakpoint mode (debugger scripting).
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting;
- Flags to be used for Integrate Post-linker may be set through INTEGRATE_FLAGS basic setting;
- Path of BSP file for Integrate post-linker may be set through INTEGRATE_BSPFILE basic setting;
- Target hostname/IP address and port number may be set through TARGET basic setting.
- Target connection command for Multi debugger may be set through TARGET_CONNECTION basic setting.
- Target connect/setup script to use with Multi debugger may be set through TARGET_SETUP basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinghsnecv850.xdp
|
C
|
Component Testing - Code Coverage
|
Windows 2000/XP
|
GreenHills C/C++ C-V850E 5.1.7
|
GreenHills ELXR 5.0
|
GreenHills Multi v5.1.7 V800
|
None
|
Nec V850 Simulator/ICE
|
For 7.5.0.4 Release
$Revision: 1.7 2010/1/22 FL $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : GreenHills C/C++ Compiler C-V850E 5.1.7
Linker : GreenHills Linker ELXR 5.0
Debugger : GreenHills Multi Debugger v5.1.7 V800
Simulator : GreenHills Simulator SIM-V850 5.0
OS : None
Target : Nec V850 Simulator/ICE
Note:
---------
C++ support not implemented.
Execution through the Multi debugger supports retrieval (RTRT_IO) modes:
- RTRT_STD: standard I/O mode (fprintf-based host file I/O);
- RTRT_USR: user I/O mode (printf-based terminal I/O);
- RTRT_NONE: breakpoint mode (debugger scripting).
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting;
- Target connection command for Multi debugger may be set through TARGET_CONNECTION basic setting;
- Path of target device file to use for emulator connection may be set through TARGET_DEVICE_FILE basic setting;
- Target breakpoint type to use with Multi debugger may be set through TARGET_BREAKPOINTS basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinhttricore.xdp
|
C
|
Component Testing - Code Coverage
|
Windows
|
HighTec TriCore gcc 2.8 (3.4.5.1)
|
HighTec TriCore ld 5.1 (3.4.5.1)
|
HighTec TriCore gdb 6.1 (3.4.5.1)
|
None
|
Infineon TriCore TC1766 Simulator
|
For v7.0.x
$Revision: 1.4 - FL 2009/6/6 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : HighTec TriCore gcc 2.8 (3.4.5.1)
Linker : HighTec TriCore ld 5.1 (3.4.5.1)
Debugger : HighTec TriCore gdb 6.1 (3.4.5.1)
OS : None
Target : Infineon TriCore TC1766 Simulator
Note:
---------
C++ support not implemented.
Data retrieval (RTRT_IO) modes supported with TriCore debugger
- RTRT_NONE: breakpoint mode (debugger scripting)
- RTRT_USR: user I/O mode (using debugger virtual I/O)
- RTRT_STD: standard I/O mode (using debugger virtual I/O)
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting.
- Host for TriCore target or simulator may be set through TARGET_HOST basic setting.
- Port for TriCore target or simulator may be set through TARGET_PORT basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwiniar8051.xdp
|
C
|
Component Testing - Code Coverage
|
Windows XP
|
IAR C/C++ V7.60.1.10026 for 8051
|
IAR Universal V4.61T/W32
|
CspyBat (IAR C-SPY Command Line Utility) V5.6.2.0
|
None
|
IAR C-SPY Simulator Driver for 8051 7.60.1 (7.60.1.10026)
|
For v7.0.5.x
$Revision: 1.0 - FL 2010/12/1 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows XP
Compiler : IAR C/C++ Compiler V7.60.1.10026 for 8051
Linker : IAR Universal Linker V4.61T/W32
Debugger : CspyBat (IAR C-SPY Command Line Utility) V5.6.2.0
OS : None
Target : IAR C-SPY Simulator Driver for 8051 7.60.1 (7.60.1.10026)
Note:
---------
C++ support not implemented.
Execution through the C-Spy debugger supports all data retrieval (RTRT_IO) modes:
- RTRT_NONE: breakpoint mode (debugger scripting);
- RTRT_USR: user I/O mode (printf-based terminal I/O);
- RTRT_STD: standard I/O mode (fprintf-based host file I/O).
The modes effectively supported in a given configuration depend on the IAR 8051 runtime library used:
- no (minimal) library: RTRT_NONE only (RTRT_USR possible if library provides printf support)
- CLIB: RTRT_NONE and RTRT_USR
- Normal DLIB: RTRT_NONE and RTRT_USR
- Full DLIB: RTRT_NONE, RTRT_USR.
Note: no RTRT_STD support with IAR 8051 Full DLIB, since it seems to lack host file I/O support...
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting;
- Target debugger driver to use for execution may be set through TARGET_DRIVER basic setting
('sim' for Simulator);
- Path of CPU device description file to use for execution thru C-Spy debugger may be set through TARGET_DDF basic setting;
- Target layout options for the target debugger driver may be set through TARGET_LAYOUT basic setting
(they should be kept consistent with equivalent options in DEFAULT_CFLAGS/DEFAULT_LDFLAGS compiler/linker options).
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwiniarCortex.xdp
|
C
|
Component Testing - Code Coverage
|
Windows
|
IAR ANSI C/C++ V6.40.3.54009/W32 for ARM
|
IAR ELF V6.40.3.54009/W32 for ARM
|
IAR C-SPY
|
None
|
IAR C-SPY Simulator Driver
|
$Revision: 1.0 - RF 2012/09 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : IAR ANSI C/C++ Compiler V6.40.3.54009/W32 for ARM
Linker : IAR ELF Linker V6.40.3.54009/W32 for ARM
Debugger : IAR C-SPY Debugger
OS : None
Target : IAR C-SPY Simulator Driver
Note:
---------
C++ support not implemented.
Execution through the C-Spy debugger supports all data retrieval (RTRT_IO) modes:
- RTRT_NONE: breakpoint mode (debugger scripting);
- RTRT_USR: user I/O mode (printf-based terminal I/O);
- RTRT_STD: standard I/O mode (fprintf-based host file I/O).
The modes effectively supported in a given configuration depend on the IAR runtime library used:
- no (minimal) library: RTRT_NONE only (RTRT_USR possible if library provides printf support)
- CLIB: RTRT_NONE and RTRT_USR
- Normal DLIB: RTRT_NONE and RTRT_USR
- Full DLIB: RTRT_NONE, RTRT_USR and RTRT_STD.
cspybat
"C:\Program Files\IAR Systems\Embedded Workbench 5.4_2\arm\bin\armproc.dll"
"C:\Program Files\IAR Systems\Embedded Workbench 5.4_2\arm\bin\armjlink.dll"
%1
--plugin "C:\Program Files\IAR Systems\Embedded Workbench 5.4_2\arm\bin\"
--flash_loader "C:\Program Files\IAR Systems\Embedded Workbench 5.4_2\arm\config\flashloader\Atmel\AT91SAM3S4-EK\at91sam3s4-flash.board"
--backend
-B
"--endian=little"
"--cpu=Cortex-M3"
"--fpu=None"
"-p" "C:\Program Files\IAR Systems\Embedded Workbench 5.4_2\arm\CONFIG\debugger\Atmel\ioat91sam3s4.ddf"
"--semihosting"
"--device=AT91SAM3S4"
"-d" "jlink"
"--drv_communication=USB0"
"--jlink_speed=auto"
"--jlink_initial_speed=32"
"--jlink_reset_strategy=0,0"
|
|
cwiniardspic.xdp
|
C
|
Component Testing - Code Coverage
|
Windows XP
|
IAR dsPIC C/EC++ V1.40A/W32
|
IAR Universal V4.61C/386
|
CspyBat (IAR C-SPY Command Line Utility) V5.1.1.0
|
None
|
IAR C-SPY Batch Simulator Driver for DSPIC V1.40A/W32
|
For v7.0.5.x
$Revision: 1.0 - FL 2010/6/10 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows XP
Compiler : IAR dsPIC C/EC++ Compiler V1.40A/W32
Linker : IAR Universal Linker V4.61C/386
Debugger : CspyBat (IAR C-SPY Command Line Utility) V5.1.1.0
OS : None
Target : IAR C-SPY Batch Simulator Driver for DSPIC V1.40A/W32
Note:
---------
C++ support not implemented.
Execution through the C-Spy debugger supports all data retrieval (RTRT_IO) modes:
- RTRT_NONE: breakpoint mode (debugger scripting);
- RTRT_USR: user I/O mode (printf-based terminal I/O);
- RTRT_STD: standard I/O mode (fprintf-based host file I/O).
The modes effectively supported in a given configuration depend on the IAR dsPIC runtime library used:
- no (minimal) library: RTRT_NONE only (RTRT_USR possible if library provides printf support)
- CLIB: RTRT_NONE and RTRT_USR
- Normal DLIB: RTRT_NONE and RTRT_USR
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting;
- Target debugger driver to use for execution may be set through TARGET_DRIVER basic setting
('sim' for Simulator, 'emuRealIce' for MPLAB REAL ICE);
- Path of CPU device description file to use for execution thru C-Spy debugger may be set through TARGET_DDF basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwiniarnec78k.xdp
|
C
|
Component Testing - Code Coverage
|
Windows XP
|
IAR C/C++ V4.62.1.20009/W32 for 78K0 and 78K0S
|
IAR Universal V4.61N/W32
|
CspyBat (IAR C-SPY Command Line Utility) V5.5.0.0
|
None
|
IAR C-SPY Simulator Driver for NEC 78K0 and 78K0S 4.62.1.20009
|
For v7.0.5.x
$Revision: 1.0 - FL 2010/6/2 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows XP
Compiler : IAR C/C++ Compiler V4.62.1.20009/W32 for 78K0 and 78K0S
Linker : IAR Universal Linker V4.61N/W32
Debugger : CspyBat (IAR C-SPY Command Line Utility) V5.5.0.0
OS : None
Target : IAR C-SPY Simulator Driver for NEC 78K0 and 78K0S 4.62.1.20009
Note:
---------
C++ support not implemented.
Execution through the C-Spy debugger supports all data retrieval (RTRT_IO) modes:
- RTRT_NONE: breakpoint mode (debugger scripting);
- RTRT_USR: user I/O mode (printf-based terminal I/O);
- RTRT_STD: standard I/O mode (fprintf-based host file I/O).
The modes effectively supported in a given configuration depend on the IAR runtime library used:
- no (minimal) library: RTRT_NONE only (RTRT_USR possible if library provides printf support)
- CLIB: RTRT_NONE and RTRT_USR
- Normal DLIB: RTRT_NONE and RTRT_USR
- Full DLIB: RTRT_NONE, RTRT_USR and RTRT_STD.
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting;
- Target debugger driver to use for execution may be set through TARGET_DRIVER basic setting
('sim' for Simulator or 'iecube' for IECUBE Emulator);
- Path of CPU device description file to use for execution thru C-Spy debugger may be set through TARGET_DDF basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinkeilc51.xdp
|
C
|
Component Testing - Code Coverage
|
Windows 2000/XP
|
Keil C51 V8.09
|
Keil BL51 /Locator V6.05
|
Uv3 (Keil uVision 3 V3.53)
|
None
|
Keil C51 simulator (S8051 DLL V3.12)
|
For v7.0.x
$Revision: 1.6 - FL 2010/1/29 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : Keil C51 Compiler V8.09
Asssembler : Keil A51 Macro Assembler V8.00d
Linker : Keil BL51 Linker/Locator V6.05
Debugger : Uv3 (Keil uVision 3 V3.53)
OS : None
Target : Keil C51 simulator (S8051 DLL V3.12)
Note:
---------
Data retrieval (RTRT_IO) mode supported with Uv3 debugger is:
- RTRT_NONE : breakpoint mode (debugger scripting based) (always available)
or - RTRT_USR : user I/O (serial I/O through debugger) (supported only on some devices).
TDP specific basic settings:
-------------------------------------------
- Intermediate command files are used for for Keil assembler/compiler invocations (to avoid command line length overflow problems)
if USE_KEIL_CMDFILE basic setting is defined.
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting.
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting.
- Path of template project for execution may be set through TARGET_PROJECT basic setting.
Note: These settings may be overriden by environment variables of same name.
|
|
cwinmccppct32.xdp
|
C
|
Component Testing - Code Coverage
|
Windows 2000/XP
|
Microtec PowerPC C/C++ Version 3.2A
|
Microtec PowerPC Version 3.2
|
Lauterbach Trace32 Simulator Build 7034 (Dec 18 2006)
|
None
|
PowerPC (PPC8270)
|
For v7.0.x
$Revision: 1.28 - FL 2008/2/18 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows 2000/XP
Compiler : Microtec PowerPC C/C++ Compiler Version 3.2A
Asssembler : Microtec PowerPC Assembler v3.2
Linker : Microtec PowerPC Linker Version 3.2
Debugger : Lauterbach Trace32 Simulator Build 7034 (Dec 18 2006)
OS : None
Target : PowerPC (PPC8270)
Note:
---------
C++ support not implemented.
Data retrieval (RTRT_IO) mode supported with Trace32:
- RTRT_NONE : breakpoint mode (debugger scripting based);
TDP specific basic settings:
-------------------------------------------
- Path of Trace32 target-specific initialization file may be set through TARGET_INIT basic setting.
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting.
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting.
Note: These settings may be overriden by environment variables of same name.
|
|
cwinmingw3_2.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Gnu 3.2 (mingw)
|
Gnu 3.2 (mingw)
|
Gnu 3.2 (mingw)
|
Native
|
Native
|
For v7.5
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.34.4.5 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Gnu Compiler 3.2 (mingw)
Linker : Gnu Linker 3.2 (mingw)
Debugger : Gnu Debugger 3.2 (mingw)
OS : Native
Target : Native
This target deployment port is adapted for the "Minimalist Gnu for Windows". This package can be downloaded from http://www.mingw.org/index.shtml
Depending on where you installed this package, you might need to update the following settings by changing the path C:\MinGW to the location where you installed the compiler:
- Basic Settings
- For ALL
ENV_PATH C:\MinGW\bin;$ENV{'PATH'}
|
|
cwinmplabdspic.xdp
|
C
|
Component Testing - Code Coverage - Performance Profiling - Trace
|
Windows
|
MPLAB dsPIC compiler (GCC) 4.0.3 (dsPIC30, Microchip v3.12)
|
MPLAB dsPIC linker (GCC) 4.0.3 (dsPIC30, Microchip v3.12)
|
None
|
None
|
Microchip dsPIC30 simulator [CLI v3.43.00.00]
|
For v7.0.x
$Revision: 1.3 - FL 2009/7/22 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage - Performance Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows
Compiler : MPLAB dsPIC compiler (GCC) 4.0.3 (dsPIC30, Microchip v3.12)
Linker : MPLAB dsPIC linker (GCC) 4.0.3 (dsPIC30, Microchip v3.12)
Debugger : None
OS : None
Target : Microchip dsPIC30 simulator [CLI v3.43.00.00]
Note:
---------
Data retrieval (RTRT_IO) modes supported with dsPIC simulator
- RTRT_USR: user I/O mode (using simulator's simulated file I/O)
TDP specific basic settings:
-------------------------------------------
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting;
- Path of directives file to use with linker may be set through TARGET_CONFIG basic setting.
- Device for dsPIC simulator may be set through TARGET_DEVICE basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinmulti.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
GreenHills C/C++ Version 3.0
|
GreenHills Version 3.0
|
Multi 2000 Version 3.0
|
None
|
PowerPC Simulator
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.33.4.12 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : GreenHills C/C++ Compiler Version 3.0
Linker : GreenHills Linker Version 3.0
Debugger : Multi 2000 Version 3.0
OS : None
Target : PowerPC Simulator
|
|
cwinrvctarm.xdp
|
C
|
Component Testing - Code Coverage
|
Windows
|
RVCT ARM C/C++ , 4.1 [Build 561]
|
RVCT ARM , 4.1 [Build 561]
|
ARM RealView v4.1.1 or Lauterbach Trace32 for ARM (R.2010.04.000025064)
|
None
|
Cortex-M3 (RealView ISSM or Trace32 simulator)
|
For v7.5.0.3
$Revision: 1.3 - 2010/12/21 $
Support:
-------------
Language : C
Features : Component Testing - Code Coverage
Tested Against:
------------------------
Host Machine : Windows
Compiler : RVCT ARM C/C++ Compiler, 4.1 [Build 561]
Linker : RVCT ARM Linker, 4.1 [Build 561]
Debugger : ARM RealView v4.1.1 or Lauterbach Trace32 for ARM (R.2010.04.000025064)
OS : None
Target : Cortex-M3 (RealView ISSM or Trace32 simulator)
Note:
---------
C++ support not implemented.
Data retrieval (RTRT_IO) modes supported with RealView:
- RTRT_NONE: breakpoint mode (debugger scripting based);
- RTRT_USR: user I/O mode (printf-based terminal I/O thru debugger 'semihosting' support - with microlib or standardlib);
- RTRT_STD: standard I/O mode (fprintf-based host file I/O thru debugger 'semihosting' support - with standardlib).
Data retrieval (RTRT_IO) modes supported with Trace32:
- RTRT_NONE: breakpoint mode (debugger scripting based);
- RTRT_USR: user I/O mode (printf-based terminal I/O thru debugger 'semihosting' support - with standardlib (buggy with microlib) );
- RTRT_STD: standard I/O mode (fprintf-based host file I/O thru debugger 'semihosting' support - with standardlib).
TDP specific basic settings:
-------------------------------------------
For RVCT toolchain:
- Path of startup file to compile/link with executable may be set through TARGET_STARTUP basic setting.
- Path of directives (scatter) file to use with linker may be set through TARGET_CONFIG basic setting.
For RealView debugger:
- Target connection for ARM RealView debugger may be set through TARGET_RVD_CONNECTION basic setting.
For Trace32 debugger:
- Path of Trace32 target-specific initialization script may be set through TARGET_T32_INIT basic setting.
- Path of Trace32 target-specific executable load script may be set through TARGET_T32_LOAD basic setting.
Note: These TDP specific basic settings may be overriden by environment variables of same name.
|
|
cwinvx386.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Gnu 2.7
|
Gnu 2.7
|
Tornado II
|
VxWorks 5.4
|
Intel x86
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.76.4.4 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Gnu Compiler 2.7
Linker : Gnu Linker 2.7
Debugger : Tornado II
OS : VxWorks 5.4
Target : Intel x86
This target deployment port is adapted for VxWorks 5.4 running on an Intel x86 board.
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME [@hostname]
DEFAULT_DEFINES CPU=,.....
COMPILER,LINKER,DEBUGGER,NM cc,ld,gdb,nm
This TDP uses the WTX API from WindRiver to collect test results. The name of the program is rtrtWtx2.exe.
Usage: "rtrtwtx2 [options]" where options can be one or more of the following:
-entry : Name of the function to start the application
-list or .lst file
-load : Load then execute the objects listed in -list option
-unload : After execution, unload the objects listed in -list option
-out : Name of the default out.spt file written
-notraces : Do not get result file from target
-t : Name of the VxWorks target to attach to
-a : Files opened in append mode
-v : Debug/verbose mode
-b : Stops when the program exits
-delay : Try every second for seconds to attach to the target
The source code for rtrtWtx2 can be found in this TDP so you can recompile it if needed.
Note that if you execute the code wdbUserEvtPost("RTRTENDS"); on the target, it will automatically close all the the result files opened on the host machine.
|
|
cwinvx386T22.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Gnu 2.95
|
Gnu 2.95
|
Tornado 2.2
|
VxWorks 5.5
|
Intel x386
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.57.4.4 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Gnu Compiler 2.95
Linker : Gnu Linker 2.95
Debugger : Tornado 2.2
OS : VxWorks 5.5
Target : Intel x386
This target deployment port is adapted for VxWorks 5.4 running on an Intel x86 board.
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME [@hostname]
DEFAULT_DEFINES CPU=,.....
COMPILER,LINKER,DEBUGGER,NM cc,ld,gdb,nm
This TDP uses the WTX API from WindRiver to collect test results. The name of the program is rtrtWtx2.exe.
Usage: "rtrtwtx2 [options]" where options can be one or more of the following:
-entry : Name of the function to start the application
-list or .lst file
-load : Load then execute the objects listed in -list option
-unload : After execution, unload the objects listed in -list option
-out : Name of the default out.spt file written
-notraces : Do not get result file from target
-t : Name of the VxWorks target to attach to
-a : Files opened in append mode
-v : Debug/verbose mode
-b : Stops when the program exits
-delay : Try every second for seconds to attach to the target
The source code for rtrtWtx2 can be found in this TDP so you can recompile it if needed.
Note that if you execute the code wdbUserEvtPost("RTRTENDS"); on the target, it will automatically close all the the result files opened on the host machine.
|
|
cwinvxppc.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Gnu 2.7
|
Gnu 2.7
|
Tornado II
|
VxWorks 5.4
|
PowerPC 603
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.73.4.4 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Gnu Compiler 2.7
Linker : Gnu Linker 2.7
Debugger : Tornado II
OS : VxWorks 5.4
Target : PowerPC 603
This target deployment port is adapted for VxWorks 5.4 running on a Power PC board.
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME
DEFAULT_DEFINES CPU=,.....
COMPILER,LINKER,DEBUGGER,NM cc,ld,gdb,nm
This TDP uses the WTX API from WindRiver to collect test results. The name of the program is rtrtWtx2.exe.
Usage: "rtrtwtx2 [options]" where options can be one or more of the following:
-entry : Name of the function to start the application
-list or .lst file
-load : Load then execute the objects listed in -list option
-unload : After execution, unload the objects listed in -list option
-out : Name of the default out.spt file written
-notraces : Do not get result file from target
-t : Name of the VxWorks target to attach to
-a : Files opened in append mode
-v : Debug/verbose mode
-b : Stops when the program exits
-delay : Try every second for seconds to attach to the target
The source code for rtrtWtx2 can be found in this TDP so you can recompile it if needed.
Note that if you execute the code wdbUserEvtPost("RTRTENDS"); on the target, it will automatically close all the the result files opened on the host machine.
|
|
cwinvxsim.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Gnu 2.7
|
Gnu 2.7
|
Tornado II
|
VxWorks 5.4
|
VxSim
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.81.4.4 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Gnu Compiler 2.7
Linker : Gnu Linker 2.7
Debugger : Tornado II
OS : VxWorks 5.4
Target : VxSim
This target deployment port is adapted for the use of the VxSim simulator running VxWorks 5.4.
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME vxsim[@hostname]
DEFAULT_DEFINES CPU=,.....
COMPILER,LINKER,DEBUGGER,NM cc,ld,gdb,nm
This TDP uses the WTX API from WindRiver to collect test results. The name of the program is rtrtWtx2.exe.
Usage: "rtrtwtx2 [options]" where options can be one or more of the following:
-entry : Name of the function to start the application
-list or .lst file
-load : Load then execute the objects listed in -list option
-unload : After execution, unload the objects listed in -list option
-out : Name of the default out.spt file written
-notraces : Do not get result file from target
-t : Name of the VxWorks target to attach to
-a : Files opened in append mode
-v : Debug/verbose mode
-b : Stops when the program exits
-delay : Try every second for seconds to attach to the target
The source code for rtrtWtx2 can be found in this TDP so you can recompile it if needed.
Note that if you execute the code wdbUserEvtPost("RTRTENDS"); on the target, it will automatically close all the the result files opened on the host machine.
|
|
cwinvxsimT22.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Gnu 2.95
|
Gnu 2.95
|
Tornado 2.2
|
VxWorks 5.5
|
VxSim
|
For v2003.06.13 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.58.4.4 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Gnu Compiler 2.95
Linker : Gnu Linker 2.95
Debugger : Tornado 2.2
OS : VxWorks 5.5
Target : VxSim
This target deployment port is adapted for VxWorks 5.4 running on an Intel x86 board.
Adapt the following setting, representing the target IP address or name:
- Basic Settings
- For C and For C++:
TARGETNAME [@hostname]
DEFAULT_DEFINES CPU=,.....
COMPILER,LINKER,DEBUGGER,NM cc,ld,gdb,nm
This TDP uses the WTX API from WindRiver to collect test results. The name of the program is rtrtWtx2.exe.
Usage: "rtrtwtx2 [options]" where options can be one or more of the following:
-entry : Name of the function to start the application
-list or .lst file
-load : Load then execute the objects listed in -list option
-unload : After execution, unload the objects listed in -list option
-out : Name of the default out.spt file written
-notraces : Do not get result file from target
-t : Name of the VxWorks target to attach to
-a : Files opened in append mode
-v : Debug/verbose mode
-b : Stops when the program exits
-delay : Try every second for seconds to attach to the target
The source code for rtrtWtx2 can be found in this TDP so you can recompile it if needed.
Note that if you execute the code wdbUserEvtPost("RTRTENDS"); on the target, it will automatically close all the the result files opened on the host machine.
|
|
cxWinUnixGnu.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
|
gcc on remote machine
|
gcc on remote machine
|
gdb on remote machine
|
Unix
|
Native
|
For v8.0.0 Release and later
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2015-2017 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
--------------
Host machine : Windows
Compiler : gcc on remote machine
Linker : gcc on remote machine
Debugger : gdb on remote machine
OS : Unix
Target : Native
Notes for this "cross" TDP:
--------------------------
This TDP intend to use a compiler located on remote machine, and execute on the remote machine as well.
To get the preprocessor script code generator (attolprepro/atoprepro) working it require to have a copy of used header files on the Host machine or share the location where the compiler and the project files are installed.
To be able to compile theTestRT runtime TP.c[pp] properly the TDP/lib files must be copied from the TDP "generated in" directory to the remote machine. To let the postGen.pl doing this task the connection to shared space and ssh connection must be available when saving the TDP.
STD_INCLUDE (basic settings) is then include path for standard include or compiler include path of the remote machine
HOST_INCLUDE is the same for copied inlude on the host.
- all TestRT operations (studio GUI, test script pre-processing, source instrumentation, report post-processing) execute on the 'local' (typically
Windows but possibly UNIX/Linux) host.
- but all compiler operations (C/C++ sources preprocessing and compilation, link and execution) execute on the 'remote' Linux host.
This TDP relies on file sharing between the local and remote host (typically by mounting of Samba or NFS shares from the remote host on the local host).
It uses the following specific basic settings, that have to be adapted as needed:
- REMOTE_CONNECTION : remote connection method: rsh or ssh or putty or plink or .... (if not set, rsh will be used).
- REMOTE_HOST : hostname of the remote host (may be overriden by environment variable of same name).
Note: if this is not set or is the local hostname, the TDP will run in 'local' mode, and should then behave exactly as the standard 'clinuxgnu' TDP.
In this case, the other cross specific basic settings will not be used.
- REMOTE_USER : username used for command invocation (through 'rsh') on remote host (may be overriden by environment variable of same name.)
Note: if not set, local username will be used.
- REMOTE_TARGETDIR : path where the TDP target directory is installed on the remote host.
Note: this installation does not need to be complete: only the $TARGETDIR/lib directory is needed (to access TDP library sources).
If the full TDP is installed on the remote host, it may be used in 'local' mode on this host.
- REMOTE_SYS_INCL : path of the 'system directory' (containing standard include files and libraries) on the remote host.
- LOCAL_SYS_INCL : name of the share (Samba UNC path or drive letter, or NFS mount point) on which REMOTE_SYS_DIR is mounted on local host.
- SHARED_REMOTE_DIR : path of the user directory' (containing test projects and scripts and source files) on the remote host.
- SHARED_HOST_DIR : name of the share (Samba UNC path or drive letter, or NFS mount point) on which SHARED_REMOTE_DIR is mounted on local host.
the net use command is assumed to be active for this couple of SHARED_XXX_DIR
|
|
cxlinuxgnu.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
|
gcc version 3.2 to 4.1
|
gcc version 3.2 to 4.1
|
GNU gdb Linux (5.2.1-4 / 5.3)
|
Native
|
Native
|
For v7.0.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.33.4.7 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
--------------
TestRT Host machine : Windows or UNIX/Linux (remote mode) or Linux (local mode)
Compiler Host Machine : Linux Suse 8.1 - Linux RedHat 8.0
Compiler : gcc version 3.2 to 4.1
Linker : gcc version 3.2 to 4.1
Debugger : GNU gdb Linux (5.2.1-4 / 5.3)
OS : Native
Target : Native
Notes for this "cross" TDP:
--------------------------
This variant of the standard 'clinuxgnu' TDP is a proof of concept for a "cross" TDP, that is a TDP that drives a compiler on a remote host machine:
- all TestRT operations (studio GUI, test script pre-processing, source instrumentation, report post-processing) execute on the 'local' (typically
Windows but possibly UNIX/Linux) host.
- but all compiler operations (C/C++ sources preprocessing and compilation, link and execution) execute on the 'remote' Linux host.
This TDP relies on file sharing between the local and remote host (typically by mounting of Samba or NFS shares from the remote host on the local host).
It uses the following specific basic settings, that have to be adapted as needed:
- REMOTE_CONNECTION : remote connection method: rsh or ssh (if not set, rsh will be used).
- REMOTE_HOST : hostname of the remote host (may be overriden by environment variable of same name).
Note: if this is not set or is the local hostname, the TDP will run in 'local' mode, and should then behave exactly as the standard 'clinuxgnu' TDP.
In this case, the other cross specific basic settings will not be used.
- REMOTE_USER : username used for command invocation (through 'rsh') on remote host (may be overriden by environment variable of same name.)
Note: if not set, local username will be used.
- REMOTE_TARGETDIR : path where the TDP target directory is installed on the remote host.
Note: this installation does not need to be complete: only the $TARGETDIR/lib directory is needed (to access TDP library sources).
If the full TDP is installed on the remote host, it may be used in 'local' mode on this host.
- REMOTE_SYS_DIR : path of the 'system directory' (containing standard include files and libraries) on the remote host.
- LOCAL_SYS_SHARE : name of the share (Samba UNC path or drive letter, or NFS mount point) on which REMOTE_SYS_DIR is mounted on local host.
- REMOTE_USER_DIR : path of the user directory' (containing test projects and scripts and source files) on the remote host.
- LOCAL_USER_SHARE : name of the share (Samba UNC path or drive letter, or NFS mount point) on which REMOTE_USER_DIR is mounted on local host.
The changes made here to the base 'clinuxgnu' TDP, that rely on a set of utility routines provided in the 'remoteUtils.pl' perl script,
should be applicable to any other UNIX/Linux-based C/C++ TDP, to turn it into a "cross" TDP.
Notes from the base Linux version of this TDP:
---------------------------------------------
The attolcc launcher is migrating to a Perl script version, easier to modify. This attolcc.pl requires a perl launcher having the same baseName. So, we cannot have both: the old attolcc instrumenter launcher and the new attolcc perl launcher.
For ascendant compatibility the old attolcc instrumenter launcher is kept as the default launcher until the next version.
Usage of the attolcc launcher is still the same. Type 'attolcc -help' for more details.
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
|
|
czlinuxgnu.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
zLinux - Linux RedHat 4.0
|
gcc version 3.2 to 4.1
|
gcc version 3.2 to 4.1
|
GNU gdb Linux
|
Native
|
Native
|
For v7.0.0.0 Release
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.32.4.7 $
Support:
-------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------
Host Machine : zLinux - Linux RedHat 4.0
Compiler : gcc version 3.2 to 4.1
Linker : gcc version 3.2 to 4.1
Debugger : GNU gdb Linux
OS : Native
Target : Native
If you want to custom your own launcher, the following steps are necessary:
- Run the tdpeditor and open the corresponding xdp;
- Replace the content of attolcc.pl by the content of /lib/scripts/attolcc_gcc.pl or attolcc_cl.pl;
Thus, the user may change the behaviour of this launcher by modifying it.
For Memory Profiling, if memalign is used to dynamically allocate memory, please uncomment RTRT_memalign function in the "Memory Function Extensions" and "Macro Redefinition" tabs of Library Settings::Heap management configuration::Tracking user-defined or OS-dependant memory functions.
For a multi-threaded application, do not forget to add the '-pthread' option to the linker.
|
|
gccmingw_template_tutorial.xdp
|
C - C++
|
Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
|
Windows 2000
|
Gnu 3.2 (mingw)
|
Gnu 3.2 (mingw)
|
Gnu 3.2 (mingw)
|
Native
|
Native
|
For v7.5
IBM Rational Test RealTime
(c) Copyright IBM Corp. 2005-2016 All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017-2018. All Rights Reserved
$Revision: 1.1.4.5 $
Support:
-------------
Language : C - C++
Features : Component Testing - Code Coverage - Performance Profiling - Memory Profiling - Trace
Tested Against:
------------------------
Host Machine : Windows 2000
Compiler : Gnu Compiler 3.2 (mingw)
Linker : Gnu Linker 3.2 (mingw)
Debugger : Gnu Debugger 3.2 (mingw)
OS : Native
Target : Native
This target deployment port is a starting point to the TDP tutorial. Some part of this TDP have to be customised following's the instructions given by the TDP tutorial.
At the final step of the TDP tutorial this TDP is adapted for the "Minimalist Gnu for Windows". This package can be downloaded from http://www.mingw.org/index.shtml
It sould be finaly the same as gccmingw.xdp
|
|
templatea.xdp
|
|
|
|
|
|
|
|
|
For v2003.06.13
$Revision: 1.22.4.2 $
Support:
-------------
Language :
Features :
Tested Against:
------------------------
Host Machine :
Compiler :
Linker :
Debugger :
OS :
Target :
|
|
templatec.xdp
|
|
|
|
|
|
|
|
|
For v7.0.0 Release
$Revision: 1.32.4.3 $
Support:
-------------
Language :
Features :
Tested Against:
------------------------
Host Machine :
Compiler :
Linker :
Debugger :
OS :
Target :
|