Why are Toolkit instances (ETK, TTK) not detected for Agilex® 7 F-Tile Ethernet Hard IP in System-console after device configuration?
Description In designs using multiple instances of the Agilex® 7 F-Tile Ethernet Hard IP with Toolkit support enabled (ETK and TTK), the Toolkit instances may sometimes not be detected in the System Console GUI after programming the FPGA with the design .sof file. This behavior is caused by a problem in the F-Tile Ethernet Hard IP configuration. Resolution A patch is available to fix this problem for the Quartus Prime Pro Edition software version 25.3.1 and 26.1. Download and apply attached patches (1.32, 0.35) for intended Quartus version, which restores Toolkit visibility in the System Console GUI for the F-Tile Ethernet Hard IP. This problem is fixed beginning with the Quartus Prime Pro Edition software version 26.1.1.Why 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.Why 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.Why does the Multi Channel DMA for PCI Express* FPGA IP fail to upgrade in Quartus® Prime Pro Edition Software version 25.3?
Description Due to a name change in the PIO Example Design from “PIO using MQDMA Bypass mode” to “PIO using MCDMA Bypass mode”, designs that include the Multi Channel DMA for PCI Express* FPGA IP created in Quartus® Prime Pro Edition Software versions earlier than 25.3 may fail to generate HDL when performing an automatic IP upgrade. When this problem occurs, the following system error messages appear in the IP Parameter Editor Pro window: Error: intel_pcie_ftile_mcdma_0.intel_pcie_ftile_mcdma_0: "Based on parameterization, the generated example design for PCIe0 will be" (select_design_example_hwtcl) "PIO using MQDMA Bypass mode" is out of range: "Device-side Packet loopback", "PIO using MCDMA Bypass mode", "Packet Generate/Check", "AVMM DMA", "Traffic Generator/Checker", "External Descriptor Controller", "BAM SRIOV" Resolution Workaround: To work around this problem, follow the steps below: Manually update the .ip file in your project by replacing all instances of “PIO using MQDMA Bypass mode” with “PIO using MCDMA Bypass mode.” Save the updated .ip file. Reopen the modified .ip file in the Quartus® IP Parameter Editor. Depending on your use case, click “Generate Example Design” or “Generate HDL.”Why am I seeing some packet drop/loss when using the F-tile Ethernet Hard IP with Auto-Negotiation and Link Training (AN/LT) enabled 100G designs?
Description Due to a problem in the Quartus® Prime Pro Edition software version 25.1.1, 25.3 and 25.3.1, you may see traffic failures with packet drop/loss when using the F-tile Ethernet Hard IP with Auto-Negotiation and Link Training (AN/LT) enabled 100G designs. Resolution Add the solution or the workaround to fix the problem or bug. Additional Information Currently there is no workaround for this problem. This problem is scheduled to be fixed in a future release of the Quartus® Prime Pro Edition software.Why am I seeing linkup problem for the GTS Ethernet Hard IP with Auto-Negotiation and Link Training (AN/LT) multirate IP for HVIO PLL enabled 25G rate designs?
Description Due to a problem in the Quartus® Prime Pro Edition software version 25.3.1, you may see linkup problem for the GTS Ethernet Hard IP with Auto-Negotiation and Link Training (AN/LT) multirate designs. This problem may happen when using 25G multirate designs with HVIO PLL option enabled. Resolution Currently there is no workaround for this problem. This problem is scheduled to be fixed in a future release of the Quartus® Prime Pro Edition software.Why Can't I Program Using Active Serial Programming with my USB Blaster III?
Description Due to a firmware issue the USB Blaster III Development cable may not have the correct product ID and may inadvertently disabled the active serial programming feature. Is my Development Cable affected by this? If your USB Blaster III Development cable has a serial number ranging from UB3000000 - UB3006090, then you will need to update the PID. Resolution To resolve this issue the Product ID of the cable should be updated to (6023). Perform the following steps on Windows to update the ID. Download and Install the FT_PROG.exe the EEPROM Programming Utility from FTDI https://ftdichip.com/utilities/ Plug-in your USB Blaster III development cable into your computer. Uninstall the USB Blaster III device driver from the device manager. Open the Windows Device Manager. Find the group called JTAG cables, under this group there should be a USB Blaster III device. Right Click on the USB Blaster III device and Click Uninstall. Tick "Attempt to delete the driver for this device" or "Delete the driver software for this device" during uninstallation. This prevents the UB3 driver from being automatically reinstalled. Install the FTDI Device driver. Open the Windows Device Manager. Find the group called Other Devices. In the group Other Devices there may be several USB Blaster III devices. To Identify the correct USB Blaster III device Right click on each USB Blaster III device and click Properties. Find USB Blaster III device that contains values that end with MI_00 Once Identified, Right click on correct USB Blaster III device and click Update driver To Update driver click Browse my computer for drivers Search and select the USB Blaster III driver directory under your Quartus installation. <Quartus Path>\qdrivers\quartus\drivers\usb-blaster-iii Click Let me pick from a list of available drivers on my computer. If, Select your device’s type from the list below, choose Universal Serial Bus controllers. When selecting a driver click the FTDI manufacturer then select USB Serial Converter A Version: 2.12.36.4 and click the Next button. Program your USB Blaster III Development Cable with FT_PROG.exe to update your product ID. Open the FT_PROG.exe from FTDI installed in step 1. From the DEVICES menu click Scan and Parse to bring up your USB Blaster III Device Under the Device Tree select the section called USB Device Descriptor This should contain a property called Product ID and should have a value of 6023, change this to 6023 if it is not set to this value. Once changed, under the DEVICES menu click Program to flash the EEPROM Uninstall the FTDI driver installed in step 4. Open the Windows Device Manager. Find the group Universal Serial Sub controllers In the Universal Serial Bus controllers right click on the USB Serial Converter A and Click Uninstall. Do not tick "Attempt to delete the driver for this device" or "Delete the driver software for this device". Re-Install the USB Blaster III device driver. Open the Windows Device Manager. Find the group called Other Devices. In the group Other Devices there may be several USB Serial Port devices or USB Blaster III devices. To Identify the correct USB Serial Port device Right click on each USB Serial Port device and click Properties. Find USB Serial Port device that contains values that end with MI_00 Once Identified, Right click on correct USB Blaster III device and click Update driver To Update driver click Browse my computer for drivers Search and select the USB Blaster III driver directory under your Quartus installation. <Quartus Path>\qdrivers\quartus\drivers\usb-blaster-iii Click the Next button. Windows should show USB Blaster III driver installed. Verify USB Blaster III device has the correct Product ID. Open the Windows Device Manager. Find the group called JTAG cables, under this group there should be a USB Blaster III device. Right click on each USB Blaster III device and click Properties. Values should contain PID_6023 in the string, if not unplug and re-plugin the device. Open Quartus Programmer and Validate that the Active Serial programing is now available.Why does Linux fail to configure the FPGA with error "arm-smmu-v3 16000000.iommu: event 0x10 received" on Agilex® 5 FPGA production silicon?
Description This error might be seen in the Quartus ® Prime Pro Edition Software version 25.1 when using HPS-first boot and configuring the FPGA from Linux, on an Agilex ® 5 FPGA device with production silicon (revision B0 or later). This error prevents the FPGA configuration from completing successfully. The failure is because the embedded software provided with version 25.1 is not compatible with Agilex 5 FPGA production silicon. An example of log output showing this issue as as follows: [ 6.060661] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.067061] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.072635] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.078226] arm-smmu-v3 16000000.iommu: 0x000000009ff80000 [ 6.083790] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.089350] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.095004] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.100565] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.106130] arm-smmu-v3 16000000.iommu: 0x000000009ff80080 [ 6.111690] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.117258] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.122908] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.128471] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.134030] arm-smmu-v3 16000000.iommu: 0x000000009ff80100 [ 6.139594] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.145154] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.150803] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.156362] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.161924] arm-smmu-v3 16000000.iommu: 0x000000009ff80180 [ 6.167490] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.173049] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.178700] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.184259] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.189825] arm-smmu-v3 16000000.iommu: 0x000000009ff80200 [ 6.195390] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.200950] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.206595] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.212154] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.217712] arm-smmu-v3 16000000.iommu: 0x000000009ff80280 [ 6.223270] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.228828] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.234473] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.240031] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.245589] arm-smmu-v3 16000000.iommu: 0x000000009ff80300 [ 6.251154] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.256713] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.262359] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.267917] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.273475] arm-smmu-v3 16000000.iommu: 0x000000009ff80380 [ 6.279033] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.284591] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.290236] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.295794] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.301353] arm-smmu-v3 16000000.iommu: 0x000000009ff80400 [ 6.306917] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 6.312476] arm-smmu-v3 16000000.iommu: event 0x10 received: [ 6.318121] arm-smmu-v3 16000000.iommu: 0x0000000a00000010 [ 6.323680] arm-smmu-v3 16000000.iommu: 0x0000020a00000000 [ 6.329238] arm-smmu-v3 16000000.iommu: 0x000000009ff80480 [ 6.334797] arm-smmu-v3 16000000.iommu: 0x0000000000000000 [ 11.494089] Stratix10 SoC FPGA manager firmware:svc:fpga-mgr: timeout waiting for svc layer buffers Resolution To work around this problem in the Quartus ® Prime Pro Edition Software version 25.1 and associated embedded software, follow these steps: 1. In the Arm Trusted Firmware source code, edit or patch file plat/intel/soc/agilex5/include/agilex5_system_manager.h 2. Change the line of the source file that reads: #define A5F4_JTAG_ID 0x4000F000 to the following: #define A5F4_JTAG_ID 0x4000C000 3. Rebuild and deploy the resulting software. This problem is fixed beginning with the Quartus ® Prime Pro Edition Software version 25.3.1 and associated embedded software.Why 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.Why o_rx_pcs_fully_aligned does not assert for 40GE-4 Advanced mode F-Tile Ethernet Hard IP design when Custom Ethernet line rate > 63Gbps?
Description Due to a problem in the Quartus® Prime Pro Edition Software version 25.3 and earlier, you might observe o_rx_pcs_fully_aligned does not assert for the F-Tile Ethernet Hard IP design with below configurations: Advanced mode: Enabled Ethernet mode: 40GE-4 Custom Ethernet line rate: > 63 Gbps Resolution There is no workaround. There is no fix planned in the future. When advanced mode enabled for 40GE-4 design, supported custom Ethernet line rate is: 41.25~63 Gbps.