Sebastian Huber c347dd177e testsuites/validation: Bound the ISR wait
CallWithinISR() raises an interrupt with Cause_tm27_intr() and then
waits for the handler to run.  The wait was an unbounded busy loop.

Not every BSP can raise an interrupt in software.  moxie, or1k and
x86_64 use the default of <rtems/tm27-default.h>, where
Cause_tm27_intr() does nothing, and the microblaze definition is empty
as well.  The wait spins forever there, so the test case never ends and
takes every later case of the test suite with it.  The unit test suite
produced no result at all on six of the eleven simulators of the
programme for this reason.

Give up after ten million iterations and fail the test case.  The
interrupt arrives a few instructions after it was raised, so the bound
is far out of the way where the mechanism works.  Do the check only
when the bound is reached, because an assertion in the loop would
record ten million test steps.

The unit test suite reports eight test cases and one failure now
instead of hanging, and the failure names Cause_tm27_intr().

Update #5710.

Assisted-by: Claude:claude-opus-5 claude-code
Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
2026-08-20 17:40:16 -05:00
…
2026-02-01 19:24:33 -06:00
…
…

Real-Time Executive for Multiprocessing Systems

RTEMS is a real-time executive (kernel) which provides a high performance environment for embedded applications with the following features:

  • Standards based user interfaces.
  • Multitasking capabilities.
  • Homogeneous and heterogeneous multiprocessor systems.
  • Symmetric Multiprocessing (SMP):
    • Cluster scheduling: Job-level fixed prority scheduler (EDF) with support for one-to-one and one-to-all thread to processor affinities.
    • Locking protocols with transitive priority inheritance, priority ceiling, MRsP and OMIP.
  • Event-driven, priority-based, preemptive scheduling.
  • Scalable timer and timeout support.
  • Optional rate monotonic scheduling.
  • Intertask communication and synchronisation.
  • Priority inheritance.
  • Responsive interrupt management.
  • Dynamic memory allocation.
  • Dynamic code loading using run-time link editing.
  • File systems, IMFS, FAT, RFS, JFFS, NSFv4 (with LibBSD)
  • High level of user configurability.
  • Link-time configurable schedulers.
  • Linker-set based initialization (similar to global C++ constructors).
  • Drivers for I2C, SPI and LibBSD has NIC, USB, SD/MMC and Framebuffer.
  • Open source with a friendly user license.

RTEMS Project:

Project git repositories are located at:

Online documentation is available at:

RTEMS Doxygen for CPUKit:

RTEMS POSIX 1003.1 Compliance Guide:

RTEMS Discourse User forum for questions, answers and examples:

RTEMS Discord for support:

RTEMS Mailing Lists for general purpose use the users list and for developers use the devel list.

The version number for this software in releases is located in the VERSION file if present.

S
Description
RTEMS is a ​real-time executive in use by embedded systems applications around the world and beyond
Readme
141 MiB
0 Stars 1 Watchers 0 Forks
Languages
C 93.9%
Assembly 3.4%
Ada 1.4%
Python 0.3%
HTML 0.3%
Other 0.4%