mirror of
https://gitlab.rtems.org/rtems/rtos/rtems.git
synced 2026-10-06 10:59:48 +08:00
Sebastian Huber
d0545d272c
ScoreIsrValIsr checks that the context which an interrupt during the multitasking start interrupted ran on the stack of the thread which was running. A wrapper of the interrupt dispatch of the architecture takes the address of that stack, and there is one for six architectures only. Everywhere else the address stays zero, the check cannot pass, and it reports nothing but a line number, which says neither that the architecture is unsupported nor what was expected. Add the wrapper for mips, i386 and x86_64, and say in the check what a zero address means, so that the next port is told why it fails rather than left to find out. The frame which the mips dispatch receives is built on the stack of the interrupted context, so the address of the frame is an address within that stack. Its stack pointer member is not used. Only the path which the debugger stub takes fills it, and the interrupt path leaves it zero. The two x86 ports keep the frame base of the interrupted context in the frame pointer register and may then switch to the interrupt stack, so the wrapper has to take the value before the compiler establishes a frame of its own. A register variable does not do that, because the compiler emits its prologue first and the wrapper then reads its own frame. They get the same treatment as sparc, which has the problem for the same reason. Close #5712. Assisted-by: Claude:claude-opus-5 claude-code Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
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.