
Zero-footprint timing analysis for critical software
Collect timing metrics from systems that produce branch traces
By automatically producing software timing metrics from branch traces, RapiTimeZero reduces the effort needed to verify software timing behavior. Along with branch traces produced by the system hardware, RapiTimeZero only needs a disassembly of the application, meaning there’s no need for either source code or instrumentation.
The high-water mark execution time results produced by RapiTimeZero help you produce evidence that your code meets it timing deadlines.
Identify code to optimize for worst-case behavior
Optimizing code to improve average case performance often has little effect, and may even have a negative effect, on worst-case timing behavior.
RapiTimeZero helps you identify the code elements that have the highest contribution to your overall execution time. This helps you focus your optimization efforts on the sections of code for which it’s most likely to affect your code’s overall behavior.
Debug rare timing events
During program execution, many events occur, and debugging the source of issues like rare timing events can be like searching for a needle in a haystack.
RapiTimeZero helps you debug rare timing events in your code by letting you step through your program execution step by step as you would with a code debugger.
Simplify verification through integration with your continuous test tool
Keep your verification on track by using RapiTimeZero alongside your continuous integration tool. Collect timing results and track your project’s progress over time with our integrations for Jenkins and Bamboo.
By analyzing your code with RapiTimeZero on every new build, you can easily identify anomalies in execution time results as they happen.
Analyze timing behavior of libraries without source code
RapiTimeZero lets you analyze the timing behavior of third-party libraries or other pieces of software for which you have no access to the source code.
As RapiTimeZero analyzes a branch trace and a disassembly to produce timing results, it can produce results even when you don’t have access to source code.

