You are here: Home / Technical Services / 
2026-07-24 - 03:27

Dates and Events:

electronica 2026
10.11. - 13.11.

OSADL Articles:

2024-10-02 12:00

Linux is now an RTOS!

PREEMPT_RT is mainline - What's next?


2023-11-12 12:00

Open Source License Obligations Checklists even better now

Import the checklists to other tools, create context diffs and merged lists


2023-03-01 12:00

Embedded Linux distributions

Results of the online "wish list"


2022-01-13 12:00

Phase #3 of OSADL project on OPC UA PubSub over TSN successfully completed

Another important milestone on the way to interoperable Open Source real-time Ethernet has been reached


2021-02-09 12:00

Open Source OPC UA PubSub over TSN project phase #3 launched

Letter of Intent with call for participation is now available



OSADL Projects

OSADL QA Farm for Real-time of Zephyr

Worst-case latency monitoring with zyclictest

Various Zephyr reference systems undergo repeated load phases and latency measurements in the OSADL QA farm using the Zephyr zyclictest module. The two measurement phases, which determine the system’s worst-case latency, have a fixed duration of five hours and 33 minutes. They begin at 7:10 a.m. and 7:10 p.m. The number of cycles required depends on the measurement interval. To keep the fixed duration of five hours and 33 minutes with an interval of 200 µs, 100,000,000 cycles are needed, with 400 µs, 50,000,000 cycles are needed. Although the "zyclictest" program generates a relatively high interrupt load, it does not cause any other significant loads that could affect the system. Therefore, an additional load is generated in different ways depending on the board.

On the Olimex STM32F407 board (Zephyr 4.3.0), an additional background load is generated by continuously reading a sensor.

On the Raspberry Pi Pico board (Zephyr 4.3.99), the additional load is generated by a computational load on the CPU.

The results of the latest test run and the observed worst-case latencies of the last seven days are listed below. More information on building Zephyr can be found here. The Zephyr configuration (prj.conf) used for each board is specified as well.

STM32F407ZG

  • CPU Data: 1 core Arm Cortex-M4 @ 168 MHz, Zephyr was built with this prj.conf
Continuous worst-case latency monitoring
Results for Olimex STM32F407 on Zephyr

Longterm latency monitoring of STM32F407
Longterm latency monitoring of STM32F407

RP Pico 1

  • CPU Data: Dual-core Arm Cortex-M0+ @ 133 MHz, Zephyr was built with this prj.conf
Continuous worst-case latency monitoring
Results for Raspberry Pi Pico on Zephyr

Jitter analysis of the system
Longterm latency monitoring of Raspberry Pi Pico