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.

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.

The key to multiprocessing with the RTXC/mp framework is the Link Manager. It's a combination of code provided as part of the RTXC Quadros distribution and completed by the user, according to the physical and protocol characteristics of the link between any processors. The concept of RTXC/mp puts no limitation on the nature of the link or the protocol either. It can be shared memory, an asynchronous or synchronous serial link, Ethernet or some user-defined custom connection and protocol. Again, it's your choice. 

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 include:

• 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