Timing analysis

What do you mean: no-one can tell me what the actual WCET is?

Given that we’re a company that makes a tool that helps you to find the worst-case execution time (WCET) of your code, it might be surprising to hear us say that it’s (generally) not possible to give an exact value for WCET. So what do we mean by an exact value for WCET?
Read More

What is the state of the practice in WCET (part 3) - what is the alternative?

Last time we looked at the limitations of a common approach to finding WCET: measuring end-to-end times. This week we look at an alternative approach.
Read More

What is the state of the practice in WCET (part 2) - what are the limitations?

Previously we looked at how WCET (worst-case execution time) is measured in many applications. In the second of three posts we now turn to the limitations of current practices, and how they can be overcome through the use of automated timing analysis (specifically RapiTime).
Read More

What is the state of the practice in WCET (part 1)?

Since 2004 we have worked with companies which need to conduct timing analysis on their embedded real-time systems. Our consultancy work gives us plenty of opportunities to speak with engineers about how they are conducting timing analysis right now, and especially how they determine worst-case execution time (WCET).
Read More

On-target verification - if it's so difficult, why do it?

Last week we discussed how difficult it is to do on-target verification of embedded systems. Clearly this prompts the question – why bother?
Read More

Pages