RapiTimeZero | Zero-footprint timing analysis for critical software

RapiTime^Zero extracts information on program execution from a branch trace that must be collected while the program under analysis is executed. This branch trace may be produced by target hardware or collected using a specific data collection mechanism such as a Lauterbach debugger.

For a list of currently supported platforms, see our RapiTime^Zero Hardware support.

RapiTime^Zero does not currently collect worst-case execution time results, but we are developing a solution to do so. This requires more in-depth analysis of collected branch traces than that required for analysis of other execution time metrics.

For more information, contact support@rapitasystems.com.

If you need to collect worst-case execution time results, you can do so using RapiTime.

As with all RVS tools, RapiTime^Zero supports data collection on multicore architectures. To analyze the timing behavior of multicore architectures, RapiTime^Zero simply needs to know which branches corresponded to which core during program execution. This information can either be inferred by providing an individual branch trace for each core, or a combined trace that includes information on the core on which each branch was taken.

As RapiTime^Zero analyzes object code directly to produce results, it supports any language that targets machine code.

We offer both “Node-locked” and “Floating” licenses, and a license server to support use of our tools in your specific development environment. Floating licenses follow the “Enterprise” model, meaning that you can use our tools across geographical boundaries and different projects and users.

For more information on our licensing models, see our RVS licensing FAQs.

We provide an extensive set of RVS documentation with each of our products, and offer training courses guiding you through the most effective use of RVS tools. All our users can benefit from privileged access to our website, which includes downloads for new product releases.