2.16 eNVM1 Becomes Inaccessible to FPGA Fabric Master After Executing SRAM-PUF Services

In the IGLOO 2 M2GL090/M2GL150 devices, the System Controller does not release the eNVM1 access after executing the following SRAM-PUF system services:

• Create User AC (Activation Code) service
• Delete User AC service
• Create User KC for an Intrinsic Key service
• Create User KC for an Extrinsic Key service
• Delete User KC service

The above system services are executed successfully. However, the eNVM1 is inaccessible to fabric master.

Any subsequent access to eNVM1 after this point, where eNVM1 is locked by the System Controller, results in a stall, and a Power on Reset (POR) is required to remove the stall.

Workaround:

Execute "Get Number of the Key Code (GET_NUMBER_OF_KC)" SRAM-PUF system services immediately after the above services.

• The additional GET_NUMBER_OF_KC services releases the eNVM1 access from the System Controller
• The firmware code for running SRAM-PUF services workaround must be executed from eNVM0, eSRAM,or DDR memories only, as the Fabric master does not get access to the eNVM1 that time