INTEL DOES NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THIS PATCH WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THIS PATCH WILL BE UNINTERRUPTED OR ERROR-FREE. //**************************************************************** quartus-21.4-0.72-readme.txt Readme file for Intel(R) Quartus(R) Prime 21.4 Patch 0.72 Copyright (C) Intel Corporation 2019 All right reserved. Patch created on Oct. 5, 2022, 3:11 a.m. Patch Case#: 15012034486 Patches included: 0.45,0.66,0.70 Patches conflicted: //**************************************************************** Description: This patch fixes the issue of possible M20K functional failure after partial reconfiguration on Agilex devices. This patch also addresses the following internal error that the Fitter may encounter on Agilex devices: Internal Error: Sub-system: U2B2_CDB, File: /quartus/db/u2b2/u2b2_re_network_checker.cpp, Line: 174 [Issue tracking number: 15012086354] Patch# 0.45: This patch addresses the following internal error that the Fitter may encounter on Agilex devices during the retime stage: Internal Error: Sub-system: LAB, File: /quartus/legality/lab/lab_fm_40_config_creator_module.cpp, Line: 1513 Patch# 0.66: While populating hipis into the netlist at the end of routing stage, we did not handle the cross partition hipis correctly. It is an edge case which has already been fixed in 22.3. Special check has been added in the patch to handle the cross partition hipis and avoid modifying/touching them. Patch# 0.70: None Caution - You must either have previously installed the Intel(R) Quartus(R) Prime 21.4 software or must install the Intel(R) Quartus(R) Prime 21.4 software before installing this patch. Otherwise, the patch will not be installed correctly and the Intel(R) Quartus(R) Prime software will not run properly. Note: - means this patch includes those patches. If you already installed those patches, you can safely install this new patch on top. - means this patch conflicts with those patches. If you have any of those patches installed, don't install this patch. Contact Intel for further support.