agilex® 5 fpgas and socs
522 TopicsWhy 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 v22.1 through v25.3.1 Standalone Quartus Prime Pro Programmer v22.1 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 22.1 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 22.1 0.51 22.2 0.63 22.3 0.56 22.4 0.51 23.1 0.63 23.2 0.63 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.0214KViews5likes0CommentsWhy do I see Error (18950), Error (18948) and Error (209012) when program SOF file for Agilex® 5 FPGA device in Quartus® Prime Pro Edition version 26.3 ?
Description You may encounter programming failure in Quartus® Prime Pro Edition Software version 26.3 with an Agilex® 5 FPGA device SOF File. The operation fails with the following errors: Error(18950): Device has stopped receiving configuration data Error(18948): Error message received from device: Failed to load firmware due to authentication failure. Ensure the firmware is signed with the correct signing key. Error(209012): Operation failed Impacted Agilex 5 OPN A5Dx160xxxxxxxxRx Resolution A patch is available to fix this problem for the Quartus® Prime Pro Edition version 26.3. Download and Install patch below. quartus-26.3-0.05fw-windows.exe quartus-26.3-0.05fw-linux.run quartus-26.3-0.05fw-readme.txt Related Article Agilex® 5 FPGA Part Number Decoder100Views0likes0CommentsWhy does the Quartus® Prime Pro Edition Software report Error (170084) for Agilex® 5 Configuration via Protocol CvP designs?
Description Due to a problem in the Quartus® Prime Pro Edition Software version 26.1.1, Error (170084) might occur during the Fitter stage when compiling designs that enable Configuration via Protocol (CvP) with the GTS AXI Streaming IP for PCI Express* for Agilex® 5 FPGA devices because of a control shadow register connectivity problem in the IP. This problem happens when the design enables CvP in the GTS AXI Streaming IP for PCI Express* and in the Device and Pin Options CvP settings is enabled. Designs that do not enable CvP are not affected. You might see an error message similar to the following: Error (170084): Can't route signal "<hierarchy>|...|O_HIO_USER_RX_CLK1_CLK" to atom "<hierarchy>|...|u_ctrl_shadow_loader|avmm_clk_o" Resolution A patch is available to fix this problem for the Quartus® Prime Pro Edition Software version 26.1.1. Download and install patch 1.21 below. This problem is scheduled to be resolved in a future release of the Quartus® Prime Pro Edition Software.24Views0likes0CommentsWhy does the Nios® V/g processor become unstable when both CLIC and shadow registers are enabled?
Description Due to a problem in the Quartus® Pro/Standard Edition software version 26.1/25.1, Nios® V/g interrupt handling might be unstable when both CLIC mode and Shadow Register are enabled. This is because the Shadow Register CSR (msrfstatus) is not saved/restored during interrupt context saving under CLIC mode. Resolution To work around this problem in the Quartus® Prime Pro/Standard Edition Software version 26.1/25.1, follow these steps: Download the machine_trap.zip Extract to get the new machine_trap.S Search for the old machine_trap.S in your BSP project Replace with the new machine_trap.S file Rebuild your software Additional Information This problem is currently scheduled to be resolved in a future release of the Quartus® Prime Pro and Standard Edition Software.30Views0likes0CommentsError: CPU "intel_niosv_g_0" has no memories connected to its Avalon host(s)
Description Due to a problem in the Quartus® Pro Edition software version 26.1.1, you might see an error when generating a Nios® V BSP, when the AXI Address Span Extender IP is inserted between the Nios V processor and the memory device connected to the instruction and data buses of the Nios V. This is because the AXI Address Span Extender IP does not recognize the connected device as a memory device for the Nios V processor. Resolution To work around this problem in the Quartus® Prime Pro Edition Software version 26.1.1, follow these steps: 1. Open <QUARTUS_INSTALL_DIR>/ip/altera/merlin/axi_address_span_extender/axi_address_span_extender_hw.tcl 2. Go to around line 448, then delete the lines marked in red and add the lines marked in green as shown below. # this assignment allows this component to appear as a memory target in the Nios II linker script configuration GUI # it makes the memory map of our slave look like a valid linker target memory region # <<to be revisited in 13.0>> - #set_interface_assignment windowed_slave embeddedsw.configuration.isMemoryDevice 1 + set_interface_assignment $slave embeddedsw.configuration.isMemoryDevice 1 # # this assignment allows the macros of components attached to our master to appear in the Nios II system.h header # <<to be revisited in 13.0>> - #set_interface_assignment windowed_slave embeddedsw.configuration.affectsTransactionsOnMasters "expanded_master" + set_interface_assignment $slave embeddedsw.configuration.affectsTransactionsOnMasters $master Please do not include the leading "+" and "-" characters. 3. Regenerate your design in Platform Designer. Additional Information This problem is currently scheduled to be resolved in a future release of the Quartus® Prime Pro Edition Software. However, the updated statements are commented out by default. To apply the changes, remove the comment markers.14Views0likes0CommentsCan the GTS SDI II design example run on the Agilex® 5 FPGA E-Series Modular Development Kit, Revision C?
Description The GTS SDI II IP Design Example User Guide: Agilex® 3 and Agilex® 5 FPGAs and SoCs describes how to compile and test the SDI II design example on hardware. The instructions, including the Clock Controller GUI setup, are based on Revision B of the Agilex® 5 FPGA E-Series Modular Development Kit (MDK). When using a Revision C board, some procedures may differ. Resolution To work around this problem, follow the steps written below. The GTS SDI II IP Design Example User Guide is scheduled to be fixed in a future release of the Quartus® Prime Pro Edition software. Steps Migration Design to Modular Devkit REVC. For GTS SDI II Modular Devkit (Parallel Loopback (with/without) external VCXO and Serial loopback Design) In sdi_ii_agi_demo.qsf Comment out all settings related to core_refclk_1485 Change xcvr_refclk_1485 pin location from PIN_BC111 to PIN_AY120 In sdi_ii_agi_demo.sv Comment out // input core_refclk_1485, // 100 MHz default from Si5332 U412. Program OUT6-OUT8 to 148.5 MHz in Clock GUI. Change all connection core_refclk_1485 to clk_100mhz Open sdi_rx IP GUI Change Rx core clock (rx_coreclk) frequency to 100.0 MHz Click “Generate HDL” and save for regen IP with 100Mhz In sdi_ii_agi_demo.sdc Please remove Part 1 Change Part 2 (core_refclk_1485) to clk_100mhz For Parallel Loopback without external VCXO Design In sdi_ii_agi_demo.qsf Change txpll_refclk from PIN_AV120 to PIN_AT120 For AXIS-VPP Full (Parallel Loopback (with/without) external VCXO) Design Open axi4s_iopll IP GUI Change Reference Clock Frequency to 100.0 MHz Click “Generate HDL” for regen the IP. For Serial Loopback Design In sdi_ii_agi_demo.qsf Change txpll_refclk from PIN_AV120 to PIN_AT120 For Serial Loopback (with Enable Dual Simplex) Design In sdi_ii_agi_demo.qsf Change txpll_refclk from PIN_AV120 to PIN_AT120 Change syspll_refclk from PIN_AY120 to PIN_BC111 Open xcvr_ref_sysclk IP GUI Change Refclk frequency from 312.5MHz to 156.25MHz Click “Generate HDL” for regen IP In sdi_ii_agi_demo.sdc Change the create_clock value of syspll_refclk from “135 MHz” to “156.25 MHz” Remove core_refclk_1484 create_clock settings Clock Controller Settings for Agilex 5 FPGA E-Series 065B Modular Development Kit Set SI569 (U33) to 148.5MHz Set SI5391 Go to si5391 folder, click on *.slabtimeproj to open ClockBuilder Pro GUI for settings the clock. You may follow the Word document (SI5391_Configuratio_File_Generation_steps) to set the output clock and export a *.txt (register file) to import the clock settings. On the SI5391 tab, set OUT1 to 141.00MHz and set the N-divider as Auto) Import the register.txt file into SI5391 Tab Click “Read” after Import completely, should be able to see SI5391 Tab OUT1 already been set to 141.0MHz. For Select Design = Parallel loopback without external VCXO, Open Clock Controller GUI, click the SI5391 tab, set OUT1 to 141.0 MHz. For Dynamic Tx Clock Switching = Tx PLL reference clock switching, Open Clock Controller GUI, click the SI5391 tab, set OUT1 to 148.3516MHz.39Views0likes0CommentsWhy don’t the new Nios® V/c processor features appear after upgrading the Nios® V/c Processor IP to Quartus® Prime Pro version 26.3?
Description In Quartus® Prime Pro Edition 26.3, the Nios® V/c processor IP is renamed from intel_niosv_c to niosv_c across all FPGA device families. Performing IP Upgrade from earlier Quartus® Prime project will retain the legacy intel_niosv_c in your project. For your information, This legacy intel_niosv_c IP remains at last updated back in Quartus® Prime Pro Edition 26.1.1. While new Nios® V/c processor IP feature are introduced into niosv_c IP starting from Quartus® Prime Pro Edition 26.3. In another words, auto-upgrade of intel_niosv_c to niosv_c in not supported by IP Upgrade. Thus, you may find those new Nios® V/c processor features (in niosv_c) is missing in intel_niosv_c. Resolution If new Nios® V/c processor features (such as Debug option) is required, re-instantiate the Nios® V/c processor in Quartus® Prime Pro version 26.3.31Views0likes0CommentsWhy does the GTS AXI Streaming IP for PCI Express* on Agilex® 5 FPGA D-Series remain in reset or fail to initialize after system boot?
Description Due to a problem in the Quartus® Prime Pro Edition software version 26.3, the GTS AXI Streaming IP for PCI Express* on Agilex® 5 FPGA D-Series devices may not initialize successfully. Devices programmed with a .sof file or an image generated by version 26.3 may exhibit the following symptoms: The PCIe IP remains in reset. The PCIe endpoint fails to enumerate. These symptoms may occur even though device configuration and overall system boot-up have completed successfully. Impacted Agilex 5 OPN A5Dx130xxxxxxxx A5Dx160xxxxxxxx Resolution This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.58Views0likes0CommentsWhy does the bas_axi_mm_rlast signal of the GTS AXI MCDMA IP not asserted on the final beat of a read burst?
Description Due to a problem in the Quartus® Prime Pro Edition software version 26.3 and earlier, the GTS AXI Multichannel DMA IP might fail to assert bas_axi_mm_rlast on the final beat of a multi-beat AXI read burst or may assert it on an earlier beat. This problem occurs in the Bursting Slave (BAS) read-response path for multi-beat PCIe completion, potentially causing an AXI protocol violation or an incorrectly terminated read burst. Resolution This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.45Views0likes0CommentsWhy do I see a generation failure with simulation enabled, or a compilation failure, in the Integrated PHY Dual-Simplex Serial Loopback design example with TX Clock Switching?
Description Due to a problem in the Quartus® Prime Pro Edition software version 26.3, you may see the following problems when generating or compiling the Integrated PHY Dual-Simplex Serial Loopback design example with TX Clock Switching enable: Generation failure when simulation is enabled When you enable simulation in the design example, generation fails. There is currently no workaround for this problem. This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software. Compilation failure when simulation is disabled The gxb_tx_refclk_cmd_bus_in[*] ports are missing from the shared_clocks list of the TX QHIP_IP_PROPERTY assignment in the .qsf file. Because of this, compilation fails with the following error: Error (26050): IP instance port name sdi_tx_inst|gxb_tx_refclk_cmd_bus_in[n] for DR_SHARED_CLOCK assignment in dual simplex/reconfiguration group dr_top is not allowed. To fix this compilation failure, follow the workaround in the Resolution section. Resolution To work around compilation problem, user needs to add the gxb_tx_refclk_cmd_bus_in[0] to gxb_tx_refclk_cmd_bus_in[9] ports to the shared_clocks list of the TX QHIP_IP_PROPERTY assignment in qsf file. Example: "shared_clocks" : ["system_pll_clk", "system_pll_lock", "tx_pll_refclk", "gxb_tx_refclk_cmd_bus_in[9]", "gxb_tx_refclk_cmd_bus_in[8]", "gxb_tx_refclk_cmd_bus_in[7]", "gxb_tx_refclk_cmd_bus_in[6]", "gxb_tx_refclk_cmd_bus_in[5]", "gxb_tx_refclk_cmd_bus_in[4]", "gxb_tx_refclk_cmd_bus_in[3]", "gxb_tx_refclk_cmd_bus_in[2]", "gxb_tx_refclk_cmd_bus_in[1]", "gxb_tx_refclk_cmd_bus_in[0]"]}} Save the file and recompile the design.33Views0likes0Comments