U-Boot "Synchronous Abort" boot failure on Terasic Atum A5 Rev B via Quartus 24.3 .jic generation
I am reaching out for technical assistance regarding a reproducible boot failure on the Terasic Atum A5 Rev B development board (Agilex 5) when using Quartus Prime Pro 24.3. I am attempting to compile a custom design that utilizes the Lightweight HPS-to-FPGA (lwhps2fpga) bus. My current workflow is as follows: Compile the project in Quartus 24.3 to generate the .sof file. Merge the .sof with the official Terasic FSBL .hex file. Use the Programming File Generator (PFG) to create a .jic file. Flash the .jic to the QSPI. The Issue: When flashing the .jic generated by this workflow, the boot process fails during the main U-Boot phase. The U-Boot SPL and ATF (BL31) load successfully. However, after U-Boot attempts to load the environment, the system crashes with a "Synchronous Abort" handler (esr 0x96000010, far 0x108d2000). This triggers a CPU reset with the message ### ERROR ### Please RESET the board ###. (I have attached the full UART terminal log of the boot sequence for reference). Isolation Testing: To isolate the issue from my custom logic, I applied this exact same compilation and .jic generation workflow to the official Terasic GHRD bundled with the board. The result was identical—the GHRD .jic generated by Quartus 24.3 crashes at the exact same U-Boot Synchronous Abort. Conversely, when I bypass compilation and simply flash the original, pre-compiled .jic provided in the Terasic resource package, the board boots into Linux flawlessly. This confirms the physical hardware is fully functional and the issue is strictly isolated to the .jic files being generated by the 24.3 workflow. Questions: Is there a known issue or missing step in the Quartus 24.3 workflow when merging the FSBL or configuring the .jic for the Agilex 5 that would cause U-Boot to encounter a Data Abort (likely when probing the AXI bridges)? What are the exact PFG parameters or required patches to successfully generate a booting .jic for this board under the 24.3 release? I look forward to your guidance on resolving this workflow issue
Fitter error in A5ED043AB23AI2V Example design
Hi, I have tried using the example design of the A5ED065BB32AE4SR0 development kit and modified the part number to A5ED043AB23AI2V. During compilation, I am encountering a fitter error when both PCIe and USB 3.1 are enabled together. However, I am able to compile successfully when using each interface individually. Could you please help me understand how to resolve this issue?
System-Console 26.1 java.io.IOException: Cannot run program "ps": CreateProcess error=2
System-Console 26.1 throws this error. Yet it runs fine. Any fix for it? Tried on multiple computers: Windows 10, 11, ... FINE: Enabling plugin: com.altera.systemconsole.issp.internal.ISSPPluginProvider May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery loadPlugins FINE: Discovered plugin: com.altera.systemconsole.monitor.internal.MonitorPluginProvider May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler$2 run FINE: Enabling plugin: com.altera.systemconsole.monitor.internal.MonitorPluginProvider May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery loadPlugins FINE: Discovered plugin: com.altera.systemconsole.plugin.pli.PliDeviceProvider May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler$2 run FINE: Enabling plugin: com.altera.systemconsole.plugin.pli.PliDeviceProvider May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery loadPlugins FINE: Discovered plugin: com.altera.systemconsole.plugin.remotechannel.RemoteChannelPluginProvider May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler$2 run FINE: Enabling plugin: com.altera.systemconsole.plugin.remotechannel.RemoteChannelPluginProvider java.io.IOException: Cannot run program "ps": CreateProcess error=2, The system cannot find the file specified at java.base/java.lang.ProcessBuilder.start(Unknown Source) at java.base/java.lang.ProcessBuilder.start(Unknown Source) at java.base/java.lang.Runtime.exec(Unknown Source) at java.base/java.lang.Runtime.exec(Unknown Source) at java.base/java.lang.Runtime.exec(Unknown Source) at com.altera.systemconsole.plugin.remotechannel.RemoteChannelTclExtension.isScmdRunning(RemoteChannelTclExtension.java:88) at com.altera.systemconsole.plugin.remotechannel.RemoteChannelTclExtension.<init>(RemoteChannelTclExtension.java:43) at com.altera.systemconsole.plugin.remotechannel.RemoteChannelPluginProvider.installTclExtension(RemoteChannelPluginProvider.java:54) at com.altera.systemconsole.plugin.remotechannel.RemoteChannelPluginProvider.install(RemoteChannelPluginProvider.java:39) at com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler$2.run(SystemFilesystem.java:334) at com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler.pluginEnabled(SystemFilesystem.java:341) at com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler.childrenAdded(SystemFilesystem.java:367) at com.altera.systemconsole.internal.core.SystemNode.fireChildrenAdded(SystemNode.java:291) at com.altera.systemconsole.internal.core.SystemNode.addChildren(SystemNode.java:265) at com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery.loadPlugins(SystemConsole.java:246) at com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery.run(SystemConsole.java:213) at com.altera.systemconsole.internal.core.SystemExecutor$4.run(SystemExecutor.java:551) at com.altera.systemconsole.internal.core.SystemExecutor$ComparableTask.run(SystemExecutor.java:151) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.base/java.lang.ProcessImpl.create(Native Method) at java.base/java.lang.ProcessImpl.<init>(Unknown Source) at java.base/java.lang.ProcessImpl.start(Unknown Source) ... 21 more May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemConsole logWarning WARNING: Debug Server failed to start May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery loadPlugins FINE: Discovered plugin: com.altera.systemconsole.scripting.UserScriptSupport May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler$2 run FINE: Enabling plugin: com.altera.systemconsole.scripting.UserScriptSupport May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery loadPlugins FINE: Discovered plugin: com.altera.systemconsole.scripting.ui.ConsolePlugin May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemFilesystem$PluginHandler$2 run FINE: Enabling plugin: com.altera.systemconsole.scripting.ui.ConsolePlugin May 07, 2026 2:39:29 PM com.altera.systemconsole.internal.core.SystemConsole$PluginDiscovery loadPlugins FINE: Discovered plugin: com.altera.systemconsole.sldhubchannel.SldHubPluginProviderLicensing ‘Know-How’ Guide
#sharing #debug #altera #alldevices #license Disclaimer: This article is provided as-is for educational purposes only, without warranty of any kind. Use the information at your own risk. Always verify implementations in your specific environment and consult official Altera documentation for production deployments. Introduction Licensing issues are one of the most common reasons FPGA tools fail to start. The good news is that most problems are configuration related and can be fixed quickly by following a simple, step-by-step approach. Sections 1: Start with the Error Message (Most Important!) Always look at the first licensing error message shown by the tool. This is usually the real issue. Any errors that appear later are usually caused by the first problem. Here’s are common error messages and what they usually mean: Invalid hostid → License does not match your machine ID Cannot find license file → Invalid or missing license path Unable to checkout a license → License not found, in use, or server issue 300: License version is outside the range of the contract → license file generated with blank FLEXlm error: Vendor daemon version is too old → daemon used mismatch or too old Cannot checkout uncounted license in Windows Terminal Services → Questa does not support remote desktop. Most common errors already have known fixes. Try searching the error message or key issue at: Altera Knowledge Base: https://community.altera.com/category/top/kb/knowledge-base Altera Community Forums: https://community.altera.com/category/forums For floating licenses, you can also check the FlexNet error code list: Error Code Descriptions Don’t try to fix everything at once. Fix the first error, then retry. In many cases, the rest will disappear automatically. 2: Check Your License (.dat) File Open the .dat license file using a text editor (for example, Notepad) and verify the following. i. Machine ID (NIC / HOST ID) The license is locked to a specific machine ID. Example in the license file: # Primary Machine ID-NIC ID 12AB34C56EF7 If the Host ID doesn’t match your machine ID, the license will not work. Helpful Tips 1: ----------------------------------------------------- START ----------------------------------------------------- Quartus software can automatically detect the Machine ID. To view this, go to Tools → License Setup, then check Local System Information and select one of the detected NIC IDs. ------------------------------------------------------ END ------------------------------------------------------ ii. License Type Licenses are set up differently, so confirm which type you have.Look for one of these lines: # Fixed Node License → Nodelocked license # Floating Server License → Floating license Nodelocked: Locked to one machine Floating: Served from a license server and shared Make sure you’re following the setup steps that match your license type. iii. Product License Summary Find the Product License Summary section and confirm it lists the tools/IP you’re planning to use. Examples: Quartus® Prime Software (Standard / Pro) Questa® FPGA Starter Edition (SWQUESTA) If a tool or IP is not listed here, it won’t be able to check out a license—even if the license file setup successfully. iv. License Expiration & Maintenance Licenses can look similar but behave very differently. We have: a. Perpetual License Has a Maintenance Expiration date You can use tool versions released before that date Example shown in license file: # Maintenance Expiration of 2026.06 # No license expiration date b. NonPerpetualLicense Has a hard expiration date License stops working after this date Example shown in license file: # License Expires 20Jun2026 Always doublecheck the license expiration & maintenance date before moving on. 3. Verify Environment Variables The tools use environment variables to find the license. If these are wrong, the tools may not find your license—or may use an old license file. Common environment variables: Different tools use different environment variables to locate the license. LM_LICENSE_FILE → Quartus® Prime SALT_LICENSE_SERVER → Questa* FPGA Edition Depending on the license type, they should point to: Nodelocked license: Full path to the .dat file Floating license: port@hostname Examples: LM_LICENSE_FILE=C:\licenses\license.dat LM_LICENSE_FILE=25000@licenseserver Next verify the environment variable. Open Command Prompt and run: echo %LM_LICENSE_FILE% If nothing is printed, the environment variable is either not set or the changes have not taken effect. If it is the latter, close and reopen the command prompt after making the changes. If the variable points to an incorrect location, update it accordingly. Note that outdated or incorrect environment variables are a very common source of issues. Helpful Tips 2: ----------------------------------------------------- START ----------------------------------------------------- There is a quick way to set using command line. Open Command Prompt and run: Windows: setx LM_LICENSE_FILE <path_to_license_file> Linux: setenv LM_LICENSE_FILE "<path_to_license_file>" ------------------------------------------------------ END ------------------------------------------------------ 4. Check the License Server (Floating Licenses Only) If you’re using a floating license, verify the server. On the client machine: Server hostname resolves correctly Network is working Firewall is not blocking the license port On the license server: License server process is running Vendor daemon is running Server log shows no fatal errors Licenses are available (not all checked out) If the server isn’t running properly, clients won’t be able to get licenses. 5. Scenario / Walkthrough i) Floating License Setup Walkthrough A floating license setup walkthrough (Know-How: Set Up a Floating License) is available to guide you through the complete process of configuring a floating license. Know-How: Set Up a Floating License (Step-by‑Step Walkthrough) | Altera Community - 352000 ii) Manual License File Download (License Email Not Received) If you generate a license but do not receive the license email within 5 minutes, you can manually download the license file using the steps below: Log in to SSLC. Navigate to Computers and License Files. Click the Primary Computer ID. Go to the ENTITLEMENTS tab. Select the relevant license (for example, LR‑****). Click the license file link to download the license file. Example shown below: iii) SSLC Access Denied Error Resolution If you encounter the message below when attempting to sign in to SSLC, please refer to the community thread linked below for the solution: Message:“You do not currently have access to this site. Please follow the instructions on the help page to request access.” Self service license server doesn't work | Altera Community - 352404 iv) Changing License Type (Fixed ↔ Floating) To change an existing license type: Log in to SSLC. Navigate to Computers and License Files. Navigate to the license file and click Edit in the drop-down menu. Change the License Type to FIXED or FLOAT, click Save. Now you can generate the license file with the Existing Computer. For your reference, this error occurs when you attempt to create a computer with the same NIC ID. You cannot create two computers with the same NIC ID, even with different license types. *Additionally, changing the license type will use up one rehost count. If all 3 rehost count have been used up, you can not change the license type for the specific computer anymore. Conclusion Licensing issues are almost always setup or configuration problems. Following this guide step-by-step starting with the error message will resolve most issues. If you’re still stuck after trying all the steps, feel free to post your issue on the Altera Community Forum (https://community.altera.com/category/forums) for help. When posting, please try to include the following: i. Error Details The exact licensing error message, copied as is If there are multiple errors, include the first one shown ii. Tool Information Product name (example: Quartus/Questa) Tool version (example: Quartus Pro 25.3/ Questa Altera FPGA Edition 2025.2) Operating system (Windows or Linux, version if known) iii. License Information License type: Nodelocked (fixed)/ Floating (network) Purchased / Evaluation license If possible, a copy of the license file (.dat) iv. What You’ve Already Tried Steps you have already checked or attempted Any workaround that partially worked The more complete your post, the faster the community (and Altera support staff) can help. Additional Altera Support Webpages For further information related to licensing, you may check out Altera Licensing Webpages for the wholesome experiences to get your FPGA licensing product setup and running with minimal hassle: FPGA Licensing Support Center Quartus® Prime Software Licensing Questions and Answers Additionally, we have FPGA Software Download and Installation Support webpage: FPGA Software Download and Installation Support Self Service Licensing Center (SSLC) Issues For issue related to the SSLC, please contact Customer Service if you encounter any of the following: Can’t find a product in SSLC Errors when generating a license file Errors when renewing a license file Unable to generate a companion or temporary license Unable to update license users or delegate administrators Need to transfer license ownership between accounts Contact Altera Customer Service here: https://licensing.altera.com/sslc/s/contact-customer-service For account login issue, please mail to: loginsupport@altera.com License Purchase Inquiries For purchasing licenses, pricing questions, or commercial inquiries, please contact an Altera Authorized Distributor: https://www.altera.com/contactA topic explaining a problem with Cyclone V SoC - u-booting .rbf file failure - got rejected.
Hi Altera Comunity et al, I guess this is more of a question for the support and moderator people of this forum. The situation is I just posted a topic explaining a problem I am experiencing with Cyclone V SoC—U-boot failing to load the .rbf (FPGA load configuration ) file , during initial system bootup. I put a lot of information - attached files, links, etc. to give better context around the issue. But that post got flagged as Spam and got rejected. And I am just wondering what to do here. I tried editing that post (removing links and removing attached files) several times already, but it still stays flagged as spam. I don't know what to do further to fix this :( The original issue topic was : "Cyclone-V-SoC: U-Boot fails to fpga load .rbf file - Command 'load' failed: Error -6" Anyone, please advise. Thank you and Best Regards, - Monk M.
Agilex 5E - PCIE PERST# pin - failing compilation
Hello! I'm using Critical Link MytiSom Dev Kit. It has the same FPGA as the Altera Dev Kit - A5ED065BB32AE6SR0. I'm adapting the PCIe Root Port example from Altera - I have assigned the PCIe Gen3x4 lanes to bank 4B. I have checked the pin assignments several times but I keep getting failed compilation with the error attached bellow. Any suggestions on what can cause the issue. I have also attached the pin assignments. Thank youQuestion about VGA parameter in Transceiver Toolkit (Quartus Std 23.1)
Hello, I am using Transceiver Toolkit in Quartus Prime Standard 23.1 (Build 993). I can get and configure the Variable Gain Amplifier (VGA) parameter in the GUI, but I cannot find any corresponding command in the documented Transceiver Toolkit scripting API. From the documentation (683552 - 2018.09.24), I can use the following commands (get & set): transceiver_channel_rx_get_dcgain transceiver_channel_rx_get_eqctrl transceiver_channel_rx_get_dfe_tap_value However, there is no mention of VGA. Could you please clarify whether VGA is mapped to another parameter, or if it is not accessible via scripting? Thank you for your support. Best regards, Huy HO.
