NXP Framework User Manual
PUBLIC
© NXP Semiconductors N.V.
Uncontrolled copy if printed
NXP Semiconductors
Inter-Platform Communication
Framework
Rev. 1.6
AP Software
4/18/2021
Software Development
Page 1 of 9
All information hereunder is per NXP’s best knowledge. This document does not provide for any
representation or warranty express or implied by NXP. NXP makes no representation or warranty that
customer’s applications or design will be suitable for customers’ specified use without further testing or
modification. Customers are responsible for the design and operation of their applications and products
using NXP products, and NXP accepts no liability for any assistance with applications or customer product
design. Customers should provide appropriate design and operating safeguards to minimize the risks
associated with their applications and products.
For reliable information on the NXP product please consult the respective NXP data sheet. Unless
otherwise recorded in a written agreement, all sales transactions by NXP are subject to our general terms
and conditions of commercial sale. These are published at http://www.nxp.com/about/about-nxp/our-
terms-and-conditions-of-commercial-sale:TERMSCONDITIONSSALE
Product Brief
Inter-Platform Communication
Framework (IPCF)
PUBLIC
© NXP Semiconductors N.V.
Uncontrolled copy if printed
NXP Semiconductors
Inter-Platform Communication
Framework
Rev. 1.6
AP Software
4/18/2021
Software Development
Page 2 of 9
1.0 Software Product Overview
Inter-Platform Communication Framework (IPCF) is a subsystem which enables applications, running
on multiple homogenous or heterogenous processing cores, located on the same chip or different chips,
running on different operating systems (AUTOSAR®, Linux®, FreeRTOS, Zephyr, etc.), to communicate
over various transport interfaces (Shared Memory, etc.).
IPCF is designed for NXP embedded systems and features low-latency and tiny-footprint. It exposes a
zero-copy API that can be directly used by customers for maximum performance, minimum overhead
and low CPU load. The driver ensures freedom from interference between local and remote shared
memory by executing all writing operations only in local memory domain. Customers can enforce
memory protection for their software with XRDC/SMPU peripherals.
Customers can choose to build exactly what they need in terms of hardware (HW), operating system
(OS) and transport interface.
1.1 Use cases
The following diagram illustrates some use cases addressed by IPCF.
Figure 1 IPCF use cases on multiple homogenous or heterogenous processing cores
PUBLIC
© NXP Semiconductors N.V.
Uncontrolled copy if printed
NXP Semiconductors
Inter-Platform Communication
Framework
Rev. 1.6
AP Software
4/18/2021
Software Development
Page 3 of 9
Figure 2 IPCF use case with multiple instances
Figure 3 IPCF use case for Linux kernel
Loading...