Product features
-
Zero footprint execution time analysis Zero footprint timing analysis for critical software.Discover this feature
-
Source to object code traceability Trace results collected from analyzing program execution to source code, where available.Discover this feature
-
Hardware support Supported operating systems, trace capture mechanisms and CPU architectures.Discover this feature
-
Produce certification evidence Produce evidence for certification.Discover this feature
-
Optimize code for timing performance Easily identify code with the the greatest impact on timing performance.Discover this feature
-
Automate testing on host and target Run tests on host computers and test rigs in continuous build environments.Discover this feature
-
Efficient integration workflow Efficient integration workflow and inbuilt Platform Support Packages for integrations.Discover this feature
-
RVS Project Manager Take your test project from creation to completion with an intuitive user-interface.Discover this feature
-
Shared integration with zero-footprint RVS tools After integrating one zero-footprint RVS tool to work a development environment, it is trivial to use others.Discover this feature
-
Portable test environments Multiple users can share the same test environment.Discover this feature
-
Customizable workflow Customize the RVS workflow to best meet your needs.Discover this feature
-
Template integrations Create and use template integrations to reduce your effort integrating RVS with your system.Discover this feature
-
Compare reports Compare reports from different builds to track project progress over time.Discover this feature
-
Configurable export formats Export timing results in a variety of formats.Discover this feature
-
Customizable color scheme Customize the color scheme used to display your results.Discover this feature
-
Comprehensive verification toolsuite One tool to meet all your software verification needs.Discover this feature
-
View detailed timing metrics at a glance Specialized charts and tables make it easy to focus your analysis.Discover this feature
-
Treemaps View coverage and hierarchy of code at a glance.Discover this feature
-
Execution Time Profile Chart View a histogram of your software's timing behavior to easily identify patterns.Discover this feature
-
Rewind Trace Step through execution traces to investigate timing events using a debugger-like interface.Discover this feature
-
Aggregate Profile Chart A configurable chart helps you visualize timing data in the context of your code's call tree.Discover this feature
-
Invocation Timeline Chart A timeline of your invocations helps you visualize the order of calls and how long each took to execute.Discover this feature
-
Easily filter results Easily filter results to focus your analysis.Discover this feature
-
Code viewer View code with syntax highlighting and color-coding of results.Discover this feature
-
Advanced search function Search reports for specific elements using advanced queries.Discover this feature
-
Jenkins Run RVS automatically through Jenkins to collect and archive results.Discover this feature
-
Bamboo Run RVS automatically through Bamboo to collect and archive results.Discover this feature
-
Comprehensive language support Support for all languages that target machine code.Discover this feature
-
Flexible licensing options Select floating or node-locked licenses with annual or perpetual duration.Discover this feature
-
Floating licenses Floating licenses support multiple users and shared working environments.Discover this feature
-
Node-locked licenses Node-locked licenses support use of RVS within a limited geographical area.Discover this feature
-
Annual licenses License RVS in annual increments.Discover this feature
-
Perpetual licenses License RVS for use indefinitely.Discover this feature
-
FlexNet Publisher compatible export format License usage data is exported in a format compatible for tracking using FlexNet Publisher.Discover this feature
-
Easy to get started Integration and learning resources help you get started verifying your code in no time.Discover this feature
-
Support Dedicated support service to resolve technical issues quickly.Discover this feature
-
Tutorials Learn how to get the most from our verification solutions with simple, interactive tutorials.Discover this feature
-
Training Get up to speed with custom training courses delivered by skilled field application engineers.Discover this feature
-
Documentation Learn how to use RVS features with comprehensive documentation in both printed and electronic formats.Discover this feature
-
Multicore support Verify critical multicore systems.Discover this feature
Videos
CPUs
Zero-footprint RVS tools require that a branch trace is collected during program execution. Branch traces can be automatically generated by compatible targets or can be collected while the program operates using external devices. To interface with development environment, a Platform Support Package is needed.
Here are some examples of PSPs that we've prepared:
- No OS on x86 in QEMU
- No OS on ZCU102 with Lauterbach® TRACE32® debugger
- FreeRTOS on ARM M3 in QEMU
- FreeRTOS on R-Car Salvator-X with PARTNER-Jet2 debugger
- FreeRTOS on ZCU102 with Lauterbach TRACE32 debugger
- RV850 RTOS on RT850G4M with Lauterbach TRACE32 debugger
- eMCOS on R-Car Salvator-X with PARTNER-Jet2 debugger
For more information, and to see if we can add support for your development environment, contact support@rapitasystems.com.
Operating Systems
RapiTimeZero can be used to analyze software run on any host operating system.
Operating System |
---|
Windows 7+ |
Windows Server 2008 R2+ |
Variety of Linux distributions (including Ubuntu and Red Hat) |
For older operating systems, contact us. |
Programming languages
Language |
---|
Any language that targets machine code |
Mixed languages |
Compilers
Zero-footprint RVS tools can analyze software built with any compiler from which a disassembly can be produced from the assembled executable.
Frequently asked questions
-
How large a code base can RVS tools handle?
RVS tools are designed to handle very large code bases. Because of the efficient algorithms used by RVS tools, there is no fundamental limitation to the number of lines of code that RVS can process, and our RVS tools have been used on projects with millions of lines of code.
-
How are RVS products licensed?
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.
-
What happens if I encounter an issue while using an RVS tool?
All RVS licenses include access to our dedicated in-house support team, who will work with you to provide a rapid fix to your issue. This is a critical part of our vision. During 2016, we responded to 97% of new support requests within one working day, closed 56% of these within 3 working days and 91% within 20 working days. We also inform our customers of known issues via our website and email.
-
How do you support RVS users?
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.
-
What is RapiTime Zero?
RapiTimeZero is an execution time analysis tool that requires no project source code or modification of the development environment being used. To extract execution time information, RapiTimeZero analyzes branch trace information collected from a compatible target or data collection mechanism.
As part of the RVS toolsuite, it forms part of a software verification solution that also includes tools for structural coverage analysis and functional testing.
-
How does RapiTime Zero work?
RapiTimeZero uses two inputs from which to produce execution time results. The first of these is a branch trace collected while the program under analysis is executed, while the second is a disassembly of the executable. From these, it can understand both the program structure and the events that occurred during the program execution, allowing it to perform execution time analysis and produce execution time results.
-
Which hardware environments and data collection mechanisms does RapiTime Zero support?
RapiTimeZero 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 RapiTimeZero Hardware support.
-
Which types of timing data does RapiTime Zero calculate?
RapiTimeZero calculates the high and low water mark paths through your program and collects minimum, average and maximum execution times for your code.
-
Does RapiTime Zero calculate worst-case execution time results?
RapiTimeZero 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.
-
Can I view my results in the context of my project source code?
If your source code is available, yes. By importing your source code and debug symbols into your RVS project, you can view your results in the context of both your object and source code, and trace between them.
-
Can I use RapiTime Zero to analyze the timing behavior of multicore architectures?
As with all RVS tools, RapiTimeZero supports data collection on multicore architectures. To analyze the timing behavior of multicore architectures, RapiTimeZero 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.
-
How does RapiTime Zero help me investigate timing behavior?
RapiTimeZero includes a Rewind Trace utility, which lets you step through the events that occurred during program execution like you can with a debugger. This lets you set breakpoints and easily analyze the execution of your program.
-
Which languages does RapiTime Zero support?
As RapiTimeZero analyzes object code directly to produce results, it supports any language that targets machine code.
-
How do I learn more about RapiTime Zero?
You can request a trial version of RVS, which includes RapiTimeZero. You can also arrange a demonstration, where a member of our team will work with you to show the benefits that RapiTimeZero can offer you.
-
Can I use RVS tools with my continuous integration environment?
RVS integrates with continuous integration tools including Jenkins and Bamboo. By integrating RVS with your existing continuous integration tool, you can collect unit test, coverage, and execution time results with every new build, letting you easily identify anomalies in your software’s behavior as they happen.