Instrumentation

Code coverage without instrumentation

Follow our progress on collecting coverage results without applying any instrumentation at all.
Read More

Lightweight instrumentation with RapiTask

Learn how to collect task scheduling data with minimal instrumentation overheads using RapiTask.
Read More

If RapiTime provides Ipoint coverage, why do I need RapiCover?

Users of RapiTime will probably be aware that one of the categories of information shown in a RapiTime report is "Ipoint Coverage". So, given that RapiTime supplies coverage information, why do you need RapiCover?
Read More

Tools to help real-time embedded programmers learn their trade

Over at The Engineer the debate about "should everyone be a programmer?" rages on. Here are Zoe Stephenson's thoughts.
Read More

Minimize instrumentation overheads

A key challenge with on-target verification is the influence that the act of measurement itself can have on the results obtained. This is referred to as the called probe effect. For example, adding instrumentation points to the source code changes the code size, execution time, and may also increase stack usage.
Read More