Introduction
This page gives an overview of ipipsu driver which is available as part of the Xilinx Vivado and SDK distribution.
The heterogeneous multiprocessor system uses the inter-processor interrupt (IPI) structure
to exchange short interrupt-driven messages between processors in the system. The IPI
architecture allows the passing of messages across the system without the complications of
autonomous read-write transactions and polling inefficiency.
Source path for the driver:
https://github.com/Xilinx/embeddedsw/tree/master/XilinxProcessorIPLib/drivers/ipipsu/src
Driver Sources
The source code for the driver is included with the Vitis Unified Software Platform installation, as well as being available in the Xilinx Github repository.
Driver Name | Path in Vitis | Path in Github |
|---|---|---|
| ipipsu | <Vitis Install Directory>/data/embedded/XilinxProcessorIPLib/drivers/ipipsu | https://github.com/Xilinx/embeddedsw/tree/master/XilinxProcessorIPLib/drivers/ipipsu |
The driver source code is organized into different folders. The table below shows the ipipsu driver source organization.
| Directory | Description |
|---|---|
doc | Provides the API and data structure details |
data | Driver .tcl and .mdd file |
examples | Example applications that show how to use the driver features |
| src | Driver source files |
IPI Features
The IPIPSU block, provides the following features.- Supports processor communications including both an IPI interrupt structure and memory buffers to
exchange short private 32B messages between eight IPI agents. - Supports both blocking and nonblocking calls.
Links to Examples
Examples Path:
https://github.com/Xilinx/embeddedsw/tree/master/XilinxProcessorIPLib/drivers/ipipsu/examples
| Test Name | Example Source | Description |
|---|---|---|
| IPIPSU example | This examples sends a message to itself and confirms the message. |
IPIPSU example
This example sends a message to itself and receives it.
Expected Output
Hello IPI! [Build: Jul 2 2021 07:11:56] Interrupt ID: 67 Message Content: W0: 0x5851F42D W1: 0x40B18CCF W2: 0x4BB5F646 W3: 0x47033129 W4: 0x30705B04 W5: 0x20FD5DB4 W6: 0x1A8B7F78 W7: 0x502959D8 Triggering IPI and Waiting for Response... ---->Enter Interrupt Handler Message Received: W0: 0x5851F42D W1: 0x40B18CCF W2: 0x4BB5F646 W3: 0x47033129 W4: 0x30705B04 W5: 0x20FD5DB4 W6: 0x1A8B7F78 W7: 0x502959D8 Sent back Inverted Message. <----Exit Interrupt Handler Received response. Message : Response W0 -> 0x5851F42D : 0xA7AE0BD2 W1 -> 0x40B18CCF : 0xBF4E7330 W2 -> 0x4BB5F646 : 0xB44A09B9 W3 -> 0x47033129 : 0xB8FCCED6 W4 -> 0x30705B04 : 0xCF8FA4FB W5 -> 0x20FD5DB4 : 0xDF02A24B W6 -> 0x1A8B7F78 : 0xE5748087 W7 -> 0x502959D8 : 0xAFD6A627 Successfully ran Ipipsu selftest Example
Changelog
2019.1
- None
2019.2
- None
2020.1
2020.2
2021.1
Related Links
- NA