WCET

Why Static analysis doesn't work for Multicore WCET estimation

Learn why static analysis techniques aren't applicable for timing analysis on multicore systems and why a hybrid timing analysis is better.
Read More

WCET analysis of object code with zero instrumentation

Worst-case execution time (WCET) analysis is critical for the verification of safety-critical real-time embedded systems. This analysis is typically performed by instrumenting source code and obtaining timing data from an instrumented build. While this is a robust method for determining WCET metrics, it requires that instrumentation be added to source code, increasing overhead. This is why we have been developing RapiTime, our on-target timing analysis tool, to perform WCET analysis with zero instrumentation.  
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

Things that make real-time hard - parallelization

Continuing our series of posts on what makes real-time hard, this week the focus is on parallelization. What issues arise when attempting to determine WCET of parallelised code and what can you do to overcome them?
Read More

Pages