Injecting an Error in Configuration RAM - Injecting an Error in Configuration RAM - 2026.1 English - UG643

Standalone Library Documentation: BSP and Libraries Document Collection (UG643)

Document ID
UG643
Release Date
2026-06-23
Version
2026.1 English

Here are steps illustrating how to inject an error in the configuration RAM for test purposes.

  1. Stop Scan
  2. Inject Error
    Note: The error injection shall be done with valid CFRAME address and valid row.
    • For valid range of addresses, refer to the LAST_FRAME_TOP (CFRAME_REG) and LAST_FRAME_BOT (CFRAME_REG) registers.
    • For valid row, refer to the CFU_ROW_RANGE (CFU_APB) register.

    To inject uncorrectable error, ensure to inject in alternate bit positions in the same qword. To inject CRC error, ensure to inject in alternate bit positions of the same qword in 3 or more than 3 positions. Refer to the xsem_cram_example.c file in the examples directory. For register information, see Versal Adaptive SoC Register Reference (AM012).

    The safe location to perform error injection is QWORD 12 which has ECC bits. The error injection does not change the design behavior.

    When an uncorrectable/CRC error or correctable error (correction is disabled in the configuration) is detected by XilSEM, the CRAM scan on PLM is stopped and the user is notified over IPI. In such case, ensure to reprogram/ restart to recover the error.

  3. Start scan to detect/correct injected error

Wait for the XilSEM library to detect and optionally correct the error (if configured to do so) and report the error.

Note:
  • If correction is disabled in the configuration options, then XilSEM is stopped after detecting the error. Ensure to initialize the scan to start again or reprogram the bitstream. If the error persists, XilSEM continue to report the same error and stop the scan after each restart or reprogram.
  • For correctable error, XilSEM corrects the error (if detect and correct option is selected) and records the error location details in PMC RAM RTCA. You can access this information using the following XilSEM client interfaces:
    • XSem_CmdCfrGetStatus for monolithic devices
    • XSem_Ssit_CmdGetStatus for SSI technology devices

    For uncorrectable and CRC errors, XilSEM only reports the error without providing any additional information.