1.1. SmartVID-related Subcode Error Messages for Agilex™ Devices Only
From the previous error messages, you get the second-level error details based on the subcode stated. The following example shows the subcode errors related to the SmartVID. This is applicable for the Agilex™ devices only.
For the Stratix® 10 devices, the only indicator for the VID-related error is listed in Example: System Error Message of Configuration Failure due to SmartVID in Quartus® Prime Software.
SmartVID-related Subcode Error Messages
0xC801, customer_message = "Verify the address used in Quartus project matches that of the Voltage Regulator. Inspect the PMF/I2C bus traffic, ensuring proper pullups, contention, etc. "
0xC802, customer_message = "Voltage Regulator unable to achieve the requested voltage. Verify the correctness of Power Management and VID settings in Quartus project (e.g Slave device type, voltage output format, coefficient, translated votlage value unit, PAGE command, etc.)."
0xC803, customer_message = "Ensure External Master detects the ALERT_N assertion and send a VOUT_COMMAND to SDM within 200mS. Refer to the handshake requirement in Power Management User Guide.
0xC804, customer_message = "ITD fuse is out of range, file IPS case to get support from Intel."
0xC805, customer_message = "Internal Error while reading or decoding the Bitstream's Power Table, file IPS case to get support from Intel."
0xC806, customer_message = "Internal Error while reading or decoding the efuse values, file IPS case to get support from Intel."
0xC807, customer_message = "Failed to validate the vccl power is valid on the board, verify the board's power supply is in a good state."
0xC808, customer_message = "Error while sending CLEAR_FAULTS command, ensure Voltage Regulator supports this command."
0xC809, customer_message = "Error while sending VOUT_MODE command, ensure Voltage Regulator supports this command."
0xC80a, customer_message = "Error while sending PAGE_COMMAND command, ensure Voltage Regulator supports this command."
0xC80b, customer_message = "Error while sending VOUT_COMMAND command, ensure Voltage Regulator supports this command."
0xC80c, customer_message = "Error while sending READ_VOUT command, ensure Voltage Regulator supports this command."
0xC80d, customer_message = "Error while sending the vendor specific LTM4677 MFR_ADC_CTRL command, ensure Voltage Regulator supports this command."
0xC80e, customer_message = "The first I2C command has failed, no response from Voltage Regulator. Verify the address used in Quartus project matches that of the Voltage Regulator, inspect the PMBus/I2C bus traffic, pull-ups, bus contention, etc. The 'info' field of this error contains the target I2C address."
You can review the error messages in the message console. Alternatively, you can retrieve the error messages from the Configuration Debugger Tools in the Quartus® Prime software.
Tip: Some of the error messages listed in the Quartus® Prime System tab contains additional information that is useful when you are performing further analysis.
The following error messages show that the voltage regulator did not reach the correct voltage. The target and read voltages are listed in the Info section in the Quartus® Prime software.
Error Messages
Error (18950): Device has stopped receiving configuration data
Error (18948): Error message received from device: External hardware access error. (Subcode 0xC802, Info 0x032002EE, Location (0x00001800)
Error (18945): Voltage Regulator unable to achieve the requested voltage. Verify the correctness of Power Management and VID settings in Quartus project (e.g Slave device type, voltage output format, coefficient, translated voltage value unit, PAGE command, etc.)
For 0x032002EE, 0320 refers to the target voltage and 02EE refers to the actual voltage:
- 0x0320 (hexadecimal) = 800 mV (decimal)
- 0x02EE (hexadecimal) = 750 mV (decimal)