Why does the Altera® Advanced Link Analyzer Crash or Produce Incorrect Results on Microsoft Windows 11* 25H2 Virtual Machines?
Description The Altera® Advanced Link Analyzer may crash or produce incorrect simulation results on Microsoft® Windows 11 version 25H2 virtual machines configured with ABI‑based virtual CPU models. This problem occurs because the Intel® Math Kernel Library (MKL) depends on hardware‑faithful x86 CPU execution semantics, which are not fully guaranteed by ABI‑based vCPUs in Microsoft Windows 11 25H2. Resolution To work around this problem, you can configure virtual machines as follows: Microsoft Windows* 11 version 25H2 Use a hardware-faithful vCPU (for example, VMware ESXi* or VMware Workstation* default vCPU) On KVM/QEMU platforms, enable host CPU passthrough Microsoft Windows Server 2022, Windows Server 2025, and Windows 11 version 24H2 or earlier ABI-based virtual CPUs are supported; no changes required Additional Information This problem only affects Microsoft Windows 11 version 25H2 virtual machines using ABI‑based virtual CPU models. Other Windows versions and hardware‑faithful virtual CPUs are not affected.Why do I unexpectedly observe intermittent DDM Errors?
Description Beginning January 10, 2026, executing commands in the terminal or GUI of Quartus® Prime Pro Edition software, Quartus Embedded Edition software or select standalone tools may cause the software or tool to crash with an error similar to the crash signature shown below. This error affects: Quartus Prime Pro Software versions v23.3 through v25.3.1 Standalone Quartus Prime Pro Programmer v23.3 through v25.3.1 Standalone Quartus Prime Pro Embedded Edition v25.3 and v25.3.1 Standalone Quartus Prime Pro Power Thermal Analyzer v25.3 through v25.3.1 This issue is not observed in Quartus Prime Pro Edition versions 23.2 or prior or Quartus Prime Standard Edition. Crash Signature: Error (22912): Unhandled exception: Fatal Error: Assertion failed tools/cpp/ddm/ddm_assessor.cpp:53: DDM_T::verify_token(token) : Cannot identify the client from function assertion_error in tools/cpp/ddm_report/ddm_report_msg.cpp@465 *** Fatal Error: Program termination requested *** *** Below is the stack trace at the time the error occurred. *** The lines beginning "Err Handler" represent frames relating *** to generating this report. *** The point at which the error occurred is somewhere after these lines. *** There may be a few frames representing standard/library code *** before the Quartus frames begin. *** The search for the error should begin with the Quartus frames. *** Unwinder: libunwind *** Stack depth: 15 Quartus 0x24e67: err_terminator() + 0x1bc (ccl_err) Quartus 0xb036a: __cxxabiv1::__terminate(void (*)()) + 0xa (stdc++) Quartus 0xb03d5: (stdc++) Quartus 0xb0628: (stdc++) Quartus 0x1680d: void ddm_throw<DDM_RUNTIME_ERROR>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x26d (ddm_report) Quartus 0x13fae: DDM_REPORT::DDM_ASSERTION_HANDLER::assertion_error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) const + 0xde (ddm_report) Quartus 0x12a52: DDM_REPORT::ASSERTION_HANDLER::error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x72 (ddm_report) Quartus 0x13e64: DDM_REPORT::detail::assert_at_line(char const*, char const*, int, char const*, ...) + 0x1b4 (ddm_report) Quartus 0x205fb0: ddm_set_lassessor(DDM_T_ASSESSOR*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x60 (ddm) Quartus 0xf4445: DMS_MANAGER::DMS_MANAGER() + 0x5c5 (dni_dms) Quartus 0xf45b2: DMS_MANAGER::get() + 0x7a (dni_dms) Quartus 0xf6db4: _GLOBAL__sub_I_dms_manager.cpp + 0x58 (dni_dms) Quartus 0x647e: (ld-linux-x86-64) Quartus 0x6568: (ld-linux-x86-64) Quartus 0x202ca: (ld-linux-x86-64) Resolution To work around this problem: For Windows machines Download and unzip the Quartus Prime Pro version zip file that matches your Quartus Prime Pro version from this KDB. Double click on the executable ending in “windows.exe”. When the GUI pops up, press Next. Note that the GUI may look slightly different depending on the version of Quartus you are using. Accept the license agreement Specify the directory where the patch needs to be applied which may be a different location than Quartus install if you have standalone tools in a different directory from your Quartus Prime Pro software installation. Keep “Allow Patch to be uninstalled” selected. Select the software in which to install the patch: The patch will install in the directory of the software or tool you have selected. You will see an uninstall directory for the patch in your software or tool folder where patch is installed; it will contain an executable to uninstall the patch if required for any reason. To confirm patch is installed, you can run quartus_sh -v or corresponding version command for your tool via command line. Alternatively, you can Open Quartus in the GUI and select Help → About Quartus Prime in the main menu. If you are opening up a standalone tool you will navigate to Help-> About <tool_name>. For the Command Line Implementation of the patch in Windows, use the following command: <patch_filename.exe> --mode unattended --installdir <your_install_directory> --accept_eula 1 --patch_to [quartus|qprogrammer|qemb|pta] # An example to patch Quartus Prime Pro Edition Software v25.3: quartus-25.3-0.27-windows.exe --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 # An example to patch the Standalone Programmer for Quartus Prime Pro Software v25.3: quartus-25.3-0.27-windows.exe --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 --patch_to qprogrammer For Linux machines: Download and unzip the Quartus Prime Pro version zip file that matches your Quartus Prime Pro version from this KDB. Ensure you run chmod +x on the file ending with linux.run. Run in the command line: ./<installation_patch_run_file>. When GUI pops up, press Next. Note that the GUI may look slightly different depending on the version of Quartus you are using. Accept the license agreement Specify the directory where the patch needs to be applied which may be a different location than Quartus install if you have standalone tools in a different directory from your Quartus Prime Pro software installation. Keep “Allow Patch to be uninstalled” selected. Select the software in which to install the patch: The patch will install in the directory of the software or tool you have selected. You will see an uninstall directory for the patch in your software or tool folder where patch installed; it will contain an executable to uninstall the patch if required for any reason. To confirm patch is installed, you can run ./quartus_sh -v or corresponding version command for your tool via command line. Alternatively, you can Open Quartus in the GUI and select Help → About Quartus Prime in the main menu. If you are opening up a standalone tool you will navigate to Help-> About <tool_name>. For the Command Line Implementation of the patch in Linux, use the following command: ./<patch_filename.run> --mode unattended --installdir <your_install_directory> --accept_eula 1 --patch_to [quartus|qprogrammer|qemb|pta] # An example to patch Quartus Prime Pro Edition v25.3: ./quartus-25.3-0.27-linux.run --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 # An example to patch the Standalone Programmer for Quartus Prime Pro Software v25.3: ./quartus-25.3-0.27-linux.run --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 --patch_to qprogrammer This problem has been fixed in Quartus® Prime Pro Edition Software version 26.1. The below table lists the patches that are available and the associated patch number. The patch zip files are attached to the KDB below: Quartus Prime Pro Edition Version Patch Number 23.3 0.52 23.4 0.70 23.4.1 1.01 24.1 0.52 24.2 0.64 24.3 0.35 24.3.1 1.29 25.1 0.36 25.1.1 1.31 25.3 0.27 25.3.1 1.02Why does PTP accuracy error go beyond +/- 1.5ns during dynamic reconfiguration between GTS Ethernet Hard IP and Triple-Speed Ethernet IP in Quartus® Prime Pro Edition version 26.1 and earlier?
Description When using the GTS Dynamic Reconfiguration Controller IP flow in Quartus® Prime Pro Edition version 26.1 or earlier to perform dynamic reconfiguration between the GTS Ethernet Hard IP and the Triple-Speed Ethernet (TSE) IP, the PTP (Precision Time Protocol) accuracy error for the GTS Ethernet Hard IP may exceed ±1.5ns in this scenario. This PTP accuracy problem does not occur with the TSE IP in this case. Resolution No workaround is available so far. This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.Why does the Single Floating Point Variable Streaming Reverse FFT IP produce an incorrect output when the input order is set to Natural?
Description Due to a problem in the Quartus® Prime Software version 25.3.1 and earlier, the "Natural" option for setting "Input Order" is incorrectly available for selection and unsupported when generating the FFT IP. This option is available when using the following parameters: Direction: "Reverse", Data Flow: "Variable Streaming", Representation: "Single Floating Point". Resolution This problem is scheduled to be fixed in release 26.1 of the Quartus® Prime Software with the removal of the unsupported “Natural” option. Additional Information This problem affects the FFT IP in Quartus® Prime Software versions 17.0 to 25.3.1.Why does Ashling* RiscFree* IDE for Altera FPGAs software version 25.4.1 turns compiler warnings into errors?
Description In the Ashling* RiscFree* IDE for Altera FPGAs software version 25.4.1 (31 st Oct 2025) and later, you might see compilation error related to the following errors: Implicit int types (-Werror=implicit-int) Implicit function declarations (-Werror=implicit-function-declaration) Typos in function prototypes (-Werror=declaration-missing-parameter-type) Incorrect uses of the return statement (-Werror=return-mismatch) Using pointers as integers and vice versa (-Werror=int-conversion) Type checking on pointer types (-Werror=incompatible-pointer-types) This is due to an update in GCC 14 – GNU: Certain warnings are now errors, which affects future GCC versions. For more information, Ashling* RiscFree* IDE for Altera FPGAs software version 25.3.1 (1 st August 2025) is using GCC 13.2. Ashling* RiscFree* IDE for Altera FPGAs software version 25.4.1 (31 st Oct 2025) is using GCC 15.2. Thus, Ashling* RiscFree* IDE for Altera FPGAs software version 25.4.1 (31 st Oct 2025) and future versions are affected. Note that Ashling* RiscFree* IDE for Altera FPGAs software version 25.4.1 (31 st Oct 2025) is paired with Quartus ® Prime Pro Edition software version 26.1. Resolution GNU recommends resolving all the new errors for better code quality. If necessary, you may refer to the workaround – GNU: Turning errors back into warnings. In Board Support Package Editor, add "-fpermissive" in hal.make.cflags_user_flags.Critical Warning(25207): A programming file will not be generated because the assembler identified some pins have missing I/O Standard assignments. Refer to the I/O Assignment Warnings table in the fitter report for details.
Description Due to a problem in the Quartus® Prime Pro Edition Software version 25.3.1 and earlier, you might see this critical warning during the Assembler stage when assigning the I/O Standard to the negative differential pins of the Agilex® 5 FPGA devices and Agilex® 3 FPGA devices. This is due to the I/O Standard of the negative differential pin is not reflected in the Quartus® .qsf file even though the I/O Standard had been assigned to the negative differential pin in the Pin Planner. Resolution To work around this problem, add the assignment below in the .qsf: set_instance_assignment -name IO_STANDARD "<I/O_Standard>" -to "<negative_differential_pin_name>" -entity <entity_name> This problem is scheduled to be fixed in a future release of the Quartus® Prime Pro Edition Software.Why has my VCCL_HPS and VCCIO_HPS power estimates increased in the Quartus® Prime Pro Edition Software v26.1?
Description Starting in the Quartus® Prime Pro Edition Software version 26.1, the Max Power methodology for the HPS CPU subsystem in Agilex® 3 and Agilex® 5 FPGA devices was updated to account for sustained CPU execution. As a result, the power model changed and there is an increase in power estimation for the following power rails when compared to the version 25.3.1 or earlier: VCCL_HPS_CORE0_CORE1, VCCL_HPS_CORE2, and VCCL_HPS_CORE3: up to 514 mW per rail, depending on HPS core utilization and operating frequency, when CPU Application = Max Power VCCIO_HPS: approximately 2 mW Resolution Perform either of the following options :- Migrate your existing design to the Quartus® Prime Pro Edition Software version 26.1 or later for more accurate power estimation of VCCL_HPS (CORE0_CORE1, CORE2, and CORE3) and VCCIO_HPS Manually import existing PTC, PTA, QPTC, or QPTA files generated in version 25.3.1 or earlier into the Quartus® Prime Pro Edition Software version 26.1 Power & Thermal Analyzer and check the updated power estimates.Why is the power estimation of HPS core power rails inaccurate?
Description Due to a problem in the Power & Thermal Analyzer and Quartus Power Analyzer version 25.3.1 and earlier, the power estimation of HPS core power rails (VCCL_HPS, VCCL_HPS_CORE0_CORE1, VCCL_HPS_CORE2 and VCCL_HPS_CORE3) for Agilex® 3, Agilex® 5 and Agilex® 7 FPGA devices might be inaccurate if the CPU frequency field in PTA is empty or contains the wrong frequency. Resolution To work around this problem, manually import existing PTC/PTA/QPTC/QPTA files into the Power & Thermal Analyzer and ensure the CPU frequency field is filled with the correct frequency value: For Agilex 7 FPGA devices, ensure the CPU frequency field contains the highest CPU frequency used in your design For Agilex 3 and Agilex 5 FPGA devices, ensure the CPU frequency field contains the DSU frequency of your design. The DSU frequency is the highest CPU frequency (A55/A76 core frequency) used in your design divided by 1.5 This problem is scheduled to be fixed in a future release of the Quartus® Prime Pro Edition software.Why does Vendor Authorized Boot (VAB) certificate authentication failed in SDM?
Description During the Second-Stage Bootloader (SSBL), you may encounter an intermittent timeout while transferring the initial 32‑word block of the VAB certificate command Error message displayed: #ret = 0x000007ff, resp = 0x00000000, resp_len = 1 #VAB certificate authentication failed in SDM #### ERROR ### Please RESET the board ### Resolution To avoid this problem, upgrade the socfpga_v2.12.1 (socfpga_mailbox.c) An ATF patch for socfpga_v2.12.1 is available to fix this problem : Download and install patch mbox.patch from the attachment below. This problem is scheduled to be resolved in a future ATF releasedWhy does the FCS‑client abort during provision‑data retrieval when the number of owner‑root‑hash slots is changed to 5?
Description After provisioning 5 owner root hash, FCS client aborts during get provision data command command for fcs-client on get provision data (read efuse) : ./fcs_client –G <name>.bin -p --loglevel=4 Error message displayed when perform command fcs-client on get provision data on 5 owner root hash: root@agilex:~# fcs_client -G a.bin -p --loglevel=4 [dbg:]Retrieving provision data [dbg:]sysfs attribute /sys/kernel/fcs_sysfs/prov_data munmap_chunk(): invalid pointer Aborted perform owner root hash cancellation for root2,root3, and root4, get provision data command from FCS-client still remain “0”. command for fcs-client cancel owner root : ./fcs_client –c <name>.ccert –c <volatile = 1 / non-volatile =0> Error message displayed when perform command fcs-client on get provision data on 5 owner root after perform owner root hash cancellation for root2,root3 and root4: root@agilex :~# fcs_client -C signed_root4_cancel.ccert -c 1 root@agilex :~# fcs_client -C signed_root3_cancel.ccert -c 1 root@agilex :~# fcs_client -C signed_root2_cancel.ccert -c 1 root@agilex :~# fcs_client -G a.bin -p W0:Provision Status Code: 0x0 W1:Key Cancellation Status: 0x7F W2:Co-Sign Status: 0 W2:RootHash0 Cancel Status: 0 W2:RootHash1 Cancel Status: 0 W2:RootHash2 Cancel Status: 4 W2:RootHash3 Cancel Status: 0 W2:RootHash4 Cancel Status: 0 W2:Number of Hashes: 5 W2:Type of Hash: secp384r1 Resolution To avoid this problem, upgrade the libfcs with install the following patch: fix_read_provision_5_root_hash_v2.patch This problem is scheduled to be resolved in a future release of the libfcs.
