Target deployment port overview

Target deployment port (TDP) technology is a versatile, low-overhead technology enabling target-independent tests and run-time analysis despite limitless target support.

As a key component of HCL OneTest™ Embedded, TDP technology allows your test cases as well as test execution analysis to be applied directly to your target embedded system. It is constructed to accommodate your compiler, linker, debugger, and target architecture. Tests are independent of the TDP, so tests don't change when the environment does. Test script deployment, execution and reporting remain easy to use.

TDPs are designed to strongly reduce the data communication and runtime overhead that can affect your embedded systems when tested, while being versatile enough to adapt to any cross-development environment (RTOS, compiler, debugger, target communication) within a very short time.

TDP technology includes the following capabilities and benefits:
  • Compiler dialect-aware and linker-aware, for transparent test building.
  • Easy download of the test harness environment onto the target via the user's IDE, debugger, simulator or emulator.
  • Painless test and run-time analysis results download from the target environment using JTAG probes, emulators or any available communication link, such as serial, Ethernet or file system.
  • Powerful test execution monitoring to distribute, start, synchronize and stop test harness components, as well as to implement communication and exception handling.
  • Versatile communication protocol adaptation to send and receive test messages.
  • XML-based Target Deployment Port Editor enabling simple, in-house TDP customization

Obtaining target deployment ports

TDP technology was designed to adapt to any embedded or native target platform. This means that you need a particular TDP to deploy HCL OneTest Embedded to your target. A wide array of TDPs has already been developed to suit most target platforms. The following platforms are already supported:
  • Native development platforms: Windows, Solaris, AIX® and Linux, the development platforms that leading companies in the devices/embedded systems and infrastructure industries are using.
  • Cross-development environments: From 8- to 64-bit cross-development environments from the likes of WindRiver, GreenHills, ARM, Sun, Montavista, TI, NEC, Hitachi, Nohau, and more.

Creating new target deployment ports

You can choose to create, unassisted, a TDP tailored for your embedded environment. There are several requirements to consider before choosing this option:
  • Perl language knowledge: The HCL OneTest Embedded compiler interface is written in perl
  • Programming language and compiler knowledge: The HCL OneTest Embedded runtime library uses the same language as the code under test (C, C++, Ada)
  • Knowledge of HCL OneTest Embedded: Improve your experience with the product before considering your first TDP. You will need to be familiar with the runtime analysis and component testing tools and how the TDP is used with them.

Before creating a TDP for a new target platform, determine whether the target platform is capable of running embedded tests. To create a TDP, see the documentation that is embedded in the Target Deployment Port Editor, which provides an overview and detailed information on setting up a TDP, and using the Target Deployment Port Editor.

Feedback