Recent Content
MaxV - Current Value
My customer is using MAX V CPLD. Part numbers are 5M1270ZF256C4N, 5M1270ZF324C5N. They have to interface 5V address and data lines of flash memory to these CPLDs. I studied datasheet, it is saying that we can interface 5V signal to Bank-3 IO pins if we use series resister plus internal I/O clamp diodes being enabled. I could not find acceptable current limit for clamp diode from datasheet. So that I can calculate resister value. Can you please provide max and nominal current limit value for internal IO clamp diode which can pass safely through it? Regards amolkumar17Views0likes2CommentsAbout floating voltage of the Agilex 3 power on reset
Hello, I am Naken, thank you for your support. I have created a board equipped with Agilex 3 and started debugging it recently. When checking the power pins during power-up, it appears that a floating voltage from the VCC system (0.75V) is entering the power system that supplies HVIO (3.3V). (I can send images individually if needed.) As described in the documentation, it mentions that due to floating voltage, VCCIO_PIO can be affected by VCCPT. 3.3. Floating Voltage • Power Management User Guide Agilex™ 3 FPGAs and SoCs • Altera Documentation and Resources Center Is it possible that the HVIO group experiences floating voltage due to the influence of the VCC system group? Best regards, Naken11Views0likes1CommentMultiple NIOS V Implementation
Hi, I was looking at the NIOS V Processor Reference Manual. I could not find the max instantiations you can implement on a FPGA. I see many designs online of Nios II Multiprocessors. Can I make the assumption that it is the same as the Nios II and you can implement multiple instantiations of NIOS V on the same FPGA, as long as the hardware logic space (alm), memory, etc can support the design. Lastly, is there any examples online for this? I see examples like https://www.intel.com/content/www/us/en/support/programmable/support-resources/design-examples/horizontal/exm-multi-nios2-hardware.html and https://www.intel.com/content/www/us/en/design-example/714531/cyclone-v-creating-multiprocessor-nios-ii-systems-design-example.html and https://www.youtube.com/watch?v=O54sJjSjq60 Thanks!Solved2KViews0likes10CommentsPin-Out File request A5EC028AB32AE3V (Agilex 5 E-Series, B32A package) [for Altera Employees Only]
Hi Altera team, I'm currently working on a new board design based on the Agilex 5 E-Series, specifically the A5EC028AB32AE3V in the B32A (32 × 32 mm VPBGA) package, using Quartus Prime Pro Edition. Quartus already recognizes this part number and lets me place pin assignments without any issue, but I couldn't find the matching Device Pin-Out File anywhere on the official pinouts page: 🔗 https://www.altera.com/design/devices/resources/pinouts Without that file, it's really hard to move forward, since I still need to finalize the PCB symbol, map the banks to their supplies correctly, and lock down the land pattern for the B32A package. Could someone from Altera kindly help me with the following? The official Pin-Out File (.pdf or .txt) for A5EC028AB32AE3V. The B32A package drawing along with the recommended PCB land pattern. A quick confirmation that the Agilex 5 Pin Connection Guidelines fully apply to this specific SKU. Just to clarify, we don't currently have active APS access on our side, which is why I was directed to reach out through the forum. Since this involves device-specific information, I'd prefer to continue the conversation privately. If an Altera AE could reply via private message on this thread, that would be much appreciated.14Views0likes1CommentJESD204B Multi-Link Implementation with AD9695 ADCs Having Different Lane Counts (L=4 and L=2)
Hello Intel Community, I am currently working on a multi-chip ADC design using the AD9695 with the JESD204B interface on an Intel Stratix 10 FPGA. I am using the JESD204B Intel FPGA IP core and have been referring to the example design provided with the IP. I have also followed the guidelines mentioned in Intel Application Note AN 804: Implementing Analog-to-Digital Converter Multi-Link Designs with Intel Stratix 10 JESD204B RX IP Core. In my design, I have three ADC chips with the following configuration: ADC 1: 4 lanes (L=4) ADC 2: 4 lanes (L=4) ADC 3: 2 lanes (L=2) All other JESD204B parameters (such as F, M, S, N, N') are identical across all three ADCs. According to AN 804, it is mentioned that when adding multiple subsequent links within a single JESD204B IP core, all links must share the same set of JESD parameters, including the number of lanes (L). Since my third ADC has a different lane count, I am unsure about the correct implementation approach. I would appreciate your guidance on the following: Can I integrate all three ADCs into a single JESD204B IP core instance by configuring it as a multi-link design, even though the lane counts differ? If not, should I instantiate three separate JESD204B IP cores, each configured as a single link (L=4, L=4, L=2 respectively)? Alternatively, should I instantiate two IP cores — one for the first two ADCs (with L=4, using the multi-link feature) and a second core for the third ADC (with L=2)? Could you please suggest the correct and most efficient path forward? Also, if I use separate IP cores, what are the key considerations for ensuring proper synchronization (Subclass 1) and reliable operation across all three links? Any insights, reference designs, or best practices would be greatly appreciated. Thank you in advance for your support. Best regards, BALAMURuGAN V19Views0likes3CommentsCyclone V SoC 5CSXC6 Series GXB Utilization and Limitations
Dear Intel Altera, I would like to confirm that the 6 channels GXB device: Q1) Do it possible to use all 6 TX / RX GXB Transceivers when Hard PCIe is used. Based on: CV-53004 There are no specific diagram to explains the single PCIe hard core device with only 6 channel case. Q2) Based on the document: CMU PLL will use CH5 and do this simply means there will be one extra for PCIe Hard-Core? Q3) If not understood falsely, Either PCIe X2 GEN1 + 4 custom GXB usage nor PCIe X4 GEN1 + 2 custom GXB usage is possible? And most protocol uses 1,2,4 and the only possible case is PCIe X4 GEN1 + 1 custom GXB? A little more info from CV-53002 So in order for PCIe Hard Core to run x2 or x4 CH4 must be used. As a result for custom TRX there is no way to use CH1 when PCIe is > x1? Thanks, BrianCyclone 10 GX Transceiver Power-Up Calibration Time (~353 ms) Analysis Request
We are observing a transceiver power-up calibration time of approximately 353 ms on a Cyclone 10 GX device (10CX220YF780I6G) using all 12 transceivers. The total system startup requirement is 250 ms (configuration + calibration + system boot constraints), and the calibration phase alone is currently a limiting factor. According to the Cyclone 10 GX Transceiver PHY User Guide, calibration is performed automatically during device configuration via the PreSICE engine and is dependent on reference clock stability, PLL lock conditions, and reset controller sequencing. The documentation does not specify a deterministic calibration duration. Please can you provide clarification on the following points: Is a ~353 ms calibration time expected behavior for a design using all 12 transceivers on this device family? Is transceiver calibration executed sequentially across multiple quads, or is full parallel calibration supported for all active transceiver banks in Cyclone 10 GX? Are there any recommended design practices (reset controller configuration, PLL topology, clocking architecture) that can reduce power-up calibration latency? Can calibration duration be significantly impacted by reference clock stabilization time or internal wait states prior to PreSICE execution? The goal is to determine whether the observed latency is inherent to the device architecture or if it can be optimized at system level.88Views0likes4CommentsQuesta Sim on Windows - linking to external LIB
I have been trying to use Questa (from Quartus Lite 21.1) on Windows to link to the Winsock2 library, without success. I have a minimal test case attached. I can't get it to load into the simulator. I compile with the command: vlog -sv -dpiheader dpiheader.h test.v test.c That succeeds. Then, I try to start the simulator using the command: vsim -c DPI_test That fails with an error: # ** Fatal: (vsim-3828) Could not link 'vsim_auto_compile.dll': cmd = 'D:/intelFPGA_lite/21.1/questa_fse\gcc-7.4.0-mingw64vc15\bin\g++.exe -shared -o "C:/Users/barralem/AppData/Local/Temp\barralem@BHI4TNR6H2_dpi_32868\win64_gcc-7.4.0\vsim_auto_compile.dll" C:/work/embedded/test/work\_dpi\auto_compile@\win64_gcc-7.4.0\test.o -Wl,-Bsymbolic -L"D:/intelFPGA_lite/21.1/questa_fse/win64" -lmtipli' # (vsim-50) A call to system(D:/intelFPGA_lite/21.1/questa_fse\gcc-7.4.0-mingw64vc15\bin\g++.exe -shared -o "C:/Users/barralem/AppData/Local/Temp\barralem@BHI4TNR6H2_dpi_32868\win64_gcc-7.4.0\vsim_auto_compile.dll" C:/work/embedded/test/work\_dpi\auto_compile@\win64_gcc-7.4.0\test.o -Wl,-Bsymbolic -L"D:/intelFPGA_lite/21.1/questa_fse/win64" -lmtipli) returned error code '1'. # No such file or directory. (errno = ENOENT) # I have tried removing the "#pragma comment(lib, "ws2_32.lib")" line, with no change. I have also tried specifying the library on the command line with -sclib. I have tried copying the LIB to the project directory, with no help.Solved3.1KViews0likes5Comments
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,388 Topics
- fpga dev tools quartus® prime software pro4,284 Topics
- FPGA Dev Tools Quartus II Software3,160 Topics
- stratix® 10 fpgas and socs1,544 Topics
- agilex® 7 fpgas and socs1,483 Topics
- arria® 10 fpgas and socs1,377 Topics
- stratix® v fpgas1,319 Topics
- arria® v fpgas and socs1,232 Topics
- cyclone® v fpgas and socs1,059 Topics
- Configuration1,026 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.
4 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.
5 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.
14 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.
14 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