Recent Content
Is there any way to script the creation of a signal tap instance?
I have been trying to see if it is possible to create a signal tap instance using a scripted approach. For example, create an instance, add some signals from the design using wildcards, setup triggers etc. But I can't seem to find an API for this - does it exist? I have seen that there are scripting APIs for interacting to an existing running signal tap instance, but that isn't what I'm looking for. I could script the creation of a "signal tap logic analyser" IP instance and then instantiate that in HDL code in my design. However that seems quite heavy - adding it do different parts of the design becomes cumbersome and I don't want to keep them in my codebase. The use case is I want to have a collection of debugging nodes that I can conditionally insert and quickly change the configuration of, without cluttering my main RTL. Thanks!5Views0likes0CommentsWhy is the Stratix V GT device receiver parallel data output incorrect when using Quartus II software versions 14.0 to 15.0?
Description Due to a problem in the Quartus® II software versions 14.0 to 15.0, you may see an incorrect rx_parallel_data[63:0] parallel data output on a Stratix® V GT receiver. The rx_parallel_data[127:64] will be correct. Resolution To work around this problem, you can install Quartus II software version 15.0, then download and install the patch below Download the version 15.0 patch 0.21 for Windows (.exe) Download the version 15.0 patch 0.21 for Linux (.run) Download the Readme for the Quartus II software version 15.0 patch 0.21 (.txt) This problem will be fixed in a future version of the Quartus II software.Why does my PCIe link get stuck in the Detect state for the Avalon® memory mapped interface in a Cyclone® IV device?
Description Due to a problem in the Cyclone® IV FPGA PCIe Hard IP PMA, the link might be stucked in the Detect.Active state. This is because the transceiver receiver detect logic is not returning a PHYSTATUS pulse on the PIPE interface to the Hard IP core if the low period of two consecutive TxDetectRx is less than 544 ns. Resolution Manually change the Hard IP reset logic to assert the crst and srst signal for at least 1 us. You can use the following files to view the changes required for the Avalon® memory mapped interfaces to satisfy the requirement above. pcie_compiler_0 (.v) : Added reset logic can be found on multiple lines using the keyword new. Put these lines in your instantiation file for Avalon memory mapped interfaces. pcie_compiler_0 (.vhd): Added reset logic can be found on multiple lines using the keyword new. Put these lines in your instantiation file for Avalon memory mapped interfaces. This problem has been fixed in Platform Designer implementations of the Cyclone IV PCIe Hard IP. Related Articles Why does my PCIe link get stuck in the Detect state for Arria II and Stratix IV devices?Why do some IP MegaCores with a valid license fail to compile with Stratix V devices?
Description Due to a problem with the Quartus® II software versions 10.1 and later, designs containing IP MegaCore® functions from the list below may cause compilation to stop with a license error even if you have a valid IP MegaCore license. This is due to a bug in the encryption of these cores for Stratix® V devices. The list of affected cores is: POS-PHY Level 4 Reed Solomon Viterbi CIC FIR Compiler NCO FFT Alpha Blending Mixer CSC Chroma Resampler Clipper Color Plane Sequencer Deinterlacer FIR Filter 2D Frame Buffer Gamma Corrector Interlacer Median filter 2D Scaler Test Pattern Generator Triple Speed Ethernet A typical error message (using the Triple Speed Ethernet core as an example) looks like: Error: Core "Triple Speed Ethernet" (6AF7_00BD) is not enabled for current device family Affected Configurations All variations of the above cores targeting the Stratix V device family using version 10.1 or later. Workaround A patch is available to fix this problem for the Quartus II software version 10.1 SP1. If you are using the Quartus II software version 10.1, you must upgrade to 10.1 SP1 before using this patch. Download and install patch 1.19 from the appropriate link below: Download the version 10.1 SP1 patch 1.19 for Windows (.exe) Download the version 10.1 SP1 patch 1.19 for Linux (.tar) Download the Readme for the Quartus II software version 10.1 SP1 patch 1.19 (.txt) This problem is scheduled to be fixed in a future version of the Quartus II software.158Views0likes0CommentsInternal Error: Sub-system: VRFX, File: /quartus/synth/vrfx/verific/vhdl/vhdlvalue_elab.cpp, Line: 6595
Description This error may be generated by the Quartus® II software versions 10.0 and 10.0 SP1 when compiling VHDL source files which use arrays. A patch is available to fix this problem for the Quartus II software version 10.0 SP1. Download and install Patch 1.133 from the appropriate link below. Download the version 10.0 SP1 Patch 1.133 for Windows (.exe) Download the version 10.0 SP1 Patch 1.133 for Linux (.tar) Download the Readme for the Quartus II software version 10.0 SP1 Patch 1.133 (.txt) This problem is fixed beginning with the Quartus II software version 10.1.36Views0likes0CommentsClarification on Agilex 3 W vs Y Device Variants and Security Feature Mapping
Hi support team, I hope you are doing well. I am currently evaluating Agilex™ 3 devices for a design and would like to clarify the detailed differences between the W and Y device variants, particularly regarding their security capabilities. After reviewing several official documents, I found that the description is not entirely aligned, and I would appreciate your clarification with references to the official definitions. I have mainly referred to the following documents: Security Overview for SDM-Based FPGA Devices Agilex™ 3 FPGAs and SoCs C‑Series Product Table Agilex™ 3 FPGAs and SoCs Device Data Sheet Questions and points needing clarification In the Agilex 3 product table, the W/Y/Z variants are differentiated by a “C-r-y-p-t-o” field. Could you please clarify: What exactly is included in “C-r-y-p-t-o”? Does this explicitly include: ECDSA authentication SHA‑384 integrity verification Secure boot / authenticated configuration Or does it also include lower-level cryptographic primitives (AES, SHA engines, etc.)? 2, In the Security Overview document, it states that: SDM contains cryptographic engines (AES, SHA, ECC) and key management hardware, and these can also be accessed by user logic. From this description, it appears that: Cryptographic primitives exist in the platform (even for Y devices) So the question is: Are cryptographic engines available in both Y and W variants? If yes, is the difference that: W enables secure system-level usage (authentication / secure boot) while Y only exposes these engines for user application use? 3,From the product table and security overview: PUF SPDM attestation Physical anti‑tamper monitoring appear to be available beyond just W variants. Could you confirm: Are these features available on both Y and W devices? If so, what is the functional difference in how they are used? For example: Monitoring vs enforcement Reporting vs blocking 4,In the document: Security Overview for SDM-Based FPGA Devices Table 1 seems to indicate that Agilex 3 devices generally support both encryption and authentication, without distinguishing between W and Y variants. This creates confusion when compared with the product table. Could you please clarify: Is Table 1 describing platform-level capability (architecture-based) rather than specific device configurations? And is the correct interpretation that: Only W variants enable full cryptographic security flows (e.g. authenticated configuration / root-of-trust) while Y variants provide only partial or application-level capabilities? My design really care the security and low power consumption rather than performance or high speed tranceivers. we only nee 30KLE, 300Kbit RAM, 2 PLL,200GPIO, no tranceiver ,no high speed needed so smaller density A3CY025BB18AI7S of Agilex3 might suitable but security W is not available in that small density, so I would like to know if we choose Code Y then what security features is missing from W. Regard JL32Views1like1CommentIs there a way to detect whether the tamper bit has been programmed in a Stratix® II or Stratix® II GX device?
Description Yes, there is a way to detect whether the tamper bit has been programmed in a Stratix® II or Stratix II GX device. To do this, Intel provides a Jam file (SII_SIIGX_key_verify.jam) that you can run to show whether the tamper bit has been set or not. Resolution Download and run the SII_SIIGX_key_verify.jam file.136Views0likes0CommentsError-[SFCOR] Source file cannot be opened Source file "/…/…/…/quartus//eda/sim_lib/synopsys/ct1_hssi_atoms_ncrypt.sv" cannot be opened for reading due to 'No such file or directory'.
Description Due to a problem in the Intel® Quartus® Prime Pro Edition Software version 20.3 installation package for Linux OS, this error is reported during simulation when using the Synopsys VCS simulator. Resolution A patch is available to install the missing libraries for the Intel® Quartus® Prime Pro Edition Software version 20.3 in Linux OS. Download patch Intel® Quartus® Prime Pro Edition Software version 20.3 Patch 0.14 Linux (.run) Download the Readme for Intel® Quartus® Prime Pro Edition Software version 20.3 Patch 0.14 (.txt) This problem is fixed beginning with version 20.4 of the Intel® Quartus® Prime Pro Edition Software.Error: add_fileset_file: No such file C:/intelFPGA/20.1std/ip/altera/altera_nios2_gen2_rtl/cadence/altera_nios2_gen2_rtl_module.sv
Description Due to a problem in the Intel® Quartus® Prime Standard Edition Software v19.1, 20.1, and 20.1.1 for Windows operating system, you may see the above error message when you generate the RTL of a Platform Designer system that includes a Nios® II processor IP. Resolution A patch is available to fix this problem in the Intel® Quartus® Prime Standard Edition Software v20.1.1, upgrade your design to this version for patch compatibility. After upgrading your design, download and install Patch 0.01std from the following links: Intel® Quartus® Prime Standard Edition 20.1.1 Patch 1.01std for Windows (.exe) Readme for Intel® Quartus® Prime Standard Edition 20.1.1 Patch 1.01std (.txt) This problem is fixed starting with the Intel® Quartus® Prime Standard Edition Software v21.1.
Featured Places
Community Resources
Check out the support articles on personalizing your community account, contributing to the community, and providing community feedback directly to the admin team!Tags
- troubleshooting10,393 Topics
- fpga dev tools quartus® prime software pro4,290 Topics
- FPGA Dev Tools Quartus II Software3,160 Topics
- stratix® 10 fpgas and socs1,547 Topics
- agilex® 7 fpgas and socs1,489 Topics
- arria® 10 fpgas and socs1,380 Topics
- stratix® v fpgas1,319 Topics
- arria® v fpgas and socs1,232 Topics
- cyclone® v fpgas and socs1,059 Topics
- Configuration1,020 Topics
Recent Blogs
Agilex® 5 and Agilex® 3 FPGAs now provide native MIPI D-PHY support for CSI-2 camera and DSI display interfaces, making it easier to bring sensor and display data directly into FPGA fabric for real-time processing, aggregation, adaptation, and transport. The blog highlights how scalable MIPI bandwidth, multi-interface connectivity, and integration with the Altera Video Solutions Stack enable high-performance vision, robotics, medical imaging, edge AI, and display systems while simplifying the path from image capture to processing and AI workflows.
12 days ago0likes
The Nios® V/c compact microcontroller is the third and the latest addition to the Nios V soft processor family and is supported in Intel® Agilex®, Intel® Stratix® 10, Intel® Arria® 10, and Intel® Cyclone® 10 GX FPGAs and SoCs. With the Nios V processor, you can easily create a processor and peripheral system using the traditional hardware tool flows like Intel® Quartus® Prime Software and Platform Designer as needed for your production solution.
13 days ago0likes
2 MIN READ
Altera is extending the availability of its Agilex®, MAX® 10, and Cyclone® V FPGA families through 2045 to support long-lifecycle applications like industrial, aerospace, and medical systems. This helps customers avoid costly redesigns and ensures reliable, long-term supply, reinforcing Altera as a trusted partner for decades-long deployments.
22 days ago2likes
To help address these challenges, Altera® is expanding the Agilex® 9 Direct RF-Series FPGA portfolio with the addition of the AGRW039, a new maximum-compute wideband device designed for demanding aerospace and defense RF applications.
22 days ago0likes
4 MIN READ
Runtime flexibility is only valuable when it is reliable High-speed systems are being asked to do more with the same hardware. A data-center platform may need to operate as a single 400G Ethernet link in one deployment, then support multiple 100G links in another. A front-haul or edge system may need to adapt to different rates, protocol roles, or customer configurations over the life of the product. The promise is simple: deploy one platform, then adapt it as requirements change. But in high-speed design, changing a configuration is not the hardest part. Changing it correctly is. A live transition is not just a speed change. It can require coordinated updates across the the various networking layers, along with clocking, lane mapping, reset behavior, and link recovery. If those layers do not move together and in the right order, the result can be an unstable link, silent data corruption, or a system that hangs indefinitely waiting for CDR lock. That is the real value of Altera Dynamic Reconfiguration: it gives designers confidence that runtime transitions are clean, verified, and repeatable. The Altera difference: clean, verified transitions Altera Dynamic Reconfiguration is built around a profile-driven, silicon-aware flow. Designers define the target operating modes in Quartus Prime, and the system generates validated profiles for each supported state. At runtime, the Dynamic Reconfiguration Controller applies the selected profile through a managed, hardware-driven sequence. It orchestrates the transition across the full protocol stack, ensuring MAC, FEC, PCS, and PMA layers are updated in a coordinated and deterministic order, rather than leaving the designer to manually manage each step. The result: clean, verified transitions - no partial configurations, no unsequenced resets, and no user-managed state machines to debug at 2 a.m. This matters because the transition itself is often where risk appears. A system may appear to support multiple modes on paper, but if each layer must be independently controlled, reset, and validated by user logic, the design team carries the burden of proving that every edge case works under real operating conditions. Altera reduces that risk by turning reconfiguration into a controlled system operation. The selected profile is known, and the transition is repeatable. Silicon-driven confidence The assurance comes from the architecture. Agilex devices use hardened transceiver and protocol IP designed for high-speed operation. Rather than treating reconfiguration as a collection of ad hoc register writes, Altera Dynamic Reconfiguration works with hardened IP and validated profiles to help ensure that runtime switching happens in a controlled, silicon-driven way. That silicon foundation is especially important at 100G and 400G data rates, where small sequencing mistakes can lead to difficult debug cycles. When designers hand-craft transceiver reset state machines, getting the order right, the timing right, and the edge cases right can take weeks. With Altera, those critical sequencing responsibilities are built into the reconfiguration flow. The benefit is not just ease of use. Ease of use is a result. The primary benefit is trust: designers can enable live switching with greater confidence that the system will move from one valid state to another without glitches. A practical advantage for real systems In real deployments, flexibility has business value only if it does not create operational risk. Altera Dynamic Reconfiguration helps a single hardware platform support multiple configurations while avoiding the disruption of a full FPGA reprogramming cycle or duplicate hardware paths for every possible mode. For networking platforms, this can mean supporting different Ethernet configurations on the same physical transceiver resources. For multi-protocol systems, it can mean adapting a port role as requirements evolve. For platform owners, it means more deployment options from the same hardware design. This is where Altera has a practical positioning advantage: customers get runtime flexibility with more of the critical transition behavior handled by the platform. Instead of asking designers to manually manage every reconfiguration step, Altera provides a structured flow designed to produce predictable, verified results. What the demo proves The Agilex 7 400G Dynamic Reconfiguration demo turns this story into proof. In the demo, two Agilex 7 FPGA boards are connected over QSFP-DD, and the system dynamically switches between a 400G Ethernet configuration and multiple 100G Ethernet links using the same setup. The demonstration shows more than a mode change. It shows live traffic validation, link status, packet counters, error status, and FEC behavior during the transition. That is the point: the feature is not theoretical. It is running on silicon, switching in real time, and validating the kind of clean transition designers need before they trust the feature in production systems. Why this matters now As data-center, telecom, edge, and industrial systems become more configurable, customers increasingly need hardware platforms that can support multiple roles over time. The question is no longer whether a system can support more than one mode. The question is whether it can switch modes cleanly, predictably, and with confidence. Altera Dynamic Reconfiguration is designed for that moment. It combines hardened IP performance, profile-driven control, and coordinated sequencing to deliver runtime flexibility without compromising reliability. Dynamic reconfiguration is valuable because it enables flexibility. Altera makes it compelling because it makes that flexibility trustworthy. Watch the Runtime Reconfiguration You Can Trust demo video
1 month ago1like