RapiTime support specification

Supported CPU
Developing RapiTime support for a specific target processor consists of writing a target specific library for the RVS API. To provide detailed timing analysis and determination of worst-case execution times (WCET) RapiTime requires a library that supports generation of timing traces. A generic library is supplied with RapiTime to allow a quick start.

Often, it is the case that a specific library can be developed which considers the impact of the target processor, the compiler, the data collection method, and maybe also the RTOS. This can be done through Rapita Systems' Target Integration Service or by implementing the advice of the Integration Guide, supplied as part of the standard RVS documentation.

When we provide a tool qualification pack for DO-178B/DO-178C (DO-330) or ISO 26262 as part of our qualification service, this will also include tests for the processor-specific target library.

Will RVS work with my system?

RVS tools can be used on projects built with almost any compiler. 

The non-exhaustive list below shows some of the compilers we have worked with:


  • GNAT Pro


  • DS-5
  • armcl


  • Borland C++

Cosmic Software


  • GCC
  • G++

Green Hills

  • Ada MULTI

IAR Systems

  • Embedded Workbench


  • C51


  • Visual Studio


  • CodeWarrior HCS12


  • CC166

Texas Instruments

  • CCSv6
  • CL500
  • CL2000
  • C6X
  • C28X


  • Diab

Due to their flexible integration strategies, RVS tools can collect data from almost any target CPU.

The non-exhaustive list below shows some of the architectures that RVS tools can be used with:


  • ARM7
  • ARM9
  • ARM10
  • ARM11
  • Cortex-M
  • Cortex-R
  • Cortex-A

Analog Devices

  • Blackfin
  • SigmaDSP
  • TigerSHARC
  • ADSP-21xx


  • AT90CAN128

Cobham Gaisler

  • LEON3

Freescale Semiconductor

  • 68000
  • 680x0
  • ColdFire
  • M-CORE
  • Power Architecture (MPC5xx, MPC55xx, MPC56xx)
  • ARM Cortex-M microcontrollers (Kinetis E series, Kinetis K series, Kinetis L series, Kinetis M series, Kinetis W series).
  • 56k DSP family
  • QorIQ (P2010, P2020, P4080, P5010, P5020, P5021, P5040)


  • PowerPC (PPC) implementations:
    • G1 (601)
    • G2 (602, 603, 604, 620)
    • G3 (740/750)
    • 7xx/750 family
    • G5/970 series
    • 401
    • 403
    • 405
    • 440 range


  • XE166 family (XE161, XE162, XE164, XE167, XE169)
  • XC 2000 family (XC2200, XC2300, XC2700)
  • C166 family
  • TriCore (TC1130, TC1724, TC1728, TC1766, TC1767, TC179x, TC1796 , TC1797, AUDO)
  • Tricore Aurix (TC21x, TC22x, TC23x, TC24x, TC26x, TC270, TC290)
  • XMC1000


  • x86
  • Pentium
  • Atom

NXP Semiconductors

  • ARM7-based series (LPC2100, LPC2200, LPC2300, LPC2400)
  • ARM9-based series (LPC2900, LPC3100, LPC3200)
  • ARM Cortex-M0 based series (LPC1100, LPC1200)
  • ARM Cortex-M0+ based series (LPC800)
  • ARM Cortex-M3 based series (LPC1300, LPC1700, LPC1800)
  • ARM Cortex-M4 series (LPC4000, LPC4300)

Renesas (previously Hitachi, Mitsubishi, NEC)

  • V850
  • V850E
  • V850ES
  • V850E2
  • RX family
  • RZ family
  • SuperH family
  • RH850 Family

Rockwell Collins

  • AAMP

Rolls Royce



  • ARM-based parts (STR7, STR9, STM32 F0, STM32 F1, F2, L1, W, STM 32 F3, F4)
  • ST10
  • ST20
  • ST40

Texas Instruments

  • MSP430
  • TMS320 (DSP)
  • TMS570
  • C2000
  • Stellaris (ARM Cortex-M3)
  • Hercules - TMS570 (ARM Cortex-R4)
  • TMS470M ARM Cortex-M3
  • RM4 ARM Cortex-R4

We are able to cater for a wide variety of systems in addition to those stated above. Please contact us if you have any questions.

RVS tools support the following languages:

  • Ada
  • C
  • C++

They also support projects with mixed languages.