RapiTime

Out of the box RVS integration for DDC-I's Deos RTOS

Our RVS integration with the Deos RTOS promises to offer an out-of-the-box solution, significantly reducing the effort needed to analyze timing and scheduling behavior of software hosted on Deos.
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

Misusing Execution Time Profiles

One of my favourite sayings is "when the only tool you have is a hammer, all your problems look like nails". We've been analyzing the response time of our website by tracking the ping response times, and I saw an opportunity to use one of RapiTime's reports to visualise this data.
Read More

How do you put the "real-time" into a real-time operating system?

There are lots of products on the market claiming to be real-time operating systems. Wikipedia alone lists 149. But what does it mean to be a real-time operating system?
Read More

Is Windows Safe Mode faster for code?

In a conversation with a colleague, I found myself wondering what was the impact of running code under Windows vs a "bare metal" x86 box. One of the nice things about working for a tool vendor is that you have the tools to hand to perform these kind of experiments "for fun".
Read More

Pages