Both C++test standalone and the C++test Eclipse plugin allow C++test to be used with Keil MDK-ARM —no special integration is required. 

C++test doesn't actually "integrate" with the Keil MDK-ARM/uVision development environment; rather, it is preconfigured to support Keil’s set of compilers, allow C++test projects to use these compilers, and allow complete Keil uVision projects to be imported into the C++test workspace. 

Supported Environments

C++test supports:

  • Keil MDK-ARM 3.4x with uVision3 version 3.7x
  • Real View MDK-ARM 4.0x to 4.7x
  • Keil C166 7.00 with uVision4 version 4.00a (see Importing Keil uVision 4.0 Projects, for special instructions on importing uVision4 projects)

MDK-ARM 4.11 or higher is required in order to use fully-automated C++test Test Configurations that make a use of ITM based communication channel (i.e., Test Configuartions that are in the Builtin>Embedded>Keil uVision category and have the "(ITM)" name suffix).

The following cross compilers are supported:

  • ARM/Thumb C/C++ Compiler, RVCT3.1 for uVision
  • C51 COMPILER V8.18 (static analysis only)
  • C166 compiler V7.00 (static analysis only)
  • ARM C/C++ Compiler, RVCT4.0 for uVision
  • ARM C/C++ Compiler, RVCT4.1 for uVision
  • ARM C/C++ Compiler, RVCT5.0 for uVision
  • ARM C/C++ Compiler 5.0x for uVision

Prerequisites

For C++test itself, the standard rules apply. CDT is already installed with the standalone C++test Eclipse product, so no additional extensions are needed. But if you are using an Eclipse plugin, then  you must also install the CDT (C++ Development Tools) extension into Eclipse. See Installation for details.

To allow testing with RealView MDK compilers, the compilers must be visible in the environment. To establish this visibility, ensure that the compiler executable location is added to the system PATH variable. For example, to use the armcc compiler, you need to add the <MKD install dir>\ARM\BIN31 path for uVision3 — or <MKD install dir>\ARM\BIN40 for uVision4 — to the PATH variable.

Optionally, you can modify the Compiler Family definition in the project properties and replace the compiler executable names with full paths. 

 

  • No labels

Need assistance? Visit our support page