A challenge with a standard MCU is that the controller is running high interrupt priorities and fast control loops, and the application requires an interrupt to do the communications bridge. A solution is to combine a C2000 device with a dedicated microprocessor that becomes the host controller. The host controller runs the communications or it runs the logic profiles, or it could be controlling sequencing and system monitoring. It is an interrupt driven engine, which allows the loop controller to focus on the real-time control. This combination can run more and faster loops, and smaller sampling windows without having to compromise between the interrupt handlers for the communications bridge. This has been a traditional solution in many different architectures combining a C2000 class device and a device such as an ARM or other dedicated host processor running its own operating system, like embedded Linux for example, or running something like Safe RTOS or Free RTOS. Texas Instruments has developed the Concerto™ MCU as a solution with both cores in one optimized control system, the C2000 core and an ARM Cortex™-M3 core. A further advantage of the Cortex-M3 core is that it is a low power device. Each processor has been given its own system tasks, without worrying about a communications bridge in between. There is no need to worry about transferring data via I2C, SPI, CAN, or even a memory interface which is an added delay between the two separate devices when communicating with one another. In Concerto the best of the C2000 core and the best of the ARM Cortex core have been combined, with an interprocessor communications pipeline, in one package.