Article ID: 000093377 Content Type: Troubleshooting Last Reviewed: 11/30/2023

Why do I sometimes see CPB corruption when I run a Factory or Firmware Update Image on my SoC Remote System Update enabled Intel® Stratix® 10 or Intel Agilex® FPGA system?

Environment

  • Intel® Quartus® Prime Pro Edition
  • BUILT IN - ARTICLE INTRO SECOND COMPONENT

    Critical Issue

    Description

    Due to a problem in the Device Firmware from the Intel® Quartus® Prime Pro Edition Software version 20.3 and later, SoC Remote System Update (RSU) Factory update or Firmware Update images flows may fail at run time with RSU State error code 0xf004d003 or 0xf004d00c if the Update Image is in the last slot in the  RSU Configuration Pointer Block (CPB), or is followed by only canceled CPB entries. 

    The RSU Configuration Pointer Block (CPB) in flash stores the location and order of the enabled RSU boot partitions and contains 508 slots.  When the table becomes full, it auto-compresses.

     

    See the Intel Agilex® Hard Processor System Remote System Update User Guide and Intel® Stratix® 10 Hard Processor System Remote System Update User Guide for more information on Remote System Update. 

     

    Resolution

    To work around this problem:  

    When writing the Factory / Firmware Update Image to the flash, ensure it's not the last entry in the CPB table, else force a CBP compression (by running rsu slot_disable <slot> and then rsu slot_enable <slot> )

    AND

    Do not cancel (disable) any RSU slots after writing Factory / Firmware Update Image to the flash, before POR (and the Update Image running)

     

    To detect if the Factory / Firmware Update Image is in the last slot:  u-boot example: 

    Save the CPB to memory using the rsu save_cpb command:  rsu save_cpb <address>

    Examine the CPB using md.b <address+slot offset> 8

    rsu save_cpb 0x2000 0000

    md.b 0x20000ff0  8

    md.b 0x20000ff8  8

    Empty slots will contain  FF FF FF FF FF FF FF FF; cleared slots will contain all 00s   

     

    This problem is scheduled to be fixed in a future release of the Device Firmware for Intel Agilex® and Intel® Stratix 10 devices.

     

    Related Products

    This article applies to 3 products

    Show all