errata
197 TopicsWhy 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 is there D2H payload mismatch on GTS AXI MCDMA IP?
Description Due to a problem in the Quartus® Prime Pro Edition software version 26.3 and earlier, the GTS AXI Multichannel DMA IP for PCI Express* might transmit D2H data associated with the wrong queue on AXI-Stream TX interface. As a result, the Host may receive data at an incorrect destination address, potentially causing transaction mismatches. Resolution This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.37Views0likes0CommentsError(14394): Verilog HDL error at <module_name>.sv(<line>): vector/single is not declared under the prefix ""
Description Due to a problem in the Quartus® Prime Pro Edition Software version 26.1.1 or earlier, you might see this error when synthesizing the SystemVerilog HDL code where a typedef struct declared inside an interface is referenced within a nested submodule. The SystemVerilog HDL code as below: interface my_interface #( parameter int WIDTH = 1 )(); typedef struct packed { logic single; logic [WIDTH-1:0] vector; } MY_STRUCT; logic req; logic ack; MY_STRUCT data; modport src ( output req, input ack, output data ); modport dst ( input req, output ack, input data ); endinterface module testmodule ( input wire clock, my_interface.dst data_in, my_interface.src data_out ); typedef data_in.MY_STRUCT ITYPE; typedef data_out.MY_STRUCT OTYPE; … ITYPE demo_in; OTYPE demo_out; assign demo_in = data_in.data; assign data_out.data = demo_out; submodule my_sub ( .data_in ( demo_in ), .data_out ( demo_out ) ); module submodule ( input ITYPE data_in, output OTYPE data_out ); … endmodule endmodule Resolution To work around this problem in the Quartus® Prime Pro Edition Software version 26.1, download and install the patch 0.37 below. This problem is scheduled to be fixed in a future release of the Quartus® Prime Pro Edition Software.158Views0likes0CommentsWhy does the Quartus® Prime Pro fitter fail when compiling the Agilex® 5 GTS HDMI IP Clocked Video design example with the HDMI PHY?
Description Due to a problem in the Quartus® Prime Pro Edition Software version 26.1.1, the fitter may fail during placement when compiling the Agilex® 5 GTS HDMI IP design example configured with the Clocked Video interface with the HDMI PHY configuration. The failure occurs while routing a core global signal for the HDMI receive path and reports that no valid lab location can be found near chip coordinates (157, 74). The fitter then exits unsuccessfully. Resolution This problem will be fixed in a future release of the Quartus Prime Pro Edition Software.60Views0likes0CommentsWhy are setup timing violations reported on the F-Tile Support Logic and Direct PHY paths?
Description Due to a problem in the Quartus® Prime Pro Edition software version 25.1.1, you may observe setup timing violations on clocks associated with F-Tile support logic and Direct PHY paths. The failing path was between Soft Reset Controller (SRC) and Direct PHY (DPHY) logic due to synchronizer problem. Resolution This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.107Views0likes0CommentsWhy is SW2 missing on my Agilex® 5 FPGA E-Series 065B Modular Development Kit?
Description Due to an issue with the revision C2 Agilex® 5 FPGA E-Series 065B Modular Development Kit carrier board, power switch SW2 is not installed. As a result, the PCIe® 12 V or ATX 12 V power supply paths cannot be controlled. A Rev C2 Carrier board uses the PCIe® 12 V supply when the card is plugged into a server and uses the ATX power when 12 V is provided from the ATX connector. DO NOT Connect both ATX 12V and PCIe 12V powers simultaneously. You can identify a Rev C2 board by one of the following methods: Serial number range—A5EBMKPA100009 to A5EBMKPA100050 Absence of SW2 "RevC2" silkscreen marking near the PCIe edge connector Resolution Agilex® 5 FPGA E-Series 065B Modular Development Kit revision C3 carrier boards are corrected and have SW2 installed.56Views0likes0CommentsWhy does the Agilex® 5 FPGA device pin-out file list the "Direct to Factory Image" (~LOADFACTORY~) pin as an output instead of an input?
Description Due to a data error in the published Agilex® FPGA 5 device pin-out file, the optional "Direct to Factory Image" configuration signal (signal name ~LOADFACTORY~, ball BW102, 1.8-V, SDM bank) might be listed with pin direction "output" instead of "input" for designs targeting Agilex® 5 FPGAs and SoCs because the pin-out file entry for this signal has not yet been corrected to match the signal's actual, documented behavior as an input pin used to select between the factory and application images during a remote system update. Resolution To work around this problem, follow these steps: Do not use the device pin-out file as the authoritative reference for the "Direct to Factory Image" (~LOADFACTORY~) signal direction. Refer instead to the Pin Connection Guidelines: Agilex® 5 FPGAs and SoCs (doc ID: 813266), Section 1.2.14, Secure Device Manager (SDM) Optional Signal Pins, which correctly documents this pin as an input. Additional Information The device pin-out file is a board-routing reference only. It is not read or enforced by the Quartus® Prime software during design compilation or fitting, so this discrepancy causes no functional failure, no compilation error, and no design-rule violation. Customers should treat the Pin Connection Guidelines handbook (doc ID: 813266) as the authoritative source whenever it disagrees with the device pin-out file.67Views0likes0CommentsWhy does the Agilex® 7 FPGA HPS EMIF and fabric EMIF hang after core reconfiguration when both interfaces share the same IO bank in x72 configuration?
Description Due to a problem in the Quartus® Prime Pro Edition Software version 24.2, when Agilex® 7 FPGA F-Series and I-Series HPS EMIF and fabric EMIF share the same IO bank in x72 configuration and the design operates in HPS-first mode, the initial configuration can succeed, but subsequent core reconfigurations can cause the fabric EMIF calibration firmware to hang for designs targeting in Agilex® 7 FPGA F-Series and I-Series devices. The observed failure signature is that, after the FPGA is reconfigured without a full board power cycle, the fabric EMIF no longer responds correctly and the calibration flow does not assert cal_success or cal_fail. Resolution A patch is available to fix this problem for the Quartus® Prime Pro Edition Software version 24.2. Download and install patch 0.70fw below. quartus-24.2-0.70fw-linux.zip quartus-24.2-0.70fw-readme.zip quartus-24.2-0.70fw-windows.zip A patch is available to fix this problem for the Quartus® Prime Pro Edition Software version 25.1.1. Download and install patch 1.54fw below. quartus-25.1.1-1.54fw-linux.zip quartus-25.1.1-1.54fw-readme.zip quartus-25.1.1-1.54fw-windows.zip This problem is resolved in Quartus® Prime Pro Edition Software version 26.1.1.106Views0likes0CommentsWhy does the F-Tile Low Latency 100G Ethernet IP not work when Ready Latency is set to 3?
Description Due to a problem in the Quartus Prime Pro Edition software version 26.1, you may see the F-Tile Low Latency 100G Ethernet IP doesn’t work when the IP for Ready Latency is set to 3 and it may result in incorrect TX client interface behavior because the Ready Latency parameter is not fully propagated through the generated IP hierarchy. There is no workaround in the current IP implementation because the Ready Latency GUI parameter is not used in the generated IP. Resolution A 26.1 patch (0.32) is available for this problem and it is attached to this article. This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.69Views0likes0CommentsHow do I enable debug endpoint for transceiver toolkit (ADME) for the F-Tile 25G Ethernet Soft-IP to use the Transceiver Toolkit?
Description The F-Tile 25G Ethernet IP (alt_e25_f) does not expose the "Enable debug endpoint for transceiver toolkit" option in the IP Parameter Editor GUI. As a result, users cannot enable Transceiver Toolkit access through the standard IP configuration interface. Resolution To enable debug endpoint for transceiver toolkit for the F-Tile 25G Ethernet IP, use the following workaround: To enable the debug endpoint for the Transceiver Toolkit, use the following workaround: Open the .ip file for the F-Tile 25G Ethernet Soft IP. Locate the ENABLE_ADME_GUI parameter. Change its value from 0 to 1. Save the .ip file. Regenerate the IP. Note: This workaround modifies a hidden parameter that is not officially available in the GUI. The parameter implementation may change in future releases. After upgrading Quartus® Prime software, verify that the functionality continues to operate as expected.60Views0likes0Comments