Timing analysis

On-target verification – why is it so difficult?

At Rapita, we love a challenge. The company was set up to address a very specific challenge: performing on-target verification of embedded systems (initially WCET, but subsequently, we’ve looked at other properties). Here we discuss what we mean by “on-target verification” and explain why it is so difficult?
Read More

PROARTIS: thoughts on Statistics, Randomness and Timing

We're involved in an exciting research project at the moment, called PROARTIS, that's taking a very unusual approach to timing analysis. So I thought that it would be worth writing about here. The research in PROARTIS is starting to take shape now and we're thinking about how we can use the technology in RVS/RapiTime.
Read More

Safety, WCET and measurements

I was at a meeting this week where someone put a slide on the screen that contained the sentence "Measuring WCET is unsafe." This statement is wrong on so many counts, and yet seems to be circulating in literature, is widely quoted, and is frequently re-stated "blindly", with no understanding of what it means. As it keeps getting quoted, I thought I'd write something about it.
Read More

Eliminating timing variability: DRAM refresh times

If you're interested in getting accurate timing measurements of your software, you need to eliminate sources of variation to the software timing wherever possible.
Read More

Go beyond simple profiling

If you've measured execution time, eliminating the context switches and the variability they cause (see our last blog post), you may still have a wide variety of execution times that arise from the thread you're measuring. A natural question is why this should happen. To be able to answer such questions, you need to have the right level of information.
Read More