Sebastian Huber d869458bbc bsps/mips/jmr3904: Add the interrupt controller
The interrupt controller operations were not implemented.  Every one of
them returned RTEMS_UNSATISFIED, so ts-validation-intr reported 2511
failures, most of them because rtems_interrupt_vector_is_enabled() must
work for every valid vector.

Drive the controller of the TX3904.  A source passes when its level in
the interrupt level registers is greater than the level in the interrupt
mask register, so the level is both the priority and the enable, and the
vector numbers of the BSP are the source numbers of the controller.  A
bit of the interrupt status register reads as zero while its source is
asserted.  The two software interrupts of the processor are raised and
cleared in the cause register and are the only sources this board can
raise.

The sources which do not pass the controller are masked in the status
register, which the context of every thread enables completely, so they
report as enabled and nothing disables them.

The other BSPs of the architecture keep the operations which are not
implemented, now in their own file.

Thirteen failures remain.  They need a vector which the validation tests
can raise and also enable and disable, and this board has none: the
status register belongs to the context of a thread, so a disable of a
software interrupt would not survive a context switch.

Update #5688.

Assisted-by: Claude:claude-opus-5 claude-code
Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
2026-08-20 18:23:09 -05: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%