Your browser does not support JavaScript! Skip to main content
Free 30-day trial Customer portal Careers DO-178C Handbook
 
Rapita Systems
 

Industry leading verification tools & services

Rapita Verification Suite (RVS)

  RapiTest - Unit/system testing   RapiCover - Structural coverage analysis   RapiTime - Timing analysis (inc. WCET)   RapiTask - Scheduling visualization   RapiCoverZero - Zero footprint coverage analysis   RapiTimeZero - Zero footprint timing analysis   RapiTaskZero - Zero footprint scheduling analysis

Multicore verification

  MACH178   Multicore Timing Solution   RapiDaemons

Services

  V & V Services   Qualification   Training   Tool Integration  Support

Industries

  Aerospace (DO-178C)   Automotive (ISO 26262)   Space

Other

  RTBx   Mx-Suite   Software licensing   Product life cycle policy  RVS development roadmap

Latest from Rapita HQ

Latest news

RVS 3.18 Launched
Solid Sands partners with Rapita Systems
Danlaw Acquires Maspatechnologies - Expanding Rapita Systems to Spain
Rapita co-authored paper wins ERTS22 Best paper award
View News

Latest from the Rapita blog

Measuring response times and more with RapiTime
Why mitigating interference alone isn’t enough to verify timing performance for multicore DO-178C projects
There are how many sources of interference in a multicore system?
Supporting modern development methodologies for verification of safety-critical software
View Blog

Latest discovery pages

do178c DO-178C Guidance: Introduction to RTCA DO-178 certification
matlab_simulink MATLAB® Simulink® MCDC coverage and WCET analysis
code_coverage_ada Code coverage for Ada, C and C++
amc-20-193 AMC 20-193
View Discovery pages

Upcoming events

Aerospace Tech Week Europe 2023
2023-03-29
Aeromart Montreal 2023
2023-04-04
Certification Together International Conference
2023-05-10
View Events

Technical resources for industry professionals

Latest White papers

DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
Compliance with the Future Airborne Capability Environment (FACE) standard
View White papers

Latest Videos

Streamlined software verification with RVS 3.18
Sequence analysis with RapiTime
Visualize call dependencies with RVS thumbnail
Visualize call dependencies with RVS
Analyze code complexity thumbnail
Analyze code complexity with RVS
View Videos

Latest Case studies

Supporting ISO 26262 ASIL D software verification for EasyMile
RapiCover’s advanced features accelerate the certification of military UAV Engine Control
Front cover of whitepaper collins
Delivering world-class tool support to Collins Aerospace
View Case studies

Other Downloads

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

Discover Rapita

Who we are

The company menu

  • About us
  • Customers
  • Distributors
  • Locations
  • Partners
  • Research projects
  • Contact us

US office

+1 248-957-9801
info@rapitasystems.com
Rapita Systems, Inc.
41131 Vincenti Ct.
Novi
MI 48375
USA

UK office

+44 (0)1904 413945
info@rapitasystems.com
Rapita Systems Ltd.
Atlas House
Osbaldwick Link Road
York, YO10 3JB
UK

Spain office

+34 930 46 42 72
info@rapitasystems.com
Rapita Systems S.L.
Parc UPC, Edificio K2M
c/ Jordi Girona, 1-3, Office 306-307
Barcelona 08034
Spain

Working at Rapita

Careers

Careers menu

  • Current opportunities & application process
  • Working at Rapita
Back to Top

Breadcrumb

  1. Home
  2. RVS
  3. RapiTaskZero
RapiTaskZero

Zero-footprint event-level scheduling analysis for critical software

Why choose RapiTaskZero?

  •  Gain insight into your application through scheduling analysis
  •  Locate rare timing events that need attention
  •  Identify bottlenecks in your application by analyzing capacity issues
  •  Compare scheduling algorithms from different RTOSs
  •  Visualize scheduling behavior of libraries without source code
