RTXC/mp - Multiprocessor/Multicore RTOS

The fourth RTXC Quadros framework, RTXC/mp, is for use in those applications that require more than one processor. The type of multiprocessing is up to you: System-on-Chip (SoC), DSP farm on a board, a loose collection of CPUs, MCU and DSP, homogeneous or heterogeneous. You make the choice depending on your requirements.

RTXC/mp is designed for applications with multiple cores or multiple processors. Coupled with Poly-Messenger from PolyCore Software, it provides an advanced multi-core run-time platform, helping to reduce complexity and time-to-market. Whether it's an SoC design or multiple CPUs, MCU or DSPs, heterogeneous or homogeneous, RTXC/mp has the needed support. It uses the same kernel services as RTXC/ms which means you can reuse your application code as your needs evolve from a single processor to multiple.

Poly-Messenger is an advanced Inter-Processor Communication (IPC) Framework, designed to allow systems and application developers to more effectively design, program, and manage multi-core systems. Poly-Messenger enables different cores to inter-operate at the board or chip level.

The combined Poly-Messenger and RTXC/mp framework allows you to shift processing loads from overloaded CPUs, MCUs or DSPs to those that are under-utilized. Use RTXCgen to make changes to the application specification and then recompile the tasks for the CPU where they are to be relocated.

The kernel services of RTXC/mp are the same as those for RTXC/ms, making the particular RTOS framework transparent to the application code. That transparency means that you can reuse your application code as your needs evolve from one processor to many. Or, from many to one if you prefer. It's your choice. API transparency also means that you can shift processing loads from overloaded CPUs to those that are less heavily loaded. It's easy. You make some simple changes to the application specification via RTXCgen and then recompile the tasks for the CPU on which they are to be relocated.

You can also add the Single Stack kernel, RTXC/ss, to the RTXC/mp framework but certain limitations apply. The services of the RTXC/ss API are not useable on multiple processors. Thus, Threads and the objects they reference must exist on the same physical processor as the calling Thread.

RTXC/mp features

• Same features as for RTXC/ms framework
• Transparency with RTXC/ms API
• User defined topology of processor network
• User defined Link Managers, including physical link and protocol
• Easy configuration of multiple processors and applications via RTXCgen
• RTXC/ss kernel can be added to the framework, with limitations

Further reading

Questions You Should Ask Before Making an RTOS Decision
Introduction to Real-time Operating Systems