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

Engineering 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

NAVAIR FACE & SOSA TIM and Expo
2023-09-12
DASC 2023
2023-10-01
HISC 2023
2023-10-17
Aerospace Tech Week Americas 2023
2023-11-14
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

Challenges of certifying multicore avionics in line with A(M)C 20-193 objectives - ATW Europe 2023
Streamlined software verification with RVS 3.18
Sequence analysis with RapiTime
Visualize call dependencies with RVS thumbnail
Visualize call dependencies 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 93 351 02 05
info@rapitasystems.com
Rapita Systems S.L.
Parc UPC, Edificio K2M
c/ Jordi Girona, 1-3
Barcelona 08034
Spain

Working at Rapita

Careers

Careers menu

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

Measuring response times and more with RapiTime

Breadcrumb

  1. Home
  2. Blog
  3. Measuring response times and more with RapiTime
Daniel Wright & Greg Manning
2023-03-10

Analysis of the timing behavior of avionics software helps avoid errors such as timing overruns and is needed to support DO-178C certification.

While many timing requirements relate to the worst-case execution time of software, some may relate to other metrics such as response time, periodicity of execution, or separation between different instances of a sequence running.

Execution time vs. response time

The execution time of a piece of software is the time taken for a task to finish, ignoring time spent executing other functions or interrupts.

The response time of a piece of software is the total time taken for a task to finish, including time spent executing code in other functions or interrupts.

 

As of RVS 3.18, RapiTime includes a sequence analysis feature that provides a flexible framework for making these kinds of timing observations. This lets you define sequences of checkpoints within your code across which you want to take measurements. For each sequence, you can define the measurements you want taken, which can be the elapsed time between any two checkpoints within the sequence. After measurements have been defined, RapiTime can instrument your code appropriately, collect the necessary results during software execution, and display these results in your RapiTime report.

 

Sequence analysis conceptual diagram
Interesting timing metrics across and between sequences include response time, periodicity and separation
Checkpoints and measurements for RapiTime sequences
Checkpoints and measurements for a sequence configured in RapiTime
Results from RapiTime sequence analysis
Results from measuring execution of sequences in RapiTime
❮ ❯
    

This flexible framework also supports multicore timing analysis such as that carried out in our MACH178 solution to meet A(M)C 20-193 objectives for multicore DO-178C projects. Sequence analysis makes it possible to measure end-to-end timing metrics for sequences of events when multiple tasks run simultaneously, even when sequences involve checkpoints executing on different cores (as shown below).

 
References support distinguishing between different instances of sequences
Example multicore sequence involving multiple instances of a sequence executing on multiple cores, for which timing results can be collected by RapiTime
 

To support analysis in situations where multiple instances of a task may be running simultaneously, we needed to have a way to uniquely attribute checkpoints as belonging to a specific instance of a sequence. We did this by annotating each checkpoint with a sequence reference. When you define a checkpoint, you can supply a snippet of code that returns an integer shared by all checkpoints in the sequence, and is unique to each instantiation of the sequence. When each checkpoint is hit, this code is evaluated and the resulting integer is recorded in the checkpoint. This allows RVS to demultiplex sequences that execute simultaneously, so long as there is a distinguishing integer available.

 
References support distinguishing between different instances of sequences
Results from different instances of a sequence can be collected by using references – in this example, “num” is used as a reference as it has a unique value for each instance of the sequence
 

We're looking forward to see how RVS’s new sequence analysis feature can help you verify your critical software. We’ll be building on the feature to support more complex, non-linear sequences and sequences where no single distinguishing integer reference is available in future RVS versions, stay tuned!

To learn more about sequence analysis, visit our feature page or contact us. For more information on multicore certification, visit our MACH178 page.

DO-178C webinars

DO178C webinars

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
5 key factors to consider when selecting an embedded testing tool

Related blog posts

Setting up a free-running timer on the STM32 Discovery F4 board

.
2013-11-25

Is Windows Safe Mode faster for code?

.
2013-10-29

Using Timed Finite Automata to define the timing behaviour of a system

.
2013-09-25

Things that make real-time hard: DRAM refresh

.
2013-09-18

Pagination

  • First page « First
  • Previous page ‹ Previous
  • Page 1
  • Page 2
  • Current page 3
  • Page 4
  • Page 5
  • Page 6
  • Page 7
  • Page 8
  • Page 9
  • Next page Next ›
  • Last page Last »
  • 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