Error: niosv_g_dcache.sv: part-select direction is opposite from prefix index direction
Description Due to a problem in the: Quartus® Prime Pro Edition Software version 24.3.1, 25.1, and Quartus® Prime Standard Edition Software version 24.1 When the Nios® V/g processor is configured with No Data Cache and enabled with Error Detection and ECC Status Reporting, performing Analysis and Synthesis fails with the error "niosv_g_dcache.sv: part-select direction is opposite from prefix index direction". Note that this issue has no relationship with No Instruction Cache. Figure. Nios® V/g Processor Setting to Replicate the Error Resolution To work around this error, Select 1Kbytes Data Cache. Apply a Peripheral Region that covers the whole Nios® V processor’s data_manager address map Enable Error Detection and ECC Status Reporting. By implementing Peripheral Region, the above settings can emulate an ECC-enabled Nios® V processor system that operates without caches. Figure. Workaround (in this example, the whole Nios® V processor’s data_manager address map is 1GB) This problem is scheduled to be fixed in a future release of the Quartus® Prime Edition Software.Why doesn't the Triple-Speed Ethernet (TSE) FPGA IP for all devices always maintain a negative running disparity during idle cycles as per the IEEE 802.3 standard?
Description Due to a problem in the Quartus® Prime Pro Edition software, when using the Triple-Speed Ethernet (TSE) FPGA IP across supported device families, the transmitter may not maintain a negative running disparity during idle cycles as defined in the IEEE 802.3 standard. Specifically, the first IDLE sequence after a packet or configuration set is not always generated as /I1/, which is required to restore the running disparity to negative. Resolution A patch is available to fix this problem for the Quartus® Prime Pro Edition software version 24.1 for Agilex™ 7 FPGA F-Series E-Tile devices. Download version 24.1 patch 0.47 for Windows and Linux below This patch ensures the transmitter maintains negative running disparity for Agilex™ 7 FPGA F-Series E-Tile devices by inserting the first idle sequence (/I1/) whenever required, followed by all subsequent idle sequences (/I2/), maintaining compliance with the IEEE 802.3 standard. Please contact your local Sales representative or submit a request through the Support page for further support. This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.Error (16045): Instance "ccip_std_afu|bsp_logic_inst|board_inst" instantiates undefined entity "board" File: /home/anchen/Downloads/dla/build/dla/build/bsp_logic.sv Line: 133
Description Due to a problem in the Intel® Quartus® Prime Pro Edition Software version 17.1.1, this error may occur when you compile the dla2019r1 source code. Resolution To work around this problem, please modify the build.sh file and add the below environment variable to line 175 export QUARTUS_ROOTDIR_OVERRIDE="$QUARTUS_ROOTDIR" This problem has been fixed in dla2019r3.Why does a kernel panic occur when OpenCL™ Applications are executed on Intel® FPGA Development Kits with IOMMU support enabled?
Description When executing OpenCL™ host applications on an attached development kit while IOMMU (e.g. intel_iommu) is enabled in a Linux Kernel, a kernel panic may occur and cause the host to hang. This may happen even if 'aocl diagnose' and 'aocl program' pass. The hang occurs because the OpenCL™ board support packages (BSPs) for the development kits don't support SR-IOV. Resolution To work around this problem, disable IOMMU functionality : For example on CentOS7.4, with grub2, UEFI and intel_iommu : 1. Edit /etc/default/grub and delete the following line. intel_iommu=on in GRUB_CMDLINE_LINUX 2. Update grub configuration file grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg 3. Reboot 4. Check /proc/cmdline Ensure intel_iommu=on does not appear on the kernel command line. This workaround does not apply to the Intel FPGA Programmable Acceleration Card (PAC) since that OpenCL™ BSP does support SR-IOV. If IOMMU is disabled when using the PAC, refer to the Intel® Acceleration Stack Quick Start Guide for instructions to enable the Intel IOMMU driver.error: Unexpected use of HDL library function(s) (possibly due to taking the address of the function)!
Description You may see this error message when the Intel® FPGA SDK for OpenCL™ compiler executes an EFI(Extensible Firmware Interface) function which is equivalent to its OpenCL funtion Resolution This problem is fixed beginning with the Intel FPGA SDK for OpenCL compiler software version 18.1.ERROR: CL_INVALID_KERNEL_NAME
Description If you run vector_add opencl example design on Intel® Programmable Acceleration Card with Intel® Arria®10 GX FPGA . An error may occur as follows: [root@localhost vector_add]# ./bin/host Initializing OpenCL Platform: Intel(R) FPGA SDK for OpenCL(TM) Using 1 device(s) pac_a10 : PAC Arria 10 Platform (pac_a10_f100000) Using AOCX: vector_add.aocx Context callback: Specified kernel was not built for any devices ERROR: CL_INVALID_KERNEL_NAME Location: host/src/main.cpp:169 Failed to create kernel Segmentation fault (core dumped) Resolution You should check if your initialization script file (for example the init_env.sh file) has the following enironment variables set: CL_CONTEXT_COMPILER_MODE_ALTERA=3 CL_CONTEXT_COMPILER_MODE_INTELFPGA=3 To work around this problem, you should unset the environment variables, and try running the host again.Why does the report.html can not display on the Intel® Programmable Acceleration Card with Arria® 10 GX FPGA?
Description If you compile OpenCL™ example design, the report.html may not be displayed on the CentOS 7.4/Kernel 3.10 server as follow: Even if you move the .html file to your local computer, it also can not display as follow: Resolution To work around this problem, you should copy the entire report folder from the server to the local computer, the html file can be display normally as follow: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.1Error: aoc: The Intel® Kernel Builder for OpenCL™ compiler (ioc64) can not be found
Description Due to a problem in version 19.1 and 19.2 of the Intel® FPGA SDK for OpenCL™, if you compile your OpenCL project for emulation by adding -fast-emulator, Errors may occur as following: Error: aoc: The Intel® Kernel Builder for OpenCL™ compiler (ioc64) can not be found This is because for fast emulator support, the "Intel SDK for OpenCL Applications" must also be installed. It is separate from the Intel® FPGA SDK for OpenCL™. Resolution To work around this problem, you must download and install the correct version of the "Intel SDK forOpenCL Applications" You may be required to log into your account during this process. 1. Go to the following link http://fpgasoftware.intel.com/ 2. Select your Quartus software version in the dropdown menu 3. Select Linux or Windows 4. Select Akamai DLM3 Download Manager or Direct Download 5. Click the Additional Software tab 6. Download and install “Intel SDK for OpenCL Applications (for Intel Code Builder for OpenCL API) “Why does aocl diagnose fail while using Windows 10?
Description When using Windows® 10, aocl diagnose may fail even though the board is installed in the PC and the user has installed the drivers using aocl install. If the user has installed the drivers then opens Windows Device Manager, the board should show up under "unknown device". Why does this happen? Windows 10 enforces driver signatures by default and the OpenCL drivers for our development kits are not "signed" for Windows 10. Resolution To work around this problem, run aocl uninstall then reboot the computer. After the computer has restarted, disable Windows 10 signed driver enforcement as shown below. Click the Start menu and select Settings. Click Update and Security. Click on Recovery. Click Restart now under Advanced Startup. (The computer won't actually restart until after step 8.) Click Troubleshoot. Click Advanced options. Click Startup Settings. Click on Restart. On the Startup Settings screen press 7 or F7 to disable driver signature enforcement. After the computer has finished booting up, run aocl install. Run aocl diagnose to verify that it succeeds Note: If your system has BitLocker enabled, you will need to enter the recovery key between steps 8 and 9 above. You must get the recovery key before starting the above procedure. To get the recovery key, do the following: Run Bitlocker Manager Select “Back up your Recovery Key” Select “Print the recovery key” This problem is scheduled to be fixed in a future version of Quartus.
