Recent Content
Why does generating an HDMI IP Design Example fail when selecting "No Daughter Card" in the Quartus® Prime Pro?
Description Due to a problem in the Quartus® Prime Pro Edition software version 26.1.1, generating an F-Tile HDMI FPGA IP design example encounters an error under the following configurations: Daughter Card parameter set to "No Daughter Card" with No Development Kit selected. Daughter Card parameter set to "No Daughter Card" with a Development Kit selected. Symptoms & Affected Components: Failure: Design Example generation fails or produces an error in Platform Designer Affected IP: F-Tile HDMI FPGA IP (ip.Video Connectivity.HDMI) Target Device / Architecture: Agilex® 7 / F-Tile devices Cause: The F-Tile HDMI IP design example generation script relies on a selected daughter card definition to automatically generate required board topology, clocking, and transceiver constraints. Selecting "No Daughter Card" causes error in the generation script in the Quartus Prime Pro Edition software version 26.1.1. Resolution To work around this problem, follow the steps below. Open the F-Tile HDMI FPGA IP parameter editor. Under the Design Example tab, select a supported HDMI Daughter Card option instead of "No Daughter Card". Generate the design example. If targeting a custom board, manually update the generated top-level pin locations and clock/transceiver settings in your project to match your custom board requirements. Patches are available to fix this problem for the Quartus Prime Pro Edition Software version 26.1.1 versions. Download and install patch below. Quartus Prime Pro Edition Software v26.1.1 Patch 1.25 This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.Why does the Linux* EDAC driver report "Previous Boot UE detected[0x40000]" on Agilex® 7 FPGA F and I-Series SoC FPGA devices?
Description The Linux* EDAC driver (drivers/edac/altera_edac.c) in the SoCFPGA Linux 6.12.11-lts (and earlier versions) may print a false Uncorrectable Error (UE) message during driver probe on Agilex® 7 F/I series SoC FPGA platform, as shown below. EDAC Altera: Previous Boot UE detected[0x40000] @ 0x0 The EDAC driver maps BOOT_SCRATCH_COLD8 (offset address0x220in System Manager, absolute address 0xFFD12220) to S10_SYSMGR_UE_VAL_OFST and treats any non-zero value as evidence of a previous boot UE event. At probe time, the driver checks: if (dberror) { ... } instead of properly masking with: if (dberror & AGX7F_I_DBE_IRQ_MASK) { ... } The valid UE sticky mask AGX7F_I_DBE_IRQ_MASK(0x30002) covers bits 1/16/17 only. When the value of BOOT_SCRATCH_COLD8 is 0x40000 in which bit 18 represents the SDM ACF DDR data rate per the Agilex 7 F/I SoC FPGA register definition, but it’s reported as a DDR UE/DBE by Linux EDAC driver by mistake. The driver does not account for the differences among the various Agilex 7 device series or for future device families. BOOT_SCRATCH_COLD8 bit definitions: Bit field Agilex 7 F/I-Series Agilex 7 M-Series Values / description Usage or source [31] Available as scratch memory DBE Triggered Flag M-Series:0: DDR DBE not triggered; 1: DDR DBE triggered U-Boot ddr_ecc_dbe_status(): evaluates DDR ECC DBE status [30] Available as scratch memory DDR Init in progress M-Series:0: DDR initialization not performed or completed successfully; 1: DDR initialization in progress U-Boot is_ddr_init_hang() checks the bit; ddr_init_inprogress() sets or clears it [29] Available as scratch memory OCRAM_DBE Error Flag M-Series:0: error did not occur; 1: error occurred U-Boot hps_ocram_dbe_status() returns OCRAM DBE status; ddr_init_inprogress() sets or clears it [28:27] Available as scratch memory Number of IO96B instances assigned to HPS M-Series:Written during DDR handoff data population U-Boot update_io96b_assigned_to_hps() [19] Flag indicating that a CPU power domain is about to be turned on; value 1 Flag indicating that a CPU power domain is about to be turned on; value 1 F/I/M-Series:A value of 1 indicates that the CPU power domain is about to be turned on ATF socfpga_pwr_domain_on() [18] ACF DDR data rate set by SDM Available as scratch memory F/I-Series: 0 = half-rate; 1 = quarter-rate U-Boot sdram_mmr_init_full() uses the value to configure DDRIOCTRL [17] ECC_DBE_DDR1 Error Flag ECC_DBE_DDR1 Error Flag F/I/M-Series:0: error did not occur; 1: error occurred ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler [16] ECC_DBE_DDR0 Error Flag ECC_DBE_DDR0 Error Flag F/I/M-Series:0: error did not occur; 1: error occurred ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler [1] ECC_DBE_OCRAM Error Flag ECC_DBE_OCRAM Error Flag F/I/M-Series:0: error did not occur; 1: error occurred ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler Impact: No actual DDR UE event is indicated by 0x40000. The false-positive log does not trigger kernel panic, reboot, or EDAC fault handling. However, the driver executes a full register write of zero to both BOOT_SCRATCH_COLD8 and BOOT_SCRATCH_COLD9 after printing the message, which may clear other valid scratch data (ATF, SDM, DDR progress bits) used by boot software on subsequent resets. Real DDR ECC uncorrectable errors continue to be reported correctly through the runtime ECC interrupt path (ECC_INTSTATUS_DERR @ sysmgr +0xA0). Resolution A patch has been applied to remove the incorrect previous DBE check using the BOOT_SCRATCH_COLD8 register during EDAC driver probe. ES-14508: EDAC/altera: Remove previous DBE check using boot scratch c… · altera-fpga/linux-socfpga@d06daa2 Related Articles A.7. BOOT_SCRATCH_COLD8 - 2025-12-16 linux-socfpga/drivers/edac/altera_edac.c at socfpga-6.12.11-lts · altera-fpga/linux-socfpgaWhy 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.Why 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.Error: 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.Can 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.Why Does a 528-bit PCS66 Phase Shift Occur with 400GZR/ZR+ Coherent Optical Modules on F-Tile Ethernet Hard IP?
Description In the Quartus® Prime Pro Edition software version 26.3 and earlier, raw receive PCS66 parallel data might appear phase-shifted by 528 bits when a 400G-8 F-Tile Ethernet Hard IP design without the Media Access Control (MAC) block is connected to a 400GZR or ZR+ coherent optical module. The shift equals eight 66-bit Physical Coding Sublayer (PCS) blocks, or half of the 1056-bit parallel word. The 66-bit symbols can remain intact, and rx_block_lock andrx_am_lock can remain asserted. This behavior can occur when the receive path selects the alternate 1:2 demultiplexer phase. The PCS does not provide parallel-data phase alignment relative to the original transmit AM and data relationship. The behavior was observed in the raw Media Independent Interface (MII) PCS66 path. MAC and MAC Segment modes successfully transferred packets. Electrical loopback, digital-to-analog converter loopback, internal serial loopback, and 400GE-8 short-reach optical paths did not show the same behavior. Resolution No Quartus Prime Pro Edition software fix is identified for this behavior at this time. To work around this problem, use a packet-oriented higher layer where possible. For designs that consume raw PCS66 data, follow these steps: Capture rx_pcs66_d and any available AM location or indication, rx_block_lock , and rx_am_lockas signals. Transmit a deterministic PCS66 block sequence that includes a unique known block pattern around the transmit AM location. Compare the received block sequence with the expected sequence to determine whether the received data is at offset 0 or offset 8 PCS66 blocks, which is a 528-bit offset. Implement protocol-specific realignment in the higher-level logic based on the detected offset. Do not use rx_am_lockas the sole phase detector. It indicates AM lock, but it does not identify which 1:2 demultiplexer phase is selected. A generalized phase-correction method or dedicated status bit/register has not been identified. The required realignment depends on the protocol consuming the raw PCS66 stream. Additional Information The current explanation is based on available data. It is generalized to all ZR/ZR+ module (subject to data availability). Customer-specific protocol details are required to define a complete phase-correction implementation or to suggest workarounds.Why 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.Why do I see Error (20354) and Error (20353) when signing CCERTs in Quartus® Prime Pro Edition version 26.3 with root keys generated in earlier versions?
Description You may encounter a signing failure in Quartus® Prime Pro Edition Software version 26.3 when an Agilex® 7 FPGA device root key generated by quartus_sign in an earlier release, such as Quartus® Prime Pro Edition Software version 21.2, is used to create and sign compact certificates (CCERTs). The operation fails with the following errors: Error (20354): Fail to execute file <path>26.3/111/linux64/devices/programmer/python/agilex_sign.py Error (20353): Module: bitstream.py, Function: verify_block0, Line: 798 Error (20353): Root key select is undetermined Error: Quartus Prime Signing_Tool was unsuccessful. 3 errors, 1 warning For example: In Quartus® Prime Pro Edition Software version 21.2, the following files were generated: root0_212.qky root0_public_212.pem root0_private_212.pem root0_aes_212.qek After switching to Quartus® Prime Pro Edition Software version 26.3 to generate the AES CCERT, the following commands were executed (using the AES CCERT test case as an example): quartus_pfg --ccert -o ccert_type=EFUSE_WRAPPED_AES_KEY -o qek_file=root0_aes_212.qek unsigned_aesccert0-263.ccert quartus_sign --family=agilex --operation=sign --pem=root0_private_212.pem --qky=root0_212.qky unsigned_aesccert0-263.ccert signed_aesccert0-263.ccert Impacted Agilex 7 OPN AGF 012 AGF 014 AGF 022 AGF 027 AGI 022 AGI 027 Resolution Recommendation: To sign a CCERT, use one of the following options: Use the same Quartus sofware version that was used to generate the existing root key. Use Quartus Prime Pro Edition Software version 26.1.1 or earlier. Use Quartus Prime Pro Edition Software version 26.3 or later to generate a new root key. Note: This behavior applies starting with Quartus Prime Pro Edition Software version 26.3 and is not expected to change in future releases. Related Articles Agilex 7 Part number DecoderWhy 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.
Featured Content
Tags
- troubleshooting10,426 Topics
- fpga dev tools quartus® prime software pro4,379 Topics
- FPGA Dev Tools Quartus II Software3,131 Topics
- agilex® 7 fpgas and socs1,559 Topics
- stratix® 10 fpgas and socs1,558 Topics
- arria® 10 fpgas and socs1,387 Topics
- stratix® v fpgas1,316 Topics
- arria® v fpgas and socs1,230 Topics
- cyclone® v fpgas and socs1,059 Topics
- stratix® iv fpgas646 Topics