There is almost no learning curve, as the development tools and API stay nearly identical. PikeOS for MPU is embedded into CODEO as if it was just another architecture. That also makes migration from older applications remarkably simple. PikeOS Classic and PikeOS for MPU projects can even be managed in the same IDE at the same time.

More about CODEO

Since the development tools, such as the ROM-Image builder and the VMIT (Virtual Machine Initialization Table) builder, are shared between the two operating systems, PikeOS for MPU inherits the qualification status of its bigger brother. That together with the fact that PikeOS for MPU bases on SYSGO's well-proven virtualization technology, PikeOS for MPU comes with a head start in terms of certification.

Multi-core processors have entered the embedded market. However, unlike to desktop computing where all processor cores are of the same type, embedded SoCs (Systems-on-a-Chip) are highly specialized for a dedicated purpose. Therefore, you will often find heterogeneous processor cores on the same chip.

With the PikeOS family of products, you can manage the entire software stack of such a complex big SoC within one single CODEO workspace. The project wizards and editors support you while you are planning the architecture of AMP and SMP domains. Even anything in between can be designed. A typical setup on a Xilinx Ultrascale+ would look like as shown in figure 1: PikeOS running multiple partitions on the Cortex-A53 cores in SMP mode, while the Cortex-R5 cores are executing PikeOS for MPU in AMP mode.

During your development it might turn out that the current assignment of software applications to processor cores is not optimal. Fortunately, this can be fixed with almost no efforts, as the PikeOS solution allows you to utilize the same API, no matter whether the CPU provides an MMU or MPU.