Why does my Deinterlacer II license fail?
Description Due to a problem in the Quartus® Prime Standard edition software version 16.1, designs containing the Deinterlacer II IP only generate a time-limited programming file. Resolution To resolve this problem in the Quartus Prime Standard edition software version 16.1, download and install the patch from the links below: Download the Quartus Prime version 16.1 Patch 0.04 for Linux (.run) Download the Quartus Prime version 16.1 Patch 0.04 for Windows (.exe) Download the Quartus Prime version 16.1 Patch 0.04 Readme (.txt) This problem is scheduled to be fixed in a future release.Why does the Frame Buffer II (4K Ready) Intel® FPGA IP drop my ancillary (user) packets?
Description Due to a problem with the Frame Buffer II (4K Ready) Intel® FPGA IP when Module is Frame Writer only is selected, you cannot change the Maximum ancillary packets field. That field, under the Memory section of the parameter editor, will be greyed out and not editable. Frame buffer in frame writer mode, default Ancillary packets = 0 This field defaults to 0 (zero), which will cause all ancillary packets (also known as User packets) to be dropped. Resolution To work around this problem, de-select Module is Frame Writer only, change the Maximum ancillary packets per frame to your desired setting, then re-select Module is Frame Writer only. Frame buffer with frame writer mode off and Ancillary packets entered Frame buffer in frame writer mode, note Ancillary packets = 3 This problem is fixed in the Intel® Quartus® Prime Software version 18.0.Fatal Error: Segment Violation: faulting address=0xfffffff4d88b0e54, PC=0x7fb0428d2e23 : 0x7fb0428d2e23: fitter_fdrgn!FDRGN_PERIPHERY_CORE_PLACEMENT::publish_routing_to_crf(QGL::FOREST const&, CDB_RE_R
Description Due to a problem in the Intel® Quartus® Prime Pro Edition software version 20.2, you may see this error during the Fitter Plan stage. This fatal error may occur when "Periphery to Core Placement and Routing Optimization" setting is enabled. Resolution A patch is available to fix this problem for the Intel® Quartus® Prime Edition Pro software version 20.2. Download and install Patch 0.15 from the appropriate link below. Download patch Intel® Quartus® Prime Pro Edition 20.2 Patch 0.15 for Windows (.exe) Download patch Intel® Quartus® Prime Pro Edition 20.2 Patch 0.15 for Linux (.run) Download the Readme for Intel® Quartus® Prime Pro Edition 20.2 Patch 0.15 (.txt) This issue has been fixed in the Intel® Quartus® Prime Pro Edition software version 20.3.Error: Could not open afu_opencl_kernel.fit.rpt for reading
Description When you compile OpenCL code for Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA, you may see the Error: Could not open afu_opencl_kernel.fit.rpt for reading. What’s more, you may see the following warning: Warning (115003): Can't generate programming files for your current project because you do not have a valid license for the following IP core or cores. Warning (115005): Unlicensed IP: "PCIe SRIOV with 4-PFs and 2K-VFs(6AF7 00FB)" Warning (115005): Unlicensed IP: "Low Latency 10Gbps Ethernet MAC(6AF7 0119)" Warning (115005): Unlicensed IP: "Low Latency 40Gbps Ethernet MAC and PHY(6AF7 011B)" Resolution This is because Rush Creek DCP license expired 12/31/2019. A patch is available to fix this problem for the Intel® Quartus® Prime software version 17.1.1. Download and install the patch from the appropriate link below. Download patch Intel® Quartus® Prime 17.1.1 Patch 1.03dcp for Linux(.run) Download the Readme for Intel® Quartus® Prime 17.1.1 Patch 1.03dcp(.txt)Why does aocl diagnose fail on Ubuntu 16.04 (kernel 4.14 or newer)?
Description aocl diagnose may fail to find Arria® 10 device on Ubuntu 16.04 (kernel 4.14 or newer) even though aocl install step completes successfully (as mentioned in AN 807 for Arria® 10 GX FPGA Development Kit) beacuse of the altera_cvp module that is included in newer Ubuntu kernels. To check if altera_cvp module is causing aocl diagnose failure in your system, check the "Kernel driver in use" field for Altera Corporation Device listed in PCIe device information: $ lspci -v Look for Processing accelerators: Altera Corporation Device Processing accelerators: Altera Corporation Device 2494 (rev 01) (prog-if 01) Subsystem: Altera Corporation Device a151 Physical Slot: 4 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at f3140000 (64-bit, prefetchable) [size=512] Memory at f3100000 (64-bit, prefetchable) [size=256K] Capabilities: <access denied> Kernel driver in use: altera-cvp Kernel modules: altera_cvp, aclpci_a10_ref_drv Resolution To prevent the altera_cvp module from being loaded for your Arria® 10 device, copy the blacklist file attached below to /etc/modprobe.d directory and restart the computer. Administrative privileges are required to complete this fix. > Download blacklist-altera_cvp.conf here $ sudo cp blacklist-altera_cvp.conf /etc/modprobe.d/ After reboot, lspci -v should NOT show altera_cvp in the "Kernel driver in use" field for Altera Corporation Device. You should see the Arria® 10 device driver (as shown for Arria® 10 GX FPGA Development Kit in the example below) Processing accelerators: Altera Corporation Device 2494 (rev 01) (prog-if 01) Subsystem: Altera Corporation Device a151 Physical Slot: 4 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f3140000 (64-bit, prefetchable) [size=512] Memory at f3100000 (64-bit, prefetchable) [size=256K] Capabilities: <access denied> Kernel driver in use: aclpci_a10_ref Kernel modules: altera_cvp, aclpci_a10_ref_drv This problem is fixed beginning with the FPGA SDK for OpenCL™ software version 18.1.1Why is the input register not registered in the negative input pins, rx_in[*](n) of the ALTLVDS_RX megafunction?
Description Due to a problem in the Quartus® Prime Standard Edition Software version 23.1 and earlier, you might see that the input register is not registered in the ALTLVDS_RX megafunction's negative input pins, rx_in[*](n). This is because the synthesis attributes "LVDS_RX_REGISTER=LOW" and "LVDS_RX_REGISTER=HIGH" are not assigned to the register in the Low-voltage differential signaling (LVDS) receiver interfaces. Resolution To work around the problem, add the following assignments in the Quartus® Settings File (.qsf): set_instance_assignment -name LVDS_RX_REGISTER LOW -to "altlvds_rx:ALTLVDS_RX_component|altlvdsrx_lvds_rx:auto_generated|altlvdsrx_lvds_ddio_in:ddio_in|ddio_l_reg" set_instance_assignment -name LVDS_RX_REGISTER HIGH -to "altlvds_rx:ALTLVDS_RX_component|altlvdsrx_lvds_rx:auto_generated|altlvdsrx_lvds_ddio_in:ddio_in|ddio_h_reg" This problem is currently scheduled to be fixed in a future release of the Quartus® Prime Standard Edition Software.Embedded Peripherals IP User Guide - Altera® FPGA MII to RMII Converter Core - Table 461. The Parameter Scenario is incorrect
Description Table 461. Parameter Usage Scenario, in section 50. Intel® FPGA MII to RMII Converter Core in the Embedded Peripherals IP User Guide is incorrect: UG-01085 ID: 683130 Version 2021.12.13 50.3 Parameters Resolution The last two rows of this table should show MAC_SPEED as 0. MIIMAC2CORESPEED10 equals port ena_10 The correct table should look like the image shown below: This updated information has been added to Version 22.3 (2023.02.09) of the Embedded IP User Guide.Why are there seed dependent functional failures in a timing clean design when compiled in the Intel® Quartus® Prime Pro Edition Software version 20.1 and earlier?
Description Due to a problem in the Intel® Quartus® Prime Pro Edition Software version 20.1 and earlier, registers that have been retimed might fail to reset correctly. This error might be seen on the Intel® Arria® 10, Intel® Cyclone® 10 GX, Intel® Stratix® 10, and Intel Agilex® 7 devices when all the following settings are set to "ON" (the default setting is "ON"). set_global_assignment -name FITTER_EARLY_RETIMING ON set_global_assignment -name PHYSICAL_SYNTHESIS ON set_global_assignment -name ALLOW_REGISTER_RETIMING ON Note that this problem specifically impacts design with registers driven by different control signal set (such as synchronous reset and enable signals), which were retimed across combinational logic and has a feedback path. For more information regarding a known DSP-related physical synthesis problem, see Why are there seed dependent functional failures where the registers feeding into and from DSP blocks stuck in reset status when compiled in the Intel® Quartus® Prime Pro Edition Software version 20.1? Resolution If you are still in the design phase of your project, and are using the Intel® Quartus® Prime Pro Edition Software version 20.1 or earlier, but cannot move to the latest version: (1) Download and install the Solution Patch from the appropriate link below. Recompile your design with the Solution Patch installed. If you are targeting the Intel® Quartus® Prime Pro Edition Software version 20.1 or earlier, and your project is finalized and in the production phase, follow through steps (1) to (3) for impact assessment on each individual compilation: (1) Download and install the Screening Patch from the appropriate link below. (2) Recompile your design with the Screening Patch installed. a. If your design is affected, you will see following warning in Quartus compilation flow message window. Proceed with Step (3). Warning (21940): Screening patch found a case where the Retimer might create incorrect logic for register "<RTL_name_of_register>" driving lut. Install the solution patch to fix the problem, available in the knowledge database solution: https://www.intel.com/content/altera-www/global/en_us/index/support/support-resources/knowledge-base/tools/2020/why-are-there-function-failures-in-some-seeds-while-there-are-no.html b. If the above warning is not reported, no further action is required. (3) Download and install the Solution Patch from the appropriate link below. Recompile your design with the Solution Patch installed. For Intel® Quartus® Prime Pro Edition Software version 18.1, download the Screening Patch 0.53 and Solution Patch 0.49 from the appropriate link below. Intel® Quartus® Prime Pro Edition Software version 18.1 Screening Patch 0.53 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 18.1 Screening Patch 0.53 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 18.1 Screening Patch 0.53 (.txt) Intel® Quartus® Prime Pro Edition Software version 18.1 Solution Patch 0.49 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 18.1 Solution Patch 0.49 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 18.1 Solution Patch 0.49 (.txt) For Intel® Quartus® Prime Pro Edition Software version 19.1, download the Screening Patch 0.55 and Solution Patch 0.51 from the appropriate link below. Intel® Quartus® Prime Pro Edition Software version 19.1 Screening Patch 0.55 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.1 Screening Patch 0.55 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.1 Screening Patch 0.55 (.txt) Intel® Quartus® Prime Pro Edition Software version 19.1 Solution Patch 0.51 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.1 Solution Patch 0.51 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.1 Solution Patch 0.51 (.txt) For Intel® Quartus® Prime Pro Edition Software version 19.2, download the Screening Patch 0.30 and Solution Patch 0.26 from the appropriate link below. Intel® Quartus® Prime Pro Edition Software version 19.2 Screening Patch 0.30 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.2 Screening Patch 0.30 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.2 Screening Patch 0.30 (.txt) Intel® Quartus® Prime Pro Edition Software version 19.2 Solution Patch 0.26 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.2 Solution Patch 0.26 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.2 Solution Patch 0.26 (.txt) For Intel® Quartus® Prime Pro Edition Software version 19.3, download the Screening Patch 0.67 and Solution Patch 0.60 from the appropriate link below. Intel® Quartus® Prime Pro Edition Software version 19.3 Screening Patch 0.67 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.3 Screening Patch 0.67 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.3 Screening Patch 0.67 (.txt) Intel® Quartus® Prime Pro Edition Software version 19.3 Solution Patch 0.60 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.3 Solution Patch 0.60 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.3 Solution Patch 0.60 (.txt) For Intel® Quartus® Prime Pro Edition Software version 19.4, download the Screening Patch 0.39 and Solution Patch 0.35 from the appropriate link below. Intel® Quartus® Prime Pro Edition Software version 19.4 Screening Patch 0.39 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.4 Screening Patch 0.39 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.4 Screening Patch 0.39 (.txt) Intel® Quartus® Prime Pro Edition Software version 19.4 Solution Patch 0.35 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 19.4 Solution Patch 0.35 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 19.4 Solution Patch 0.35 (.txt) For Intel® Quartus® Prime Pro Edition Software version 20.1, download the Screening Patch 0.52 and Solution Patch 0.32 from the appropriate link below. Intel® Quartus® Prime Pro Edition Software version 20.1 Screening Patch 0.52 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 20.1 Screening Patch 0.52 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 20.1 Screening Patch 0.52 (.txt) Intel® Quartus® Prime Pro Edition Software version 20.1 Solution Patch 0.32 for Windows (.exe) Intel® Quartus® Prime Pro Edition Software version 20.1 Solution Patch 0.32 for Linux (.run) Readme for Intel® Quartus® Prime Pro Edition Software version 20.1 Solution Patch 0.32 (.txt) Note: 1. Caution: Patch installation sequence for Screening Patch and Solution Patch matters – the latest installed patch overrides the previous patch. 2. Do not install the screening patch after installing the solution patch. Ensure that ONLY the Screening Patch is installed during screening step. You may then install solution patch on top of the Screening Patch once your screening step is completed with specific warning messages reported. This problem is fixed beginning with the Intel® Quartus® Prime Pro Edition Software version 20.2.
Why cant my USB Blaster III Development cable program in active serial through Quartus Programmer?
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. 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.Error (213009): File name "output_files/afu_import.green_region.pmsf" does not exist or can't be read
Description Due to a problem in the Intel® FPGA Add-on for oneAPI Base Toolkit software version beta01, all FPGA hardware compiles fail for designs targeting an Intel® Programmable Acceleration Card with the Intel® Arria® 10 GX FPGA. The compilation fails due to an internal license expired on December 31st, 2019. Resolution To work around this problem in the Intel® FPGA Add-on for oneAPI Base Toolkit software version beta01, download the patch and install it using follow these steps: 1. Untar oneAPI_fpga_addon_beta01_patch01.tar 2. Cd <directory where you untar above file> 3. Run chmod u x QuartusProSetup-17.1.1-Patch-1.03dcp-linux.run 4. Run sudo ./QuartusProSetup-17.1.1-Patch-1.03dcp-linux.run --mode unattended --installdir "/opt/intel/inteloneapi/intelfpgadpcpp/2021.1-beta01/QuartusPrimePro/17.1.1" --skip_registration 1 --accept_eula 1