This section list the software pieces involved in demonstrating the TRD features.
Software |
Processor |
Function with respect to TRD use cases |
|---|---|---|
PLM |
PMC |
Controls various restarts and maintains the life cycle of the subsystem. |
ATF |
APU |
Arm Trusted firmware (Running on ARM EL3) interacts directly with PLM (through IPI) for various PM activities, including restarts. Like all PM related requests, Linux’s system and subsystem restart requests are eventually handled by ATF. |
XilPm Client lib |
RPU LS |
This is the client side API library to issue PM requests to PLM. RPU application issues various PM requests, including restarts through this library to the PLM. |
Linux |
APU |
Hosts Jupyter Notebook server to demonstrate TRD features. It also manages various APU peripherals, including FPD WDT through the respective drivers. Linux Runs on ARM EL2. |
Standalone App |
RPU LS |
PM aware application with standalone OS. It uses standalone drivers to control various peripherals, like UART and LPD WDT. It also establish and uses libmetal shared memory based communication channel with APU. |
Note
There are other software pieces in the stack, like u-boot, psm-firmware, etc. but are not mentioned above as they don’t actively participates in TRD demonstration.
Below diagram shows relationship and interaction between above pieces:
Please refer Versal ACAP System Software Developers Guide for more details on software stack and detailed development guide for each component.
Refer to Restart Use Cases section in the Appendix for details on each of the TRD use cases and the software components involved.