Why does my Quartus® Prime Installation fail with certificate error: SSL certificate problem: unable to get local issuer certificate (curlcode 60)?
Description Due to a problem in the Quartus® Prime Installer Software, you might see the error message shown below when you click Download & Install. This happens because the certificate bundled with the Quartus® Prime Installer Software is no longer accepted by the Altera® Content Delivery Network (CDN). As a result, secure downloads initiated during the installation process cannot be verified using the outdated certificate. The issue impacts the Installer for the following versions of Quartus software: Operating System Quartus Prime Pro Installer Version(s) Quartus Std/Lite Installer Version(s) Microsoft Windows* 23.3 to 25.3.1 23.1std to 25.1std Linux* 23.3 to 23.4 23.1std The KDB workaround provided below applies to the following versions of Quartus software: Quartus Prime Pro Installer Version(s) Quartus Std/Lite Installer Version(s) KDB workaround applies to 24.3 to 25.3.1 24.1std to 25.1std Note that for all other affected versions not covered by the KDB, you cannot use the installer workaround and must download Quartus software package files individually without using the installer. Separate packages can be found in the Individual Files tab of the Quartus Software Download pages. Resolution To work around this problem, follow these steps: 1. Download and unzip the cacert.zip, which contains the cacert.pem certificate file. 2. Specify the new certificate using one of the following methods: i) Command Line Interface (CLI): Open a command prompt or terminal and run the installer with the--cacert option, pointing to the new certificate file. Windows*: qinst_<version>.exe -sp"--cacert <full path to cacert.pem>" Linux*: qinst_<version>.run -- --cacert <full path to cacert.pem> ii) Graphical User Interface (GUI): - Open the Quartus® Prime Installer, navigate to Settings, locate the CA Certificate Path, and specify the full path to the cacert.pem certificate file. - Then, click Apply > OK. This problem is scheduled to be resolved in a future release of the Quartus® Prime Installer Software.Why I can't open Early Power Estimators (EPE) tool in the latest version of Microsoft* Excel?
Description Due to the legacy design of the Early Power Estimator (EPE) worksheets, which include VBA macros, ActiveX components, and embedded DLL files, errors may occur when opening the Excel file on newer Windows platforms or when using Microsoft* Office 365, in both 32-bit and 64-bit versions. When the spreadsheet is opened, several actions occur in the background. Excel extracts the embedded DLLc files to the user's %TEMP% directory. A script then decompresses the DLLc files into standard DLL files. The script subsequently loads and executes the DLL files, which is used by the Excel macros. Why the issue occurs: To extract and execute the required DLL files, the Excel macros rely on a set of commands provided by Microsoft .NET and Microsoft Visual C++ runtime libraries, depending on the specific version of the Excel worksheet. In newer versions of Microsoft Windows and Microsoft Office 365, these runtime components are no longer bundled together by default, and some legacy functions used by older scripts have been deprecated or replaced with newer implementations. As a result, scripts designed for earlier environments may fail when attempting to call these functions. Note: In some systems, some of these are already installed automatically by other 3rd party software tools during installation. Additionally, the legacy script design does not support symbolic linking or modern handling of the user's %TEMP% directory, which can cause issues when extracting and accessing temporary files. Modern systems also enforce stricter security controls, including: ActiveX restrictions in newer versions of Microsoft Excel Trust Center policies that block code execution from untrusted locations Operating system security policies in Microsoft Windows that may prevent DLL execution from the %TEMP% directory if such restrictions are enabled As a result, if any of these conditions are triggered, users may encounter errors such as “Unable to find or load DLL files.” For example, errors may appear related to the zlib.dll file (the 32-bit or 64-bit version used depends on the installed Excel architecture). Resolution To workaround this issue PART A: Unblocking the Excel and Enable Macros/ActiveX 1. Unblock the Excel File • Right-click the EPE Excel file → Properties → Check Unblock under Security. • Click Apply → OK. 2. Enable Macros and ActiveX • Open Excel → File → Options → Trust Center → Trust Center Settings: Enable Macros. Enable ActiveX controls. Leave other settings as default (Safe Mode can remain enabled or disabled). 3. Check whether you can now open the EPE excel sheet. Else proceed to PART B. PART B: Installing the necessary Microsoft .NET and Visual C++ runtime libraries. Microsoft .NET installation Go to your Installed apps settings and find for .NET. It is recommended to have both .NET Runtime and ASP .NET installed in your system. If you already have a version installed on your machine then proceed to the next step( you only require 1 version each), otherwise refer to this location to download Download .NET 8.0 (Linux, macOS, and Windows) | .NET Example: Microsoft Visual C++ Installation As different EPE Excel sheet relies on specific Visual C++ version, you will need to install multiple versions of Visual C++ for both 32bit and 64bit. This is because even though Excel is running on 64bit, existing scripting might have dependency on 32bit functions as well. Recommendation to install C++ version for both 32 bit and 64 bit as below Latest Supported Visual C++ Redistributable Downloads Visual Studio 2017-2026 Visual Studio 2015 (in older Microsoft release, it might show as C++ V14 or 2015-2022 version) Visual Studio 2013 Visual Studio 2012 Example After installing both 32 bit and 64 bit, do restart the system and then try launching the EPE excel sheet again. In some rare occurrences, you might need to install Visual Studio C++ 2010 , Visual Studio C++ 2008 and Visual Studio C++ 2005. Do refer to PART C first as the issue might not be due to Visual C++ but symbolic link. PART C: Symbolic Link issue workaround (optional) If installing the .NET and Visual C++ runtime libraries still does not help in resolving the error opening EPE Excel, you should check whether your %TEMP% file folder is the same as what reported in the error when opening the EPE excel sheet. If the folder path are different between %TEMP% and the path reported by Excel sheet, it means that they are using symbolic link folder. In this case user should copy the .dll files generated out from the %TEMP% when they opened the excel sheet and copy it over to the Windows SySWoW folder (%windir%\SysWOW64). To access your %TEMP% folder , just type %TEMP% into your explorer and it will open your folder location (%TEMP% is set in windows environment variables) From the %TEMP% folder, there are multiple *epe* DLL files if you open different EPE excel sheets. Copy all of these .DLL files into your Windows SysWOW64 folder and try launching the EPE excel sheet again. Example, if using Cyclone® V EPE excel sheet, these are the 4 files required in red box in %TEMP% to be copied over NOTE 1: The SysWOW64 folder is selected because it is part of Windows’ default search locations when required DLL files cannot be found. Alternatively, you can add a custom directory to the Windows Environment Variables (PATH) so that Windows will also search that folder when looking for the DLL files. NOTE 2: Adding the %TEMP% folder into the system environment variables will not have any effect as latest Microsoft Windows have blocked the DLL searching mechanism to prevent search %TEMP% folder as part of the security to prevent remote execution from DLL. Additional Information If all fails, alternatively install Process Monitor from Microsoft to analyze the DLL failure/error 1. Download Process Monitor from this location Process Monitor - Sysinternals 2. Close all excel sheets that is open in Windows. 3. Launch the Process Monitor , then select Filter. Set to Process Name and EXCEL.exe and click Add. 4. After adding the filter, ensure that capturing is started 5. Then open any of the EPE excel file,and wait till you get the DLL (eg. epe_zlib_32bit.dll) error then press pause on the Process Monitor. 6. Then use Find and search for the dll error stated in the excel(eg. epe_zlib_32bit.dll) It will give you a list of things, but important is to check the details on createfile, open, close , query, those are the functions that are in the zlib dll file. Example Good case scenario where no error occurred. Fail case scenario where Windows unable to locate the DLL (due to symbolic link issue)
Why do some GPIO pins drive low during JIC programming in Cyclone® V SoC devices?
Description Due to a problem in the factory default SFL image in the Quartus® Prime Software, some general purpose I/O (GPIO) pins drive low when programming a serial configuration device with JTAG indirect configuration file (.jic) in the following variants of Cyclone® V SoC devices: Cyclone V SE - Member Code A5, Package F896 (31mm) Cyclone V SX - Member Code C5, Package F896 (31mm) Cyclone V ST - Member Code D5, Package F896 (31mm) Resolution To work around this problem, replace the original factory default SFL image for the affected devices with the corrected image by doing the following steps. Download the following file and unzip it. You can find the corrected default SFL image, sfl_enhanced_01_02d120dd.sof. sfl_enhanced_01_02d120dd.sof.corrected.zip Open the directory factory default SFL images location. Quartus® Prime Software : <install directory>/quartus/common/devinfo/programmer Stand-alone Quartus® Prime Software Programmer : <install directory>/qprogrammer/common/devinfo/programmer Find sfl_enhanced_01_02d120dd.sof in the directory and replace it with the corrected SFL image. This problem has been fixed since the Quartus® Prime Pro Edition Software version 19.1. However, the Quartus® Prime Standard Edition Software is still affected by this problem. Use the above workaround when the Quartus® Prime Standard Edition is used or use the Quartus® Prime Pro Edition Programmer tool version 19.1 and later instead. The Quartus® Prime Standard Edition Software will be improved in a future version.Why do write operations fail with an MT25QU01G flash device when using the FPGA Generic QUAD SPI Controller II Core?
Description Due to a problem in the FPGA Generic QUAD SPI Controller II version 18.1, erase operations starting from sector 256 onwards will fail, causing all write operations to be unsuccessful when using an MT25QU01G flash device. Erase and write operations executed below sector 256 will be performed without problems. This problem affects the FPGA Generic QUAD SPI Controller II included with the Quartus® Prime Standard Edition Software version 18.1 Resolution To work around this issue, please download and install the patch file for your Operating system: This problem is fixed starting with the Quartus® Prime Software version 19.1.Is there a known issue with simulating the Cyclone® 10 FPGA LP PLL IP using Verilog?
Description Due to a problem in the Quartus® Prime Standard Edition software version 17.0, the PLL simulation model is not instantiated for Cyclone® 10 FPGA LP devices when performing Verilog simulation. This issue does not apply when simulating the Cyclone® 10 FPGA LP PLL IP using VHDL. Resolution To fix this issue, install the patch below on top of Quartus® Prime Standard version 17.0 and follow the instructions to add extra steps in your simulation run script. if ![file isdirectory verilog_libs] { file mkdir verilog_libs } vlib verilog_libs/altera_mf_ver vmap altera_mf_ver ./verilog_libs/altera_mf_ver vlog -vlog01compat -work altera_mf_ver {c:/intelfpga/17.0/quartus/eda/sim_lib/altera_mf.v} This problem is fixed beginning with the Quartus® Prime Standard Edition software version 18.0.Why does the TX Throughput value shown in Ethernet Toolkit for the F‑Tile Ethernet FPGA Hard IP Design Example not match the expected data rate?
Description In F‑Tile Ethernet FPGA Hard IP Design Example generated using Quartus® Prime Pro Edition software versions 25.3.1 and earlier, you may notice that the TX Throughput reported by the Ethernet Toolkit appears lower than the expected line rate. This behavior is expected. The ROM‑based packet generator included in the design example has the following characteristics: It defaults to a 64‑byte packet size, and It inserts non‑zero inter‑packet gaps (IPG) These factors inherently reduce the measured throughput compared to the theoretical maximum line rate. Resolution To accurately validate the TX Throughput of the design, Altera recommends to use a standard Ethernet traffic tester capable of running in client loopback mode. This allows to measure the actual TX throughput without limitations imposed by the built‑in ROM packet generator. There is no plan to fix this problem.Why does the text overlap in the ALTPLL IP Parameter Editor?
Description Due to a problem in the Quartus® Prime Standard Edition Software version 25.1, you might see that the text overlaps in the ALTPLL IP Parameter Editor on the Windows* Operating System. This prevents the ALTPLL IP from being instantiated. This problem does not occur in the Quartus® Prime Standard Edition Software version 24.1 and earlier. Resolution To work around this problem in the Quartus® Prime Standard Edition Software version 25.1, download and install the patch below: This problem is scheduled to be resolved in a future release of the Quartus® Prime Standard Edition Software.Why has the MegaWizard Plug-In Manager failed to launch?
Description Due to a problem in Intel® Quartus® Prime Standard Software version 17.0, the following error message will be displayed when launching the DDR3 SDRAM Controller with UniPHY Intel® FPGA IP. Failed to launch MegaWizard Plugin Manager: DDR3 SDRAM Controller with UniPHY 17.0 could not be found in the specified library paths. Resolution A patch is available to fix this problem for the Intel® Quartus® Prime Standard Software version 17.0.2. Download and install Patch 2.02 from the appropriate link below. Download the patch Intel® Quartus® Prime Standard Edition version 17.0.2 Patch 2.02 for Windows* (.exe) Download the patch Intel® Quartus® Prime Standard Edition version 17.0.2 Patch 2.02 for Linux* (.run) Download the Readme for Intel® Quartus® Prime Standard Edition version 17.0.2 Patch 2.02 (.txt) Additional Information This problem is fixed starting with the Intel® Quartus® Prime Standard Edition software version 17.1.Fatal Error: Access Violation at 00007FFEACC49E5A
Description Due to a problem in the Intel® Quartus® Prime Standard Edition Software version 21.1, you might see this error when adding finite state machine nodes in Signal Tap. Resolution A patch is available to fix this problem for the Intel® Quartus® Prime Standard Edition Software version 21.1. Download and install the patch from the following links: Intel® Quartus® Prime Software v21.1 Patch 0.13std for Window (.exe) Intel® Quartus® Prime Software v21.1 Patch 0.13std for Linux (.run) Readme for Intel® Quartus® Prime Software v21.1 Patch 0.13std (.txt) This problem is fixed starting with the Intel® Quartus® Prime Standard Edition Software version 22.1.Error: SDC_ENTITY not allowed for EFileKind, must be in {[VERILOG, VERILOG_ENCRYPT, SYSTEM_VERILOG, SYSTEM_VERILOG_ENCRYPT, VERILOG_INCLUDE, SYSTEM_VERILOG_INCLUDE, VHDL, VHDL_ENCRYPT, SDC, MIF, HEX, DAT, QXP, HPS_ISW, PLI_LIBRARY, VPI_LIBRARY, OTHER]}
Description Due to a problem in the Intel® Quartus® Prime Standard Edition Software version 21.1, the error message above may be seen while executing 'generate HDL' for the Error Message Register Unloader Intel® FPGA IP Core when using Intel® Stratix® V, Intel® Arria® V, or Intel® Cyclone® V devices. The full error message is shown below: Error: SDC_ENTITY not allowed for EFileKind, must be in {[VERILOG, VERILOG_ENCRYPT, SYSTEM_VERILOG, SYSTEM_VERILOG_ENCRYPT, VERILOG_INCLUDE, SYSTEM_VERILOG_INCLUDE, VHDL, VHDL_ENCRYPT, SDC, MIF, HEX, DAT, QXP, HPS_ISW, PLI_LIBRARY, VPI_LIBRARY, FLI_LIBRARY, OTHER]} while executing "add_fileset_file $sdc_file SDC_ENTITY PATH $sdc_file {NO_AUTO_INSTANCE_DISCOVERY NO_SDC_PROMOTION}" (procedure "generate_verilog_fileset" line 24) invoked from within "generate_verilog_fileset $name $ifdef_params_list" (procedure "generate_synth" line 9) invoked from within "generate_synth altera_emr_unloader" Resolution A patch is available to fix this problem for the Intel® Quartus® Prime Standard Edition Software version 21.1 Download and install Patch 0.08std for the Intel® Quartus® Prime Standard Edition Software version 21.1 from the appropriate link below: (To download the .run file, right-click on the above link and choose “Save link as”) Intel® Quartus® Prime Standard Edition Software version 21.1 patch: Download patch 0.08std for Windows (.exe) Download patch 0.08std for Linux (.run) Download the Readme for patch 0.08std (.txt) This problem is fixed starting from Intel® Quartus® Prime Standard Edition Software version 22.1.
