How RapiTime works

RapiTime 3.0 works in four stages:

1. Instrumentation code which highlights the execution of a specific section of code is automatically added.
2. As the application is executed on the target, an execution trace is collected. This trace is a sequence of time-stamped values that show when the instrumentation code is executed.
3. Using the trace RapiTime 3.0 identifies the parts of the source code which have and have not been executed (code coverage), and performance metrics for each part of executed code.
4. Using the performance and coverage data, RapiTime 3.0 can also predict worst-case execution time, and identify the best locations for optimization.

RapiTime 3.0 also includes the collection of on-target code coverage – which gives you an accurate picture of the parts of the source code investigated during testing – and debugging support through the Rewind facility, which gives users the ability to move backwards and forwards - “Rewind” - through source code.

Of course we know that one of the biggest challenges of using C++ in embedded systems is that it may not relate to the target code as closely as C. Manually measuring the timing performance of individual parts of the code may therefore become much harder than before unless you take the automated RapiTime 3.0 approach.

The capacity to quickly identify the source of timing problems and carry out targeted optimization work means RapiTime 3.0 helps engineers and managers overcome this challenge.