Recent Content
AXE5-Falcon using the J8/J9 MIPI connectors?
Is there a MIPI reference design or other public available design for the AXE5-Falcon using the J8/J9 MIPI connectors? I keep getting RZQ_GROUP type of errors whenever I use the B2A differential ref clock and the DP58/RZQ_B_2A pin.Solved37Views0likes4CommentsUnable to configure new license server
I am struggling to get our Quartus license to work on a new server. We had to replace the old server as the operating system is going out of support. A new license file has been requested and recievd which matches the mac address of the new server In the license file it references alterad and mgcld. If i install the flexLM version of the license manager then alterad is present but mgcld is not. I have tried commenting that line out - still doesn't work. If I change the license manager type and install the siemens one, that has no alterad and my understanding is that I should be changing the license file to use saltd instead of mgcld - I have done that, it still doesn't work. I guess I must be doing something wrong. I have setup numerous flexlm and other types of license servers and do not usually encounter many issues but this is really causing us problems. Do you have anywhere that will guide me through what I need to do stet by step? The documentation in the link from the license file (https://docs.altera.com/r/docs/683472/25.3/altera-fpga-software-installation-and-licensing/setting-up-a-license-file-in-the-license-server) suggests that the license manager should have both alterad and saltd executables, but as i say, neither flex or siemens license managers install both. I havr tried installing both license managers and referencing alterad and mgcld in their respective loctions but that did not work Also - I just tried to get a new lic file to see if it would then ref the correct exes for either of the lic managers and I have just been emailed no less than 5 license files, Unsure what they are all for? This is the error message when I attempt to start the server lmgrd is not running: Cannot connect to license server system. The license server manager (lmgrd) has not been started yet, the wrong port@host or license file is being used, or the port or hostname in the license has been changed234Views0likes10CommentsQuesta FPGA Starter Edition – License file missing FEATURE/INCREMENT lines
Hello Altera Support Team, I am a university student experiencing a license generation issue with Questa FPGA Starter Edition (SW-QUESTA). I successfully registered in the Self-Service Licensing Center (SSLC) and generated a free Fixed Node license for my computer. However, the generated .dat file contains only comment lines in the FEATURE section: # FEATURE START # This is license file for Questasim*-FPGA Starter Edition # Number of seat licenses is 1 # License Expires 20-Oct-2027 # FEATURE END There are no active FEATURE or INCREMENT lines in the license file. When I try to launch Questa Intel FPGA Starter Edition 22.1, I receive the following error: "Unable to checkout a license. Make sure your license file environment variable (e.g., LM_LICENSE_FILE) is set correctly." Troubleshooting already performed: Verified that the LM_LICENSE_FILE environment variable points to the correct .dat file. Confirmed that Windows can locate the file. Regenerated the license through SSLC using the same registered computer. Verified that the newly generated license file has the same missing FEATURE/INCREMENT lines. The license request was processed successfully, but the generated files do not contain usable license features. Could you please confirm whether this is an issue with the SSLC license generation system and advise how I can obtain a valid Questa FPGA Starter Edition license file? Thank you for your assistance.54Views0likes2CommentsGenerating Free License "not working"
Hello, Last Friday 16/10/2026, I had installed Quartus Prime Lite Edition 25.1, and generating license wasnt an issue for me via the website altera.com/sslc since that day due to having day by day of license expired... . However, today when I tried to generate a new license to download, I noticed the difference of the license causing my license not working in Quartus Prime which happen that I cant simulate University Program VWF today. Old license.dat : New license.dat:41Views0likes2CommentsCompiling 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?5Views0likes1CommentThree 9x9 multipliers in one DSP
Hello everyone, Do have somebody the project example with three 9x9 multipliers in one DSP looks like in this post: How to configure DSP block in "three 9x9 multipliers" mode? | Altera Community - 90399 I tired to do this project and I have got one mult. per DSP.67Views0likes3CommentsHyperRAM Hyperbus options for Agilex
In migrating a Xilinx design : We are looking to use a A5E A 007 B23B device with a NIOS-V or other RISCV soft core. Because we need to use the HSIO pins for ~ 20 pairs of LVDS, and the entireHSIO bank (96 wide) having to be at 1.3V to support LVDS mean that we cannot use the internal LPDDR4 memory controller. Please confirm my understanding - that although the 96 wide I/O bank can be split into two functional sub banks (2A, 2B etc) (to support say, LPDDR4(16 bit), and something else , that we CANNOT split the VCCIO-BANK between the two sub banks ? (to have 1.1V for LPDDR4 and 1.3V for LVDS) The projects do not need much memory- a 64 Mbit HyperRAM device hanging from 1.8V HVIO would do the job (perhaps max clock 125 MHz on HVIO ?) What instantiable cores do ALtera have in the war chest for HyperRAM? There is a 3rd party Hyperbus controller IP but we wont want to spend $10,000 on it, as moving from a cheaper Xilinx device to a less competitive Altera device is already a big job and we do not think it deserves having that much more money spent on it. (Efinix have a free Hyperbus core, Xilinx have a free Hyperbus core....) Regards Glen.Solved155Views0likes5CommentsHow to organize a shared cache for qsys systems?
I have written a system to generate command lines and scripts/templates for various EDA tools. This will let me share the same same design across different implementations. The designs typically reside in a git (or some other VC) repository. For Altera IP's only the *.ip is kept in the git repository. The cache tag is generated from a hash of the content of the *.ip and the Quartus version used as this uniquely defines a single *.ip file. The build script will copy the '*.ip' file and run qsys-generate in the $cache/$tag location which will be added to the IP_FILE in the tcl build script. The next time the same Quartus version and same *.ip file is used it's referenced by the IP_FILE variable. This works pretty well. Putting the *.qsys itself into a similar structure works too. But distributing the *.ip and *.qsys children of the parent.qsys in the same cache seem to be problematic as the parent.qsys logicalView XML tag seem to contain a partial relative sub-path. Is there a way to make sure that only references to the child.ip or child.qsys will be present in the parent.qsys so that it can be located by the full absolute path specified in the IP_FILE? Also how are *_hw.tcl files located and what type of references and relations between these and their respective *.ip and/or *.qsys files are stored in these files? Or is the only solution to copy the full tree structure of the qsys into the cache and hash its full content? BTW I'm using Linux only.124Views0likes3CommentsUSB Blaster III and Cyclone III
ai_responder Hi, Cyclone III is supposed to be supported by USB Blaster III. I was wondering which Quartus version would be needed? Last Quartus version for Cyclone III is 13,1 as far as I know. Is USB Blaster III working with 13.1? best regards BenSolved137Views0likes8CommentsQuesta Prime Pro 25.3 license rehosting
Hello, I need to get a license rehosting for our Questa Prime Pro license as it is a fixed license to a machine that will no longer be in use at our company. I worked with Intel Customer Support last year on generating the license and was told they could do the rehost for us if we need it in the future but since everything has migrated to Altera including the license generation, could someone please help. Thanks.10Views0likes1Comment
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,407 Topics
- fpga dev tools quartus® prime software pro4,357 Topics
- FPGA Dev Tools Quartus II Software3,131 Topics
- stratix® 10 fpgas and socs1,553 Topics
- agilex® 7 fpgas and socs1,547 Topics
- arria® 10 fpgas and socs1,382 Topics
- stratix® v fpgas1,315 Topics
- arria® v fpgas and socs1,229 Topics
- Configuration1,094 Topics
- cyclone® v fpgas and socs1,058 Topics
Recent Blogs
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.
22 days 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
22 days 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.
29 days ago0likes
As AI, cloud, and high-performance computing systems continue to scale, data center operators need more bandwidth within increasingly constrained power and thermal envelopes. Linear Pluggable Optics (LPO) offers an important path forward by simplifying optical modules, reducing power consumption, and lowering latency. LPO places signal-conditioning responsibilities in the host device, allowing the optical module to operate without the DSP used in traditional retimed optics. This architecture can reduce optical module power by 30% to 40%, helping data center designers increase connectivity density while simplifying cooling and thermal management. Altera Brings LPO to the FPGA Market Altera is the first FPGA provider to publicly demonstrate Linear Pluggable Optics interoperability using production FPGA devices. Continued validation with LPO modules from Amphenol and FS further demonstrates the breadth of the emerging ecosystem supported by Altera. Agilex® 7 FPGAs and SoCs bring the power and latency advantages of LPO to programmable platforms used in SmartNICs, data processing units, AI accelerators, and custom infrastructure. The initial public demonstration established that Agilex 7 devices could successfully interoperate with 400G LPO modules. The latest validation advances that milestone by confirming that the implementation meets the performance requirements expected for deployment in demanding data center environments. Validated for Real Deployment Conditions Comprehensive testing confirms that Agilex 7 F-Tile transceivers meet the electrical and link-performance requirements defined by the 100G-DR-LPO specification. The validation demonstrated: Compliance with the required transmit, receive, and link-performance criteria Successful interoperability with LPO modules from Amphenol and FS Successful LPO connectivity across distances from 1 meter to 500 meters Consistent performance across temperature and voltage conditions Measurable performance margin beyond required thresholds Testing covered demanding signal conditions, voltage variation, and temperatures ranging from minus 40 degrees Celsius to 105 degrees Celsius for electrical characterization. Functional link testing included a 1-meter LPO connection, a 100-meter active optical cable, and 500-meter LPO modules from Amphenol and FS. The results demonstrate robust, repeatable operation across multiple module suppliers and link distances, with measurable margin relative to the required performance limits. For customers, this validation provides confidence that Agilex® 7 support for LPO is ready for real-world deployment. Following the industry’s first public FPGA interoperability demonstration, the solution has now been evaluated against LPO performance requirements using modules from multiple suppliers and over link distances up to 500 meters. Together, these results demonstrate a practical foundation for deploying LPO connectivity in next-generation data center systems. More Efficient Connectivity for AI and Cloud Infrastructure The value of LPO grows as data centers deploy more high-speed optical connections. Eliminating the DSP from each optical module can reduce power across thousands of links, simplify optical module design, ease thermal pressure at the front panel, and support lower-latency data movement. Agilex 7 FPGAs add programmability to this more efficient optical architecture. Customers can combine LPO connectivity with packet processing, acceleration, security, telemetry, and evolving protocol support on a single adaptable platform. This flexibility is especially valuable for AI clusters and cloud infrastructure, where workloads, network architectures, and connectivity standards continue to evolve. Validation with multiple module vendors also gives system designers greater flexibility as the LPO supplier ecosystem continues to develop. Ready for the Next Generation of Data Centers The combination of public interoperability and comprehensive validation marks a major step for LPO in the FPGA market. Altera has demonstrated that LPO works with production Agilex 7 devices and validated that the solution meets key LPO requirements with measurable operating margin. This gives customers a proven foundation for evaluating and deploying lower-power, lower-latency optical connectivity in real data center environments. With Agilex® 7 FPGAs, LPO is ready for real-world data center deployment.
2 months ago0likes
Security requirements are entering a new phase. Systems being designed today may remain deployed for many years, while regulatory expectations, cryptographic standards, and threat models continue to evolve. For designs in industrial, communications, infrastructure, aerospace, defense, and embedded applications, long-term security is becoming a core platform requirement. FPGA-based designs allow designs to meet today’s security needs and evolve with tomorrow’s requirements. Altera is now offering Agilex® 3 and Agilex® 5 devices with PQC-enabled secure boot and configuration support, helping customers prepare for the next generation of security requirements. With the Quartus® Prime Pro Edition 26.1.1 release, customers can begin using a PQC flow that works with Agilex 3 and Agilex 5 based hardware. This milestone extends the security architecture already built into the Agilex platform. Agilex devices use the Secure Device Manager as a hardware root of trust for secure configuration and device management. By combining PQC-capable devices with Quartus software enablement, Altera is helping customers strengthen the FPGA chain of trust as post-quantum requirements move from planning to implementation. The value is immediate and practical. Customers can start designing with supported devices today, while using Quartus 26.1.1 to take advantage of the current software flow. This gives teams a path to address emerging compliance and security expectations without needing a future platform redesign. The same hardware foundation also allows for additional security enhancements over time. Customers designing with PQC-capable Agilex 3 and Agilex 5 devices can benefit from planned software and firmware improvements enabled by the underlying hardware, with no further FPGA hardware upgrade required for those enhancements. Agilex 3 devices bring this capability to power- and cost-optimized FPGA and SoC designs used in embedded, edge, industrial, control, and platform-management applications. Agilex 5 devices extend the same security direction into mid-range FPGA and SoC designs that require higher performance, greater integration, and broader system capability. Post-quantum readiness will continue to advance, and Altera is building that evolution into the Agilex platform roadmap. With PQC-capable Agilex 3 and Agilex 5 devices and Quartus 26.1.1 software enablement, customers have a practical starting point today and a scalable foundation for future security enhancements.
2 months ago0likes