Request a demoCheck PSP compatibility
  • Overview
  • Features
  • Resources
  • Compatibility
  • FAQs

Gain insight into your application through scheduling analysis

Understanding your application’s scheduling behavior can help you troubleshoot scheduling issues. RapiTaskZero automatically collects information during program execution, presenting this data so you can follow the events that occurred in the test run.

Providing a timeline of the tasks that ran in your system, a wealth of charts and statistics, RapiTaskZero lets you analyze your system’s scheduling behavior in-depth.

understand scheduling behavior
locate rare timing events

Locate rare timing events that need attention

RapiTaskZero makes it easy to find rare timing events such as priority inversions in your system so you can fix them. By following your system’s tasks throughout execution, you can easily locate rare timing events, which can be visualized easily for example by color coding tasks according to priority.

Identify bottlenecks in your application by analyzing capacity issues

Bottlenecks in critical software can slow the system down or even cause it to fail as timing deadlines are missed. By letting you view the CPU utilization of each task in your system throughout your software execution, RapiTaskZero helps you identify bottlenecks so you can fix them.

identify bottlenecks
compare scheduling algorithms through common framework

Compare scheduling algorithms from different RTOSs

While there are many vendor-specific scheduling visualization tools, these are often only compatible with a single RTOS. RapiTaskZero lets you understand your system’s scheduling behavior through a common framework no matter which RTOS you’re using.

This means less time learning new tools and more time testing and resolving issues.

Visualize scheduling behavior of libraries without source code

RapiTaskZero lets you analyze the scheduling behavior of third-party libraries or other pieces of software for which you have no access to the source code.

As RapiTaskZero analyzes a branch trace and a disassembly to produce results, it can do so even when you don’t have access to source code.

visualize scheduling of libraries

Product features

  • Zero footprint verification
  • System event tracing
  • Integrated testing environment
  • Project navigation
  • Language support
  • Licensing
  • Support and training
  • Integration with embedded targets
  • Zero footprint system event tracing Zero footprint system event tracing 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
  • Platform support Supported compilers, instruction sets, trace capture mechanisms and RTOSs.
    Discover this feature
  • Understand scheduling behavior Understand your system's scheduling behavior at a glance.
    Discover this feature
  • Locate rare timing events Scan large traces for specific unusual situations.
    Discover this feature
  • Analyze system capacity issues Identify and analyze capacity issues in your system.
    Discover this feature
  • RTOS-independent scheduling visualization Understand program scheduling through a common framework no matter which RTOS you're using.
    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
  • 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
  • Customizable task colors Customizable task colors help you highlight the tasks you're most interested in.
    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
  • Code viewer View code with syntax highlighting and color-coding of results.
    Discover this feature
  • Easily filter results Easily filter results to focus your analysis.
    Discover this feature
  • Visualize call dependencies Visualize the call dependencies in your code.
    Discover this feature
  • Advanced search function Search reports for specific elements using advanced queries. 
    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
  • 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
  • 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
  • Easily migrate to new versions Easily migrate to new RVS versions with guided migration help.
    Discover this feature

Videos

RapiTask Zero Thumbnail
Zero-footprint system event tracing with RapiTask Zero
00:00:46 | Overview
 
Visualize call dependencies with RVS thumbnail
Visualize call dependencies with RVS
00:00:33 | Feature
 
Streamlined software verification with RVS 3.18
00:01:30 | Other
 

Downloads

  Brochure
Rapita Systems Brochure
  Product brief
Zero-footprint RTOS event tracing with RapiTask Zero
  Product brief
Software support and maintenance
  Product brief
Training courses
  FAQ
Software licensing FAQ
  Technical note
Requirements for zero-footprint RVS analysis

News & Blog

News
Zero-footprint verification with RVS 3.12

Requirements

Check PSP compatibility

Software analysis by zero-footprint RVS tools has the following requirements:

  • The platform (target and any external devices e.g. debuggers) must be capable of producing a branch trace without gaps to ensure that the full program trace can be reconstructed.
  • The OS needs to make context switches observable. For some systems, supporting this may require modifications to be made to the OS.
  • A Platform Support Package (PSP) is needed for RVS to interface with the development environment, including the target hardware and trace capture mechanisms, in order to convert the branch trace into a format that the RVS tool understands and disassemble the executable and parse the resulting object code.

PSPs are developed to be compatible with the following:

  • Compilers
  • Instruction sets
  • Branch traces collected from the platform
  • Real-time operating systems
diagram showing hardware support on zero-footprint software

For a list of components that are already supported, see below. Note that we can add support for some components not listed below.

For detailed information on the requirements for zero-footprint tracing, see our Technical note.

For more information, contact info@rapitasystems.com.


 

Compilers

Platform Support Packages (PSPs) must be able to disassemble executables for further analysis. Typically, tools required for this are supplied as part of a toolchain unique to each compiler. The compilers PSPs already support are listed below:

  • Arm Compiler
  • CC-RH850
  • Clang
  • GCC

We can develop support for other compilers. For more information, contact us at info@rapitasystems.com.

Instruction sets

When code has been disassembled, Platform Support Packages (PSPs) must be able to understand the instruction set of the object code so they can parse it before it is used for subsequent analysis by zero-footprint RVS tools. The instruction sets PSPs already support are listed below:

  • 68k
  • AArch64
  • ARM
  • PowerPC
  • RH850
  • VISIUM
  • x86

We can develop support for other instruction sets. For more information, contact us at info@rapitasystems.com.


 

Branch traces

For it to be possible to analyze executables generated by a platform by zero-footprint RVS tools, it must be possible to collect a branch trace from the platform*. Some targets generate branch traces by default, for example:

  • Boards that have been developed to meet at least Class 2 of the Nexus message-based trace protocol
  • ARM boards including an ARM ETM component
  • Custom boards developed to produce branch traces

A debugger may be used to collect these branch traces from the target. Simulators may generate branch traces, or it may be possible to modify them to do so. Each Platform Support Package (PSP) is designed to support branch traces collected by a specific debugger or from a specific simulator. The debuggers and simulators PSPs already support are listed below:

† a modified version is available, which supports zero-footprint analysis
Debuggers Simulators
Lauterbach TRACE32 QEMU†
PARTNER-Jet2  

We can develop support for other debuggers and simulators. For more information, contact us at info@rapitasystems.com.

*In some cases, other approaches may be possible, such as using a branch map.


 

Real-time operating systems

For it to be possible to analyze executables generated by a platform by zero-footprint RVS tools, it must be possible to collect information on context switches made during software execution. Whether this is possible or not depends on the real-time operating system (RTOS) used and its configuration. Platform Support Packages must be able to understand context switch information to support further analysis of an executable by zero-footprint RVS tools. The RTOSs PSPs already support are listed below:

  • eMCOS for AUTOSAR Adaptive Platform
  • eMCOS for AUTOSAR Classic Platform (RV850)
  • FreeRTOS
  • SafeRTOS
  • SYSGO PikeOS®
  • Bare Metal (no OS)

We can develop support for other real-time operating systems. For more information, contact us at info@rapitasystems.com.

Operating systems

Zero-footprint RVS tools 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

 

Multicore systems

Zero-footprint RVS tools can be used to analyze software from multicore systems.

Suitable branch trace(s) can be collected in one of two ways:

  1. Collecting a separate branch trace from each core
  2. Collecting a branch trace that includes results from all cores, where it’s possible to derive the core from which each branch was taken

Frequently asked questions

  • General
  • Compatibility
  • Licensing and support
Expand All
  • How does RVS support the analysis of shared code compiled by build systems with multiple executables 
  • What is RapiTask Zero?  
  • How does RapiTask Zero work?  
  • Which platforms and data collection mechanisms do zero-footprint RVS tools support?  
  • What are Platform Support Packages and why are they needed? 
  • Is a Platform Support Package available for my platform? 
  • Why do I need RapiTask Zero when I have tools from my RTOS vendor?  
  • How does RapiTask Zero show OS events such as inter-process communication (semaphores, messages), timers, hardware I/O etc?  
  • Can I use RapiTask Zero to analyze the behavior of multicore architectures?  
  • How are my results presented?  
  • Can I view my results in the context of my project source code?  
  • How can RVS help me understand my code base? 
  • If I have RapiTime or RapiTime Zero, do I still need RapiTask or RapiTask Zero?  
  • Which languages does RapiTask Zero support?  
  • How large a code base can RVS tools handle? 
  • How are RVS products licensed? 
  • How does RVS support Enterprise licensing? 
  • Can I create and manage groups for my floating RVS licenses? 
  • What happens if I encounter an issue while using an RVS tool? 
  • How do you support RVS users? 
  • How long has RVS been used for software verification? 
  • How do I learn more about RapiTask Zero?  
  • 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. 

    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 2021, we resolved 63% of our support requests within 7 working days and 93% within 30 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 RapiTask Zero?

    RapiTaskZero is a scheduling visualization tool that requires no project source code or modification of the development environment being used. To extract task-level scheduling information from a program, RapiTaskZero 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, worst-case execution time analysis and functional testing.

     

  • How does RapiTask Zero work?

    RapiTaskZero uses two types of inputs from which to produce task-level scheduling results. The first is the executable file and a disassembly of it, and the second is a branch trace collected while the program under analysis is executed. From these inputs, RapiTaskZero can understand both the program structure and the events that occurred during the program execution, allowing it to perform task-level scheduling analysis and produce results.

  • Why do I need RapiTask Zero when I have tools from my RTOS vendor?

    RapiTaskZero is OS-agnostic so you can keep the same visualization and metrics if you change OS, and you can use RapiTaskZero results as a point of reference to compare operating systems.

    Additionally, you can capture and display custom events not related to the operating system (for example ARINC 429 messages) and display them in the trace.

  • How does RapiTask Zero show OS events such as inter-process communication (semaphores, messages), timers, hardware I/O etc?

    RapiTaskZero is OS-agnostic; as with all Rapita tools the integration with the operating environment needs to be customized. If we can get information about items of interest from the OS we can add ‘user events’ to a RapiTaskZero trace.

  • Can I use RapiTask Zero to analyze the behavior of multicore architectures?

    As with all RVS tools, RapiTaskZero supports data collection on multicore architectures. To analyze the task-level scheduling behavior of multicore architectures, RapiTaskZero simply needs to know which branches corresponded to which core during program execution. This information can be inferred by providing a combined trace that includes information on the core on which each branch was taken.

  • How are my results presented?

    RapiTaskZero displays results in two applications, the RVS Project Manager that is shared with all RVS tools, and an application specifically designed to display task scheduling information. You can synchronize the two applications to ensure that you can easily identify specific timing events in your system.

    RapiTaskZero 's Invocation Timeline Chart helps you to understand the high-level scheduling behavior of your system at a glance.

  • If I have RapiTime or RapiTime Zero, do I still need RapiTask or RapiTask Zero?

    RapiTime and RapiTimeZero abstract away from the OS tasking model and only report the execution time of a task as if it were the only thing running on the CPU. If you are interested in the response time of your code, or the interaction between tasks and your OS, you'll need RapiTask or RapiTaskZero.

  • Which languages does RapiTask Zero support?

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

  • How do I learn more about RapiTask Zero?

    You can request a trial version of RVS, which includes RapiTaskZero. You can also arrange a demonstration, where a member of our team will work with you to show the benefits that RapiTaskZero can offer you.

  • Which platforms and data collection mechanisms do zero-footprint RVS tools support?

    Software analysis by zero-footprint RVS tools has the following requirements:

    • The platform (target and any external devices e.g. debuggers) must be capable of producing a branch trace without gaps to ensure that the full program trace can be reconstructed.
    • The OS needs to make context switches observable. For some systems, supporting this may require modifications to be made to the OS.
    • A Platform Support Package (PSP) is needed for RVS to interface with the platform, including the target hardware and trace capture mechanisms, in order to convert the branch trace into a format that the RVS tool understands and disassemble the executable and parse the resulting object code. PSPs are developed to be compatible with four components of the platform: Compilers, Instruction sets, Branch traces and Real-time operating systems.

    For more information on the requirements for software analysis by zero-footprint RVS tools and a list of currently supported platforms, see our Platform support page.

    For more detailed information on the requirements, see our Technical note.

  • 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.

  • How long has RVS been used for software verification?

    The Rapita Verification Suite (RVS) has been used in the critical embedded industry for over 15 years and supported a number of avionics projects globally. Qualification kits for qualified RVS products have supported more than 20 DO-178B and C certification projects up to and including DAL A.

  • How does RVS support Enterprise licensing?

    Floating RVS licenses follow an “Enterprise” model. You can use them across geographical boundaries*, in different projects, with different users, and share them with suppliers working on the same project.

    *Some floating licenses may be restricted to use within a specific geographical region. Where this is the case, this is agreed before licenses are issued.

  • What are Platform Support Packages and why are they needed?

    Platform Support Packages are required to support software analysis by zero-footprint RVS tools. They interface between the tools and the platform in order to do the following:

    • Convert the specific format of native branch traces generated by the platform into a format that the RVS tool understands and can use for subsequent analysis.
    • Disassemble the object code to understand the structure and control flow of the code so this can be used for subsequent analysis.

    Each PSP is designed to support various components of a platform. These include:

    • The compiler(s) used to generate executables
    • The instruction set of object code to be analyzed
    • The native branch trace format generated from the platform – this depends on the mechanism used to generate branch traces, which may be the target hardware (or simulator) or a third-party device e.g. debugger.
    • The real-time operating system.

    Different PSPs are needed to support analysis by zero-footprint RVS tools when any of the above items are different between two platforms. For more information on how PSPs support analysis by zero-footprint RVS tools, see our Requirements for zero-footprint RVS analysis Technical note.

  • Is a Platform Support Package available for my platform?

    To see whether we have already developed PSPs compatible with the components on your platform, see our zero-footprint Platform support.

    If we have not yet developed PSPs compatible with one or more components of your platform, we may be able to develop them. For more information, contact us at info@rapitasystems.com.

    Check PSP compatibility

  • Can I create and manage groups for my floating RVS licenses?

    Yes, you can create and manage groups of users for your floating RVS licenses. You can restrict each group to only serve licenses to specific hostnames or IP addresses. This allows you to reserve licenses for specific groups or specific purposes such as supporting the use of RVS on a continuous integration server.

    Any licenses that you don’t reserve will remain available as floating licenses that can be shared among different users and geographic locations.

  • How does RVS support the analysis of shared code compiled by build systems with multiple executables

    RVS supports the analysis of shared code compiled by build systems with multiple executables by letting you specify the source files that will be compiled in each executable. 

    If you have functions that are declared in multiple components with the same name but have different definitions, RVS can treat each such function uniquely, for example to provide separate coverage in RapiCover and separate execution time results in RapiTime.

  • How can RVS help me understand my code base?

    RVS analyzes the structure of your code and presents information on your code’s structure, helping you understand your code and its dependencies in a variety of forms such as the following:

    • RVS analyzes the McCabe complexity of your code and presents the complexity of each code element, letting you easily identify code with high complexity. 
    • RVS Treemaps present the hierarchy of your code’s components and source files graphically.
    • RVS lets you view and explore the call dependencies in your code.  
 

Request Demo

Times are in GMT

What happens next?
We aim to respond to demo requests within 1 working day. 

 

Check PSP compatibility

Zero-footprint Platform Support Packages (PSPs) are needed to support the analysis of object code by zero-footprint RVS tools. Each PSP is compatible with a specific platform. 

 

Enter your platform details below to check whether a PSP compatible with your platform is available.

Which compiler does your platform use?
Which instruction set does your platform use?
If your platform includes physical hardware, which debugger are you using?
If your platform includes a simulator, which simulator are you using?
Which real-time operating system are you using?

Check compatibility

 

A PSP compatible with your platform is already available. For more information, contact us at info@rapitasystems.com.

A PSP compatible with some (but not all) of the components of your platform is already available. We may be able to develop a PSP compatible with your exact platform. For more information, contact us at info@rapitasystems.com.

No PSP is currently available that is compatible with your platform, but we may be able to develop one. For more information, contact us at at info@rapitasystems.com.

Compiler,Arm Compiler,Already available
Compiler,CC-RH850 ,Already available
Compiler,Clang,Already available
Compiler,Code Composer,Roadmap
Compiler,GCC,Already available
Compiler,GNAT,Roadmap
Compiler,Tasking,Roadmap
Compiler,Other compiler,Not on the roadmap
Instruction set,AArch64,Already available
Instruction set,ARM,Already available
Instruction set,AURIX TriCore,Roadmap
Instruction set,PowerPC,Roadmap
Instruction set,RH850,Already available
Instruction set,RISC-V,Roadmap
Instruction set,VISIUM,Already available
Instruction set,x86,Already available
Instruction set,Other instruction set,Not on the roadmap
Debugger,Intel Processor Trace,Roadmap
Debugger,iSystem,Roadmap
Debugger,Lauterbach TRACE32,Already available
Debugger,PARTNER-Jet2,Already available
Debugger,Other debugger,Not on the roadmap
Simulator,ASTC VLAB,Roadmap
Simulator,MachineWare SIM-V,Roadmap
Simulator,QEMU* AArch64,Already available
Simulator,QEMU* Arm,Already available
Simulator,QEMU* x86,Already available
Simulator,Other simulator,Not on the roadmap
RTOS,None (Bare Metal),Already available
RTOS,DDC-I Deos,Roadmap
RTOS,eMCOS for AUTOSAR Adaptive Platform,Already available
RTOS,eMCOS for AUTOSAR Classic Platform (RV850),Already available
RTOS,FreeRTOS,Already available
RTOS,Green Hills INTEGRITY,Roadmap
RTOS,LynxOS,Roadmap
RTOS,PikeOS,Roadmap
RTOS,SafeRTOS,Roadmap
RTOS,Wind River VxWorks,Roadmap
RTOS,Other RTOS,Not on the roadmap
  • Solutions
    • Rapita Verification Suite
    • RapiTest
    • RapiCover
    • RapiTime
    • RapiTask
    • MACH178

    • Verification and Validation Services
    • Qualification
    • Training
    • Integration
  • Latest
  • Latest menu

    • News
    • Blog
    • Events
    • Videos
  • Downloads
  • Downloads menu

    • Brochures
    • Webinars
    • White Papers
    • Case Studies
    • Product briefs
    • Technical notes
    • Software licensing
  • Company
  • Company menu

    • About Rapita
    • Careers
    • Customers
    • Distributors
    • Industries
    • Locations
    • Partners
    • Research projects
    • Contact
  • Discover
    • AMC 20-193
    • What is CAST-32A?
    • Multicore Timing Analysis
    • MC/DC Coverage
    • Code coverage for Ada, C & C++
    • Embedded Software Testing Tools
    • Aerospace Software Testing
    • Automotive Software Testing
    • Certifying eVTOL
    • DO-178C
    • WCET Tools
    • Worst Case Execution Time
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®

All materials © Rapita Systems Ltd. 2023 - All rights reserved | Privacy information | Trademark notice Subscribe to our newsletter