Your browser does not support JavaScript! Skip to main content
Free 30-day trial DO-178C Handbook RapiCoupling Preview DO-178C Multicore Training Multicore Resources
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  RapiCouplingPreview - DCCC analysis

Multicore Verification

  MACH178  MACH178 Foundations  Multicore Timing Solution  RapiDaemons

Engineering Services

  V&V Services  Data Coupling & Control Coupling  Object code verification  Qualification  Training  Consultancy  Tool Integration  Support

Industries

  Civil Aviation (DO-178C)   Automotive (ISO 26262)   Military & Defense   Space

Other

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

Latest from Rapita HQ

Latest news

SAIF Autonomy to use RVS to verify their groundbreaking AI platform
RVS 3.22 Launched
Hybrid electric pioneers, Ascendance, join Rapita Systems Trailblazer Partnership Program
Magline joins Rapita Trailblazer Partnership Program to support DO-178 Certification
View News

Latest from the Rapita blog

How to certify multicore processors - what is everyone asking?
Data Coupling Basics in DO-178C
Control Coupling Basics in DO-178C
Components in Data Coupling and Control Coupling
View Blog

Latest discovery pages

control_tower DO-278A Guidance: Introduction to RTCA DO-278 approval
Picture of a car ISO 26262
DCCC Image Data Coupling & Control Coupling
Additional Coe verification thumb Verifying additional code for DO-178C
View Discovery pages

Upcoming events

Avionics and Testing Innovations 2025
2025-05-20
DASC 2025
2025-09-14
DO-178C Multicore In-person Training (Fort Worth, TX)
2025-10-01
DO-178C Multicore In-person Training (Toulouse)
2025-11-04
View Events

Technical resources for industry professionals

Latest White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP
Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
View White papers

Latest Videos

Rapita Systems - Safety Through Quality
Simulation for the Motorola 68020 microprocessor with Sim68020
AI-driven Requirements Traceability for Faster Testing and Certification
Multicore software verification with RVS 3.22
View Videos

Latest Case studies

GMV case study front cover
GMV verify ISO26262 automotive software with RVS
Kappa: Verifying Airborne Video Systems for Air-to-Air Refueling using RVS
Supporting DanLaw with unit testing and code coverage analysis for automotive software
View Case studies

Other Resources

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

 Multicore resources

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 Contact Us

Lightweight instrumentation with RapiTask

Breadcrumb

  1. Home
Daniel Wright
2018-06-05

If you're working with multithreaded critical embedded software, you probably want to know how your task scheduling affects the execution behavior of your code. You may even need to provide evidence of this to certify your software. In this post, we show how to perform task scheduling analysis with RapiTask without having to instrument the tasks in a system directly.

We'll demonstrate this using an example system that includes multiple tasks (individual executables) and a context switch routine that prioritizes and schedules them (Figure 1).

 

context switch routine showing system architecture

 

Figure 1. System architecture

 

RapiTask works by adding instrumentation to the source code, so that when it is executed, a routine is called which logs and timestamps the execution.

To produce timing data in our example system, we instrument the context switch routine, but not the tasks themselves; Figure 2 shows an example of this.

void TaskSwitchContext( void )
{
RVS_I(5); // Context switch out
// Find the highest priority task pending and switch to it
TopReadyPriority = TopPriority;
while( ReadyTasksLists[ TopReadyPriority ].Pending == 0 )
{
TopReadyPriority -= 1;
}
TaskSwitchFrames(CurrentTask, ReadyTasksLists[ TopReadyPriority ]);
CurrentTask = ReadyTasksLists[ TopReadyPriority ];
RVS_I(6); // Context switch in
RVS_I(CurrentTask.Ident); // New task ID
}

Figure 2. Instrumenting the context switch routine; RVS instrumentation highlighted

Next, we run tests on the system with RapiTask to produce reports on the execution time behavior of the code during each test (Figure 3).

execution time behavior chart

Figure 3. RapiTask execution time behavior chart

This gives us data on every time each task starts execution, but doesn't tell us whether this is due to a new invocation of the task or resuming a previous execution that was pre-empted. To get this information, we have to take into account the system's scheduling priorities.

The names of the tasks highlighted in our example represent their priority; High has the highest priority, and Low has the lowest. Using this knowledge and the RapiTask report shown in Figure 3, we can safely infer when Medium is first invoked, when it resumes execution after being pre-empted by High , and when it finishes execution; these points are marked on Figure 3.

If you're an embedded engineer with a detailed understanding of your system's scheduling behavior, you can use RapiTask reports to easily identify issues in your code, for example cycle slips. Let's imagine that each time Medium is invoked, it must finish each execution within 50 ms. Using our knowledge of the system's priorities, we can infer when each invocation of Medium starts and ends and use this to identify cycle slips.

The approach to collecting execution time data described here means you don't need to instrument the tasks you're analyzing. This is useful when you can't instrument tasks (for example because you don't have access to the source code, only the executable, in a system like the one in Figure 1), or if you want to avoid the overheads of instrumenting them (for example because your target is resource-constrained).

If you want to know more about RapiTask, contact us or request a trial.

DO-178C webinars

DO178C webinars

White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis

Related blog posts

Software verification on the Solar Orbiter

.
2021-03-01

Out of the box RVS integration for DDC-I's Deos RTOS

.
2020-02-23

How to trace the source of deadlocks

.
2014-08-28

What's next for Ada?

.
2014-07-04

Pagination

  • Current page 1
  • Page 2
  • 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
    • Multicore Timing Analysis
    • Embedded Software Testing Tools
    • Worst Case Execution Time
    • WCET Tools
    • Code coverage for Ada, C & C++
    • MC/DC Coverage
    • Verifying additional code for DO-178C
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®
    • Data Coupling & Control Coupling
    • Aerospace Software Testing
    • Automotive Software Testing
    • Certifying eVTOL
    • DO-178C
    • AC 20-193 and AMC 20-193
    • ISO 26262
    • What is CAST-32A?

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