Subsystem Restart - Restart of a specific subsystem Subsystem Shutdown - Shutdown of a specific subsystem During initialization of the PLM modules, the PLMI initializes the Error Manager, enables errors, and sets error action for each error in accordance with the Error Table structure defined in the xplmi_err.c file.ДЇollowing are the error actions supported for each error in PMC and PSM: The PLM Error Manager provides APIs for assigning a default error action for errors present in PMC and PSM in response to an error. All fatal errors routed to PMC/PSM Error Manager can either set to be handled by HW ( and trigger a SRST/PoR/PS Error Out) or trigger an interrupt to PMC/PSM. The Versal device has a dedicated error handler in PMC and PSM to aggregate all the fatal errors across the SoC and handle them. Error Handling in PLM Error Management HW Id_code = 0x14ca8093 //Add ID_CODE as per the Hardware Modules can register event handlers, IPI handlers, CDO commands, and scheduler events with the PLM interface layer.ДЇollowing are the list of modules present in the PLM: Depending on the modules selected in the configuration, different modules are initialized. The PLM application layer contains the module initialization and start-up tasks. Each functionally distinct feature is designed as a module.

The PLM is designed with a modular subsystem-based configuration, and task-based services.

Please refer to UG1283 for PDI Specification Modules in PLM PLM copies the CDOs to PMC RAM in 64K chunks, decodes and processes them. PLM decodes and passes this information to various modules for configuration. The CDO commands are registered by each module during module initialization phase. These files are generated by the tools and are input to PLM. Any system configuration in Versal will come in the form of a CDO to PLM. Configuration Data ObjectД¬onfiguration Data Object (CDO) contains set of commands which are required for configuring various components in the system. PLM also supports loading of the partial PDIs during run time. Once the PLM starts running, it will decode and process the rest of the PDI and boot up the system by loading the partitions present in the PDI. After the initial boot is complete, PLM is responsible for Error Management, Partial Reconfiguration, Subsystem Shutdown/Restart, Health Monitoring and Soft Error Mitigation and remains active throughout the lifetime of the system.Дuring the initial boot, the Boot ROM decodes the Programmable Device Image (PDI) and loads the PLM into the PPU RAM.

It also takes care of secure boot which are authentication and/or decryption. PLM is responsible for doing the system initialization, booting and configuration of various devices as a part of Loader. PPU has 384 KB of PPU RAM and 128 KB of PMC RAM. The Platform Management Controller (PMC) in Versal has two Platform Processing Units (PPUs) to run Boot ROM and PLM respectively. 15.3 PLM Compatibility between releases.

Failed to read boot.elf