Recent Content
ModelSim and Questa Starter Ed.
Hi all, The PC I currently use for FPGA development has both Quartus II 13.1 and Quartus 25.1 Std installed. Has it been verified that using Questa Starter Edition will not interfere with the existing FlexNet license environment for ModelSim? Now Questa Starter licenced by file fron SSLC, and Windows envisonment valiable SALT_LICENSE_SERVER=***_License.dat And alongside installed ModelSim use ordinary FlexNet Licencing LM_LICENSE_FILE=<<< local license servers >>>> I am asking this question because, while I was attempting to resolve the ModelSim license error mentioned below, my local administrator requested that I verify whether installing Questa Starter might affect ModelSim license management. Quatus 13.1 ModelSim license failureCompiling quartus design of PCIe root port example failing in WSL2
I am trying to follow the instruction for the PCIe root port example design (https://altera-fpga.github.io/rel-25.1/embedded-designs/agilex-5/e-series/premium/pcie_rp/ug-pcie_rp-agx5e-premium/). I am able to compile the design for the branch rel/26.1 in my native windows install of Quartus (version 26.1), using ```powershell git clone -b rel/26.1 https://github.com/altera-fpga/agilex5-ed-pcie-rp.git cd .\agilex5-ed-pcie-rp\src\hw\a5e065bb32aea_mdk\syn\g4x4 C:\path\to\quartus_sh --flow compile top ``` but trying the same command in WSL2 with the linux install of the same Quartus version, I get compilation errors ```bash git clone -b rel/26.1 https://github.com/altera-fpga/agilex5-ed-pcie-rp.git cd .\agilex5-ed-pcie-rp\src\hw\a5e065bb32aea_mdk\syn\g4x4 /path/to/quartus_sh --flow compile top ``` The errors I get: ``` Error (13785): VHDL Use Clause error at jtag_subsys.vhd(345): design library "hps_f2sdram" does not contain primary unit "hps_f2sdram" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 345 Error (13785): VHDL Use Clause error at jtag_subsys.vhd(347): design library "hps_m" does not contain primary unit "hps_m" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 347 Error (13785): VHDL Use Clause error at jtag_subsys.vhd(349): design library "jtag_subsys_address_span_extender_0" does not contain primary unit "jtag_subsys_address_span_extender_0" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 349 Error (13785): VHDL Use Clause error at jtag_subsys.vhd(351): design library "jtag_subsys_mm_ccb_0" does not contain primary unit "jtag_subsys_mm_ccb_0" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 351 Error (13827): Ignored construct jtag_subsys_altera_mm_interconnect_1920_pikpq3i at jtag_subsys_altera_mm_interconnect_1920_pikpq3i.v(175) due to previous errors File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/altera_mm_interconnect_1920/synth/jtag_subsys_altera_mm_interconnect_1920_pikpq3i.v Line: 175 Error (13785): VHDL Use Clause error at jtag_subsys.vhd(357): design library "altera_mm_interconnect_1920" does not contain primary unit "jtag_subsys_altera_mm_interconnect_1920_pikpq3i" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 357 Error (13827): Ignored construct jtag_subsys_altera_mm_interconnect_1920_d6b64fi at jtag_subsys_altera_mm_interconnect_1920_d6b64fi.v(173) due to previous errors File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/altera_mm_interconnect_1920/synth/jtag_subsys_altera_mm_interconnect_1920_d6b64fi.v Line: 173 Error (13785): VHDL Use Clause error at jtag_subsys.vhd(359): design library "altera_mm_interconnect_1920" does not contain primary unit "jtag_subsys_altera_mm_interconnect_1920_d6b64fi" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 359 Error (13827): Ignored construct altera_reset_controller at altera_reset_controller.v(364) due to previous errors File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/hps_subsys/ip/qsys_top/emif_io96b_hps/emif_io96b_hps_emif_io96b_hps_420_6c3i3ji/synth/ip/emif_io96b_hps_emif_io96b_hps_420_6c3i3ji/emif_io96b_hps_emif_io96b_hps_420_6c3i3ji_emif_0_ddr4comp/altera_reset_controller_1924/synth/altera_reset_controller.v Line: 364 Error (13785): VHDL Use Clause error at jtag_subsys.vhd(361): design library "altera_reset_controller_1924" does not contain primary unit "altera_reset_controller" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 361 Error (13785): VHDL Use Clause error at jtag_subsys.vhd(363): design library "altera_reset_controller_1924" does not contain primary unit "altera_reset_controller" File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 363 Error (13827): Ignored construct rtl at jtag_subsys.vhd(655) due to previous errors File: /home/krar01/git-clones/agilex5-ed-pcie-rp-unmodified/src/hw/a5e065bb32aea_mdk/src/g4x4/jtag_subsys/jtag_subsys/synth/jtag_subsys.vhd Line: 655 ``` Opening the jtab_subsys.qsys file in platform designer I also get warnings about missing .ip files, among the missing ip files is the hps_f2sdram.ip file, I get a feeling that warning is related somehow. I notice that in the windows native case the generated jtag_subsys file is generated as verilog, while in WSL it is a vhdl file. I do not why the same Quartus version and build numbers would fail in WSL while it succeeds in native windows. Is there anyone who may understand what the differences might be?70Views0likes3Comments[Arria 10 SoC] QSPI Flash GigaDevice Compatibility (GD55LB02GE / GD55LB02GF)
Hi Altera Community Support Team, We are currently using the Micron MT25QU02G as the primary QSPI boot device for our Arria 10 SoC (HPS) board. However, due to a severe unit price increase (nearly 20x), we are urgently looking for a cost-effective alternative QSPI Flash memory. During our search, we identified GigaDevice NOR Flash products as potential replacements. However, checking the "Supported Flash Devices for Arria 10 SoC Device" configuration page, GigaDevice is not listed under the Arria 10 SoC section, even though GigaDevice parts are mentioned as supported/compatible for several other FPGA/SoC device families. https://www.altera.com/developers/configuration I would like to ask the following questions: Arria 10 SoC Compatibility: Does the Arria 10 SoC HPS BootROM support booting from GigaDevice 2Gb 1.8V QSPI Flash devices? Since the BootROM operates using standard JEDEC SFDP and basic SPI opcodes, can we expect it to load the preloader/U-Boot SPL without issue? GD55LB02GE vs. GD55LB02GF: Our target part was initially the GD55LB02GE, but we found that it is becoming NR (Not Recommended) / NRND, and the newer generation revision GD55LB02GF is being recommended for new designs. Are both GD55LB02GE and GD55LB02GF supported as boot devices for Arria 10 SoC? Are there any known issues with JEDEC ID parsing or SFDP compatibility in U-Boot / HPS Flash Programmer for the newer F-revision? Programming Tooling: Will quartus_hps or the HPS Flash Programmer support flashing these GigaDevice parts directly, or would we need to handle programming via U-Boot / JTAG scripts? Any advice, official guidance, or experience regarding GigaDevice QSPI Flash migration on Arria 10 SoC would be greatly appreciated.2Views0likes1CommentWhy Generic Component are included in my GHRD?
Hi, Altera I am a Dist. FAE in Uniquest Korea. When building the Agilex 5 GHRD on a Linux OS, as you can see, the IPs are recognized as generic components. It would be great if an upgrade could fix this, but all the connections disappear and the design gets completely messed up. How do AEs deal with this goddamn situation? If the GHRD acts like this, there is no point for customers to use it as a reference design. Does anyone know a solution? I've tried copying the folders and creating new components, but I'm still just getting a bunch of red errors. Please let me know a solution.Are there any issues with the portability of Quartus designs?Sorry for bad languages.Thanks. HudsonSolvedDE10-Agilex: aocl diagnose fails with PCIe-to-fabric read error (0xffffffff)
## 1. Problem description We are experiencing an issue with our **Terasic DE10-Agilex board** when running the Intel FPGA SDK for OpenCL diagnostic. We have been following the **DE10-Agilex (revC) OpenCL BSP User Manual**, available on the [Terasic DE10-Agilex website](https://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=English&CategoryNo=142&No=1252&PartNo=4). After installing the required software, configuring the board, and setting up the PCIe driver, we execute: ```bash aocl diagnose ``` The OpenCL ICD check passes, but the board diagnostic fails with the following error: ```text Vendor: Terasic MMD INFO : [aclde10_agilex0] PCIe-to-fabric read test failed, read 0xffffffff after 1 attempts Failed Board name not available. DIAGNOSTIC_FAILED ``` **This is the issue we are trying to resolve. We have not been able to get `aocl diagnose` to pass.** Importantly, Linux successfully detects the FPGA through PCIe, and the corresponding kernel driver is loaded and bound to the device. The FPGA appears in `lspci` as: ```text 01:00.0 Processing accelerators [1200]: Altera Corporation Device [1172:35b4] (rev 01) Kernel driver in use: aclpci_de10_agilex Kernel modules: aclpci_de10_agilex_drv ``` The associated device node is also present: ```text /dev/aclde10_agilex0 ``` The PCIe memory BARs are allocated and enabled, and bus mastering is enabled. Therefore, the FPGA is recognized by the operating system, but the Terasic MMD fails when attempting to communicate with the FPGA fabric. ## 2. Hardware and software environment Our setup consists of: - **FPGA board:** Terasic DE10-Agilex - **Processor:** AMD Ryzen 9 7900X3D 12-Core Processor - **Motherboard:** MSI MPG B850 EDGE TI WIFI (MS-7E62) - **Operating system:** Ubuntu Linux - **Linux kernel:** `5.15.0-139-generic` - **FPGA software:** Intel Quartus Prime Pro 21.2 - **OpenCL software:** Intel FPGA SDK for OpenCL 21.2 - **OpenCL BSP:** Terasic `de10_agilex` - **Board configuration:** `B2E2_8GBx4` **Connection:** PCIe, with JTAG access through Quartus Programmer ## 3. Troubleshooting performed ### 3.1. PCIe detection and link verification We verified that the FPGA was detected through PCIe using: ```bash lspci -nn sudo lspci -vv -s 01:00.0 ``` The FPGA reported: ```text LnkCap: Speed 8GT/s, Width x16 LnkSta: Speed 2.5GT/s, Width x16 ``` The upstream PCIe port advertised a maximum speed of 2.5 GT/s, which could explain the negotiated Gen1 speed. The driver also reported an unsuccessful attempt to retrain the PCIe link to a higher generation. Despite the FPGA being detected and the driver being bound, `aocl diagnose` continued to fail with the PCIe-to-fabric read error. ### 3.2. Motherboard, PCIe connection, and BIOS configuration To investigate possible hardware compatibility or PCIe initialization problems, we performed several tests: - Removed and reinstalled the DE10-Agilex board multiple times. - Checked and reconnected the PCIe connection. - Replaced the original motherboard with the MSI MPG B850 EDGE TI WIFI (MS-7E62), selected for compatibility with the board's PCIe requirements. - Reviewed and modified the motherboard BIOS settings to meet the required PCIe configuration. - Repeated the PCIe detection and OpenCL diagnostic tests. These hardware and BIOS adjustments did not produce a successful `aocl diagnose` result. ### 3.3. Kernel driver verification We checked the DE10-Agilex kernel driver using: ```bash modinfo aclpci_de10_agilex_drv ``` The installed module was: ```text aclpci_de10_agilex_drv.ko ``` The module's kernel version information matched the running Linux kernel. We also verified that the driver was bound to the FPGA PCIe device and that the corresponding device node existed. Therefore, the original diagnostic failure occurred despite the kernel driver being installed and active. ### 3.4. OpenCL runtime and MMD configuration We inspected the OpenCL runtime configuration. The OpenCL ICD was configured to load: ```text libalteracl.so ``` The Terasic board configuration pointed to: ```text libterasic_agilex_mmd.so ``` The OpenCL ICD check passed during `aocl diagnose`. We also identified an older Cyclone V board configuration and disabled it to eliminate possible interference with the Terasic DE10-Agilex MMD. However, the diagnostic continued to report: ```text PCIe-to-fabric read test failed, read 0xffffffff after 1 attempts ``` ### 3.5. FPGA programming through JTAG We verified that the FPGA was accessible through JTAG using Quartus Programmer. The FPGA was detected with JTAG ID: ```text C341A0DD ``` We used the precompiled bring-up files provided with the Terasic DE10-Agilex BSP, including: ```text top.sof vector_add.aocx host ``` We successfully programmed the FPGA through JTAG using the supplied `top.sof`. However, the computer was rebooted immediately afterward, so we did not verify whether `aocl diagnose` passed while that JTAG-programmed image was still active. We would appreciate clarification on whether the programming and initialization procedure described in the manual is sufficient to ensure correct PCIe-to-fabric communication. ### 3.6. Precompiled OpenCL example We also attempted to run the precompiled vector-add example provided with the Terasic BSP. The example failed with: ```text CL_DEVICE_NOT_AVAILABLE ``` Additionally, `aocl list-devices` did not return a usable FPGA device. This is consistent with the failure reported by `aocl diagnose`, where the OpenCL runtime cannot successfully access the FPGA through the Terasic MMD. ## 4. Summary The main observations are: - Linux successfully enumerated the DE10-Agilex FPGA as PCIe device `1172:35b4`. - The `aclpci_de10_agilex` kernel driver was loaded and bound to the device. - The FPGA device node existed. - PCIe BARs were allocated and enabled. - The OpenCL ICD check passed. - The FPGA was accessible and programmable through JTAG. - We reseated the board multiple times, replaced the original motherboard, and adjusted BIOS settings for PCIe compatibility. - We verified the kernel driver and OpenCL runtime configuration. - The precompiled OpenCL vector-add example failed with `CL_DEVICE_NOT_AVAILABLE`. **Despite these checks and troubleshooting steps, `aocl diagnose` failed with:** ```text MMD INFO : [aclde10_agilex0] PCIe-to-fabric read test failed, read 0xffffffff after 1 attempts ``` We suspect that the issue may involve communication between the PCIe endpoint and the FPGA fabric, but we have not identified its root cause. ## 5. Questions for the Terasic / Intel Agilex community **1. PCIe-to-fabric read failure** What could cause the Terasic MMD to return `0xffffffff` during the PCIe-to-fabric read test when Linux successfully detects the FPGA, enables its PCIe memory resources, and binds the appropriate kernel driver? **2. FPGA configuration** Could this error indicate that the FPGA configuration does not contain the expected PCIe-to-fabric interface or that the interface has not been initialized correctly? Is there a specific FPGA configuration or initialization sequence required for `aocl diagnose` to pass? **3. Diagnostic procedures** Are there recommended tests, registers, driver logs, or debugging procedures to determine why the PCIe-to-fabric read fails? **4. Official bring-up procedure** We have followed the **DE10-Agilex (revC) OpenCL BSP User Manual** available on Terasic's website. Are there additional steps required to establish communication between the host and the FPGA fabric beyond the procedures described in this manual? **5. Software compatibility** Are there known issues involving Intel FPGA SDK for OpenCL 21.2, the Terasic DE10-Agilex BSP, or the PCIe kernel driver that could cause this diagnostic failure? Any guidance or recommended troubleshooting procedures would be greatly appreciated. Our objective is to successfully complete `aocl diagnose` and establish reliable OpenCL communication with the DE10-Agilex FPGA.2Views0likes1CommentAgilex® Defense-Grade FPGAs: Performance, Resilience, and Choice
2 MIN READ Aerospace, defense, and high reliability systems must deliver demanding processing performance while operating in environments where extreme temperatures and mechanical stress can compromise electronics. Developers must also plan for long service lives, supply continuity, and mission requirements that continue to evolve. Altera’s defense-grade Agilex® FPGA and SoC FPGA portfolio brings these priorities together. It combines scalable programmable performance with military-temperature and ruggedized packaging options, while U.S. wafer fabrication supports supply resilience. For system designers, that means more ways to balance performance, deployment conditions, and long-term program needs. Designed for harsh environments Defense-grade Agilex devices offer military-temperature options supporting operation from −55°C to +125°C, helping designers target extreme hot and cold environments in applications such as outdoor radar, vehicle-mounted communications, and airborne sensors. A wider specified temperature range can provide more thermal headroom and may reduce heating or cooling needed solely to keep a narrower-rated FPGA within its specified limits, easing size, weight, and power trade-offs. Ruggedized packaging options, including leaded-ball configurations, help address temperature cycling, vibration, and shock in mobile and deployed systems. For customers with tin-lead assembly requirements, leaded-ball options can also avoid a separate reballing step and its associated process-control and qualification burden. Addressing environmental durability and manufacturing compatibility early can reduce the risk of late-stage redesign. Together, these capabilities help designers bring Agilex FPGA performance into demanding mission environments with fewer thermal and manufacturing workarounds. Temperature grades and packaging options vary by device and configuration. Supply resilience for long-life platforms Aerospace and defense platforms often remain in service for many years, making continuity of supply an important consideration. Agilex FPGAs provide a domestic source of wafer fabrication that supports supply resilience and helps customers plan for long program lifecycles. Performance and choice across Hi-Rel applications Defense applications call for different combinations of performance, power efficiency, and integration. The Agilex portfolio spans low-power, cost-optimized Agilex 3 FPGAs, mid-range Agilex 5, high-performance Agilex 7, and Agilex 9 Direct RF-Series FPGAs. This range supports applications from embedded processing for industrial and automotive to high-bandwidth communications, radar, and electronic warfare. Altera’s HyperFlex® architecture supports higher clock frequencies and processing throughput through Hyper-Retiming and Hyper-Pipelining. Alongside FPGA programmability, these capabilities offer a flexible foundation as mission-critical systems integrate more sensing, processing, and AI within constrained platforms. Availability Initial shipments of defense-grade Agilex FPGAs are planned for the first quarter of 2027, with software support targeted for Quartus® Prime Design Software version 27.1. For more information about defense-grade device options, contact your local Altera sales representative.10Views0likes0Commentsneed for Agilex 5 utilization&performance support in Altera IP ?
Altera, please update the documentation - missing Agilex 5 IP support. Overall question- is it expected that users do all their work in DSP builder to generate performance and utilization, IE use DSP builder as a wrapper for all Altera DSP IP ? Example https://docs.altera.com/r/docs/683208/24.1/fir-ii-ip-user-guide/fir-ii-ip-core-performance-and-resource-utilization no numbers for Agilex 5, and preliminary support https://docs.altera.com/r/docs/683366/24.1/unified-fft-ips-user-guide/unified-fft-intel-fpga-ips-device-family-support support but no utilizatiion or performance numbers is it expected that users run {2.2. Generating a Unified FFT IP} generate the HDL in QUartus to get utilization ? But surely the fmax and utilizatiion will not be final until the synthesis and P&R tools have done their jobs ? https://docs.altera.com/r/docs/683374/17.1/fft-ip-core-user-guide/dsp-ip-core-device-family-support no support for Agilex 5 (old core?) regards, glen38Views0likes2Commentscurrently evaluating FPGA solutions
Dear Intel FPGA Team, Greetings from PARAS Defence and Space Technologies. We are currently evaluating FPGA solutions for our C-band SATCOM terminal project. Our key application requirements are as follows: RF frequency range: 4.4–4.95 GHz • Instantaneous RX bandwidth: 16 MHz • RF channels: 4 RX and 4 TX • Interface: JESD204B/C between the RF transceiver and FPGA • Application: Ground-based SATCOM terminal for tracking a moving aircraft We are considering the Intel Arria 10 FPGA family as a potential platform and have reviewed the available reference design for the ADRV9029 Sub-6 GHz evaluation board with Arria 10 FPGA. To clarify the technical feasibility and plan our development and procurement activities, we would like to arrange a meeting with your FPGA technical and sales teams to discuss the following topics. FPGA Selection and Compatibility Recommendation of a suitable Arria 10 or other Intel FPGA family and specific part number for our application, considering JESD interface requirements, FPGA resources, transceiver capabilities, and future scalability. ADRV9029 JESD204 Integration Confirmation of the supported JESD204B/C configurations, available transceiver lanes, achievable lane rates, and relevant FPGA IP requirements for interfacing with the ADRV9029. Reference Design and Porting Support Guidance on the available ADRV9029–Arria 10 reference design, required hardware platform, design files, software dependencies, and the feasibility of adapting the reference design to our intended FPGA platform. Development Tools and Technical Support Information on the required Intel Quartus Prime software edition, JESD204 IP licensing, simulation resources, design examples, and technical support available during FPGA development. Evaluation Hardware Recommendations for a suitable FPGA development kit or evaluation platform for initial ADRV9029 integration, including availability, compatibility, and procurement options. Product Presentation A technical presentation covering relevant FPGA families, high-speed transceiver capabilities, JESD204 interface solutions, design resources, and application examples suitable for RF and SATCOM systems. Procurement and Commercial Discussion Indicative pricing, product availability, lead times, development kit costs, and long-term supply considerations for prototype development and production. We would appreciate the opportunity to discuss these requirements with your technical specialists and sales representatives at a mutually convenient date and time. Please let us know your availability and whether any additional technical information is required from our side before the meeting. Thank you for your support. We look forward to your recommendations and to working with your team to identify a suitable FPGA solution for our project.
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,417 Topics
- fpga dev tools quartus® prime software pro4,370 Topics
- FPGA Dev Tools Quartus II Software3,131 Topics
- stratix® 10 fpgas and socs1,555 Topics
- agilex® 7 fpgas and socs1,552 Topics
- arria® 10 fpgas and socs1,384 Topics
- stratix® v fpgas1,316 Topics
- arria® v fpgas and socs1,230 Topics
- Configuration1,100 Topics
- cyclone® v fpgas and socs1,059 Topics
Recent Blogs
Aerospace, defense, and high reliability systems must deliver demanding processing performance while operating in environments where extreme temperatures and mechanical stress can compromise electronics. Developers must also plan for long service lives, supply continuity, and mission requirements that continue to evolve. Altera’s defense-grade Agilex® FPGA and SoC FPGA portfolio brings these priorities together. It combines scalable programmable performance with military-temperature and ruggedized packaging options, while U.S. wafer fabrication supports supply resilience. For system designers, that means more ways to balance performance, deployment conditions, and long-term program needs. Designed for harsh environments Defense-grade Agilex devices offer military-temperature options supporting operation from −55°C to +125°C, helping designers target extreme hot and cold environments in applications such as outdoor radar, vehicle-mounted communications, and airborne sensors. A wider specified temperature range can provide more thermal headroom and may reduce heating or cooling needed solely to keep a narrower-rated FPGA within its specified limits, easing size, weight, and power trade-offs. Ruggedized packaging options, including leaded-ball configurations, help address temperature cycling, vibration, and shock in mobile and deployed systems. For customers with tin-lead assembly requirements, leaded-ball options can also avoid a separate reballing step and its associated process-control and qualification burden. Addressing environmental durability and manufacturing compatibility early can reduce the risk of late-stage redesign. Together, these capabilities help designers bring Agilex FPGA performance into demanding mission environments with fewer thermal and manufacturing workarounds. Temperature grades and packaging options vary by device and configuration. Supply resilience for long-life platforms Aerospace and defense platforms often remain in service for many years, making continuity of supply an important consideration. Agilex FPGAs provide a domestic source of wafer fabrication that supports supply resilience and helps customers plan for long program lifecycles. Performance and choice across Hi-Rel applications Defense applications call for different combinations of performance, power efficiency, and integration. The Agilex portfolio spans low-power, cost-optimized Agilex 3 FPGAs, mid-range Agilex 5, high-performance Agilex 7, and Agilex 9 Direct RF-Series FPGAs. This range supports applications from embedded processing for industrial and automotive to high-bandwidth communications, radar, and electronic warfare. Altera’s HyperFlex® architecture supports higher clock frequencies and processing throughput through Hyper-Retiming and Hyper-Pipelining. Alongside FPGA programmability, these capabilities offer a flexible foundation as mission-critical systems integrate more sensing, processing, and AI within constrained platforms. Availability Initial shipments of defense-grade Agilex FPGAs are planned for the first quarter of 2027, with software support targeted for Quartus® Prime Design Software version 27.1. For more information about defense-grade device options, contact your local Altera sales representative.
9 hours ago0likes
Meet QuartusIQ Quartus® Prime (Pro Edition, 26.3) introduces the QuartusIQ AI Expert Companion, bringing FPGA expertise and project-aware AI assistance directly into your design workflow. Get guidance where you work, explore design decisions, and connect knowledge with hands-on tasks. Alongside new capabilities in system design, power analysis, and embedded development, QuartusIQ creates a more connected FPGA development experience. QuartusIQ: FPGA Expertise, Closer to Your Design QuartusIQ integrates AI assistance directly into the Quartus GUI, providing access to FPGA knowledge and project-aware guidance within your design environment. You can ask questions, explore design recommendations, and find relevant information without leaving Quartus. QuartusIQ connects to supported LLM providers using your own API key. Beyond general-purpose AI assistance, QuartusIQ combines FPGA-specific knowledge with project summaries to help make questions and recommendations more relevant to your design. Whether you're learning a new tool in Quartus, looking for documentation, or investigating approaches to design closure, this context can help you identify useful next steps. QuartusIQ also supports practical programming and configuration tasks. Analyze and convert programming files, discover connected hardware, and program devices through JTAG. Supports Secure Device Manager (SDM) commands, QSPI compatibility checks, and Remote System Update (RSU) image generation, extending these capabilities to additional device-configuration tasks. For teams exploring AI-assisted development beyond the Quartus GUI, Model Context Protocol (MCP) integration makes QuartusIQ expertise accessible to external AI workflows. And there is also an extension for Visual Studio Code that lets QuartusIQ work with GitHub Copilot. MCP integration and agent capabilities are available, providing additional ways to incorporate FPGA-specific knowledge and tools into connected development environments. Together, these capabilities make QuartusIQ a companion for finding information, understanding your project, and completing tasks, with recommendations you can review and apply to your design. Visual Designer Studio: Keep the System in View Visual Designer Studio (VDS) expands Platform Designer system import to include generic components and parameterized RTL, allowing more of your existing design to be incorporated into a visual workflow. Cross-probing between VDS and other Quartus applications makes it easier to navigate between the system-level view and related design information. Clock/reset fanout simplifies logical hierarchies. Improved separation of source and generated files makes revision control easier to manage. Expanded support for Arria 10, Cyclone 10 GX, and Stratix 10 devices provide greater design flexibility. Board awareness (beta) introduces board-package creation and use within VDS, adding board-level context to the system-design environment. Power & Thermal Analyzer: Streamline Power Analysis Workflows Power analysis is most valuable when it's integrated into the design process. With Tcl scripting and example scripts, Power & Thermal Analyzer makes it easier to automate analysis workflows, maintain consistency, and reassess power consumption as designs evolve. Several usability enhancements simplify working with device resources and analysis results. Device-aware resource filtering and controls help prevent invalid actions, while improved device selection, graphical displays, and numeric alignment make the interface easier to navigate. Common power-analysis reports are now available in the Report Database, providing access to power-analysis results within a familiar reporting environment. HPS is also modeled as a resource rather than a global setting, making its treatment more consistent with other design resources. Embedded Development: Expanded Platform Support and Design Examples Quartus Prime (Pro Edition, 26.3) expands embedded development support with the following: Initial Agilex® 27 SoC Hard Processor System (HPS) enablement, including Simics support and baseline hardware and software reference designs. For Agilex 5 E-Series devices, expanded FreeRTOS support includes Cortex-A76 symmetric multiprocessing (SMP) capabilities, along with the re-release of the bare-metal library. New Agilex 5 E-Series design examples help developers explore a wider range of embedded architectures. These include heterogeneous Linux and FreeRTOS operation using Bao static partitioning, cache-coherent accelerator examples for both operating systems, and Ubuntu and Docker-based Linux configurations. A new bare-metal "Hello World" example provides a simple starting point for development. Updated Nios V design examples include Triple-Speed Ethernet (TSE) designs with FreeRTOS TCP/IP and web-server functionality for Agilex 3 and Agilex 5 devices. Additional enhancements include initial Agilex 27 Nios enablement and soft-processor debug module improvements. Additional Productivity, DSP Builder Machine Learning, and Device Support Enhancements Node Finder improvements include a persistent top-level hierarchy, single-click navigation, and side-by-side search results, making it easier to explore a design while maintaining context. DSP Builder expands machine-learning capabilities with new CNN layers, expanded activation-function support, and AI Tensor DSP optimizations. Enhanced network import, quantization, and automatic sizing simplify implementation, while new demos and MATLAB/Simulink MCP-based agentic workflows support model creation, updates, and verification. Device enablement also expands for Agilex 5 E-Series and D-Series, including additional temperature-grade support for Agilex 5 D-Series devices. AI models with FPGA AI Suite FPGA AI Suite 26.3 expands the tools and capabilities available for developing and integrating AI workloads. Beta features include spatial compiler and developer APIs that enable customers to build CNN and transformer models with examples (ResNet-8, Qwen 3.5, Majika, GPT-neo), and configurable external memory interface (EMIF) connectivity. Additional updates include a new Altera Model Zoo, better integration with the Altera Video and Vision Processing, SoC/x86 profiling, and VDS examples. New production-quality design examples for Agilex 3 Memory-to-Memory designs. These additions provide more options for model exploration, data-path integration, and performance analysis. Explore Quartus Prime (Pro Edition, 26.3) From project-aware AI assistance to enhancements in system design, power analysis, embedded development, and AI workloads, Quartus Prime Pro 26.3 provides new capabilities for your FPGA projects. Visit the Quartus Prime Pro website to learn more. What's New in the Quartus® Prime (Pro Edition) Design Software Download the Quartus® Prime (Pro Edition) version 26.3 Software Learn more about QuartusIQ Read the QuartusIQ white paper Learn more about FPGA AI Suite software Agilex 3 FPGAs and SoCs overview Agilex 5 FPGAs and SoCs overview Agilex 7 FPGAs and SoCs overview
6 days ago0likes
PACKET CLASSIFICATION | FPGA | NETWORKING + SECURITY Every packet decision starts with classification. Routers, firewalls, SmartNICs, security gateways, and service-edge platforms must determine which policy applies before traffic can be forwarded, blocked, inspected, redirected, or prioritized. TCAM earned its place in these systems because it provides predictable lookup behavior and native ternary matching for ACL and LPM workloads. But as policy databases grow, search keys widen, and rules change more frequently, the traditional approach of scaling specialized ternary memory creates tougher tradeoffs in capacity, power, resource utilization, and system integration. Altera Stellar solutions takes a different approach. Instead of scaling packet classification by building ever-larger ternary-memory structures, Stellar turns classification into an optimized search problem that runs on configurable FPGA resources. The result is an FPGA-native path for large, dynamic packet-classification tables without giving up the policy semantics that made TCAM useful in the first place. TCAM scales through memory expansion. Stellar scales through search intelligence. Keep the TCAM semantics. Change the scaling model. Stellar preserves the intent of ACL, LPM, and multi-field classification, but changes how those rules are represented and searched. The Stellar Software Stack organizes policies into optimized graph structures, partitions the rule database, and continuously manages those search structures as the database evolves. The hardware then executes the search using configurable FPGA search engines while rule information is stored in conventional memory resources. Depending on the configuration, Stellar can use on-chip M20K memory, eSRAM, DDR, or HBM. That gives architects more freedom to balance throughput, capacity, latency, power, and FPGA resource use around the needs of the actual system. Use dense memory where it makes sense, and intelligence where it matters A traditional TCAM combines storage and comparison circuitry inside specialized ternary-memory arrays. That architecture delivers deterministic matching, but scaling the table means scaling the specialized comparison structure as well. Stellar separates rule storage from search execution. Ternary information can be represented as value-and-mask data in conventional memory, while graph organization and software-managed optimization direct each search toward the relevant parts of the database. As tables grow from thousands of entries toward hundreds of thousands or millions, this creates a different path for scaling capacity and power. The white paper goes deeper into why this matters, including the tradeoffs between TCAM and Stellar, the role of memory hierarchy, and a set of Stellar configurations spanning different key widths, capacities, memory resources, and projected five-tuple performance. Bring classification into the programmable datapath The value is bigger than the lookup engine itself. Stellar is designed to operate inside the FPGA alongside packet parsing, telemetry, encryption, traffic management, host-interface logic, and customer packet-processing RTL. For system architects, that means classification can become part of the same programmable platform already handling the datapath. A firewall can pair large, dynamic ACL processing with the rest of its traffic pipeline. A router can combine LPM and policy enforcement with programmable networking functions. A SmartNIC can integrate flow classification with offload and customer-specific acceleration. That system-level flexibility is especially relevant for 100GE to 400GE designs where classification must scale without consuming the platform that surrounds it. Read the full whitepaper! The full Altera white paper, Altera TCAM Alternative Solutions Scale Packet Classification to Millions of Rules for Networking Equipment, explains the architecture behind Stellar and the design choices that make it different. It covers TCAM fundamentals and scaling limits, Stellar graph-based search and software partitioning, memory-hierarchy options, configuration examples, quantitative architectural comparisons, dynamic updates, and deployment use cases across networking and security. Read the white paper See how Stellar uses search intelligence, configurable FPGA resources, and a flexible memory hierarchy to create a scalable alternative for large ACL and LPM workloads.
1 month ago0likes
4 MIN READ
September 28, 2026 The next generation of embedded systems will not be defined by compute alone. It will depend on how quickly, reliably, and intelligently systems can move data from the physical world into AI engines and turn insights back into action. That message came through clearly at Embedded World North America 2026, held September 22–24 at the Anaheim Convention Center. For Altera, the show provided an opportunity to highlight a growing collaboration with NVIDIA and demonstrate the role of FPGAs in high-performance edge AI architectures. Connecting sensors to AI with flexibility and determinism At the center of the story was NVIDIA Holoscan Sensor Bridge technology. The solution creates a high-bandwidth, low-latency path between real-world sensors and GPU-based AI processing, an increasingly important capability for robotics, industrial automation, intelligent video, medical systems, and other physical AI applications. FPGAs are well suited to this role because they can provide deterministic processing, flexible I/O, and protocol adaptation close to the sensor. Rather than forcing every application into the same hardware configuration, FPGA-based designs can be tailored to performance, connectivity, and latency requirements of a specific system. In the show’s keynote, NVIDIA Vice President Deepu Talla described the value of this flexibility: “You can select any of the Altera FPGAs depending on the application and pair them with any of the NVIDIA frameworks.” Altera’s post noted that Altera offers Holoscan Sensor Bridge solutions spanning 10G to 100G, where 25G and 100G offer significantly more bandwidth compared to other Holoscan ecosystem partners, helping developers scale connectivity for demanding edge workloads. The result is a practical sensor-to-compute architecture: Altera FPGAs handle the flexible, deterministic front end, while NVIDIA platforms provide the accelerated environment for AI and robotics workloads. An ecosystem approach to accelerating development The demonstrations also underscored that successful edge AI deployments require more than individual components. Developers need reference designs, production-ready boards, and partners that help bridge the gap between evaluation and deployment. Altera’s growing Holoscan ecosystem includes more than 10 reference designs and partner boards. These building blocks can help teams reduce integration effort and move faster from proof of concept to a real-time AI product. One example was on display at Altera partner Critical Link’s booth. Critical Link was recognized as a Best in Show Award winner in the AI & Machine Learning category at the show. Visitors to the booth could see a live demonstration of a 5-camera Holoscan Sensor Bridge solution, using Critical Link’s MitySOM-A5E as the featured Agilex® 5 FPGA hardware platform. The demonstration showed how an Agilex 5 FPGA-based system can help bring sensor data into an NVIDIA-powered AI pipeline while preserving the low-latency, high-bandwidth behavior required by edge applications. From 10G to 100G: Building the data plane for edge AI Altera’s Holoscan Sensor Bridge solutions are designed to make the sensor-to-GPU path faster and more adaptable. A recent Altera technical blog describes 10G, 25G, and 100G reference designs, including a 25G design on Agilex 5 SoC FPGAs for multi-camera sensor data flow and accelerated processing at the edge. In this architecture, the FPGA serves as the data plane: connecting to diverse sensors, aggregating streams, adapting protocols, and preprocessing data before it reaches the NVIDIA GPU. That division of labor helps reduce data-movement bottlenecks while preserving deterministic timing and giving developers room to evolve the system as sensor interfaces and AI workloads change. Altera Technical Holoscan blog for Robotics: Altera Pushes the Boundaries of Edge AI with New Holoscan Sensor Bridge Solutions | Altera Community - 355665 Watch the 25G Holoscan demo video: YouTube/Altera Why the sensor-to-compute path matters As AI moves into physical environments, system designers are balancing several competing requirements: Real-time response: Applications such as robotics and industrial inspection cannot always afford the delay of sending raw sensor data to a remote system. High-bandwidth data movement: Modern sensors generate increasingly rich data streams that must be transported without creating a bottleneck. Deterministic behavior: Safety-critical and industrial systems need predictable timing and consistent performance. Design flexibility: Product teams must support different sensors, interfaces, and deployment conditions without redesigning the entire platform. Faster development: Reference designs and ecosystem partnerships can shorten the path from concept to production. The Altera and NVIDIA approach addresses these needs by combining FPGA-based connectivity and processing with GPU-accelerated AI. It gives developers a modular foundation for building systems that can adapt as sensors, models, and application requirements evolve. Building what comes next at the edge The conversation at Embedded World North America 2026 pointed toward a broader shift in embedded design. Edge systems are becoming intelligent, connected, and increasingly autonomous, but their performance still depends on the data path that feeds them. By pairing Altera FPGAs with NVIDIA platforms and collaborating with partners such as Critical Link, developers gain more options for designing that path. The combination of flexible hardware, high-speed connectivity, and accelerated AI can help transform raw sensor input into timely decisions at the point where data is created. For teams developing the next generation of robotics, industrial automation, intelligent vision, and physical AI systems, this is the opportunity: Build a sensor-to-compute architecture that is fast enough for today’s workloads, flexible enough for tomorrow’s requirements, and ready to scale from demonstration to deployment. Learn more about Altera’s Physical AI-related Solutions: Holoscan: https://www.altera.com/fpga-solutions/sensory-interfaces Robotics: https://www.altera.com/fpga-solutions/robotics-solutions-stack Video: https://www.altera.com/fpga-solutions/video-solutions-stack
1 month ago0likes
1 MIN READ
Altera has begun shipping the new Agilex® 7 M-Series R31G multi-host acceleration package, giving customers a new way to build high-bandwidth systems that connect more hosts while moving more data through the network and memory subsystem. R31G is designed for architectures where data must move quickly between the network, memory, and multiple CPUs, GPUs, or other hosts. By bringing 800G or 2x400G Ethernet together with expanded PCIe 5.0/CXL host connectivity, the package opens new possibilities for AI NICs, storage acceleration, cloud acceleration, and other high-throughput platforms. What R31G enables More network bandwidth: 800G or 2x400G Ethernet capability for high-throughput data paths. More host connectivity: Two PCIe 5.0 x16 host interfaces, or up to four independent PCIe 5.0 x8 connections, with CXL support for flexible multi-host architectures. More memory bandwidth and I/O: DDR5-6400 and LPDDR5-6400 support, up to 204.8 GBps of memory bandwidth, and 768 GPIO in a compact 56 x 45 mm package. The result is a programmable platform that can connect, accelerate, and adapt as infrastructure requirements evolve, while keeping high-speed networking, host connectivity, and memory bandwidth tightly integrated. More network bandwidth. More hosts. More memory bandwidth. One programmable platform. Learn more in the Agilex® 7 M-Series product site.
1 month ago0likes