Workflow in the IDE

The IAR add-on of Testwell CTC++ offers a full integration with IAR Embedded Workbench, for all steps from building to report generation.

Configuration and Build

Use Tools > CTC++ Set/ Clean... to configure the coverage level, the usage of HOTA or BITCOV, and other ctc options.

There are two different ways to perform an instrumented build:

  1. Use the switch Instrument All Builds, save your settings, and use the IAR project menu commands to trigger the instrumented build.
  2. Recommended: Save your settings in the dialogue without using that switch. Use Tools > CTC++ Instrumented Build instead.
With both ways, instrumented binaries are built, and they replace their uninstrumented versions. The symbol file MON.sym is created in the project directory.
Note: Using Debug as build configuration is the most convenient way, especially when using Testwell CTC++ for the first time.

Tests

With the instrumented binaries, execute the tests as usual with IAR Embedded Workbench - on the real target, or in a simulation.

For many targets, the standard implementation of the HOTA runtime library works, especially when the debugger is used for communication. If an adaption is necessary, see Constructing the CTC Runtime for the Target for details.

Coverage Data and Reports

With the default setup for HOTA, only one step is necessary to build reports: Use Tools > CTC++ Report... to choose the report and to generate it.

If you are using BITCOV, the coverage data reside in an array in memory and have to be dumped first to a file:
  1. Use the memory screen of the IAR debugger to locate CTC_array.
  2. Save it to the project directory with file format "intel-extended" and filename memory.hex.

After that, you can continue with Tools > CTC++ Report... as described for HOTA.