Recent Content
SOLVED: BSP Editor NullPointerException on Debian 13 Linux
SOLVED: BSP Editor "New BSP" menu command is grayed out, so can't make any new BSP's, and opening any existing one from another computer throws: SEVERE: Available BSP type values for the --type argument are: [] SEVERE: BSP type "hal2" unknown. SEVERE: NullPointerException Based on other forum posts with a similar error, it seems like this is because the BSP Editor couldn't locate some of its own files. That seems likely here too since this is the first time it's used on this computer. But there's no problematic install path etc since I used the default. THERE ARE NO SPACES IN THE INSTALL PATH NOR THE PROJECT PATH. Everything else is working already for the Max 10: I can generate with Platform Designer, synthesize with Quartus, program SRAM with SignalTap, debug Nios V with RiscFree. Details are: Quartus Prime Lite 25.1std.0 Build 1129 10/21/2025 SC Lite Patches: None OS: Debian 13. This is what Ubuntu is based on, so it's very similar. And like I said everything else already works. USB came online already, not too hard. All it took was the Altera udev rules file 92 as usual, and the correct LD_LIBRARY_PATH so jtagd could find its own shared libs. Installed quartus into regular user account, not whole system, not as root. This is offered as an option in the installer if I recall correctly. Install path is the installer's default: /home/myuser/altera_lite/25.1std The project files are irrelevant here, since BSP Editor is already off-track as soon as it launches. "New BSP" is grayed out. SOLVED: BSP Editor is unable to find its own files without Altera's environment vars, which are provided when running inside niosv-shell. That's nonsensical to me, since any brain-dead program off the street can detect where its own binary loaded from, on any OS, and walk up the path from there to find the rest of its files, as a default if no env vars were provided. That's the first line of every binary or Tcl script I've ever written. Quartus main GUI seems to do it exactly that way. Anyone else struggling with this inexplicable rough edge should make sure your desktop's launcher icon invokes niosv-shell first, like this: altera_lite/25.1std/niosv/bin/niosv-shell --run altera_lite/25.1std/niosv/bin/niosv-bsp-editor To Altera: if you're struggling to maintain or improve your software because it relies on Tcl, contact me through my forum account. I could clean up a whole mess of rough edges like this one, and some other much-needed improvements.JESD204B RX Link Never Achieves CGS at 12.8 Gbps on S10 ES (1SG280LU3F50E3VGS1, Quartus Pro 17.1)
Hi Team, I am using the Intel JESD204B RX Example Design on a Stratix 10 GX Engineering Sample FPGA (1SG280LU3F50E3VGS1, L-Tile) with Quartus Prime Pro 17.1.I have two JESD204B configurations using the same board, RTL, and hardware. Case 1 (Working):ADC Clock = 1228.8 MHz, Decimation = 6 Lane Rate = 8.192 Gbps REFCLK (Core/XCVR) = 409.6 MHz Link/Frame Clock = 204.8 MHz SYSREF = 6.4 MHz This configuration works correctly and the JESD link comes up successfully. Case 2 (Not Working): ADC Clock = 1280 MHz Decimation = 4 Lane Rate = 12.8 Gbps REFCLK (Core/XCVR) = 640 MHz Link/Frame Clock = 320 MHz SYSREF = 5 MHz The JESD204B parameters are identical in both cases: L = 4 M = 8 F = 4 S = 1 N = 16 NP = 16 K = 32 Subclass 1 In the failing case, the following status is observed: Core PLL Locked = Yes ADC PLL Locked (Register 0x056F = 0x80) rx_is_lockedtodata = 0xF rx_ready = 0x0F rx_cal_busy = 0 rx_analogreset = 0 rx_digitalreset = 0 jesd204_rx_link_ready = 1 jesd204_rx_link_valid = 0 The Debug Link Buffer outputs are always zero: jesd204_rx_dlb_kchar_data = 0 jesd204_rx_dlb_data_valid = 0 jesd204_rx_dlb_data = 0 jesd204_rx_dlb_disperr = 0 jesd204_rx_dlb_errdetect = 0 Therefore, no CGS (/K28.5/) characters are detected and the link never progresses beyond this point. I have verified the following: ADC SPI configuration is correct.SYSREF is present on both ADC and FPGA.Register 0x0120 is written with 0x1C and correctly reads back 0x18 after SYSREF capture.Register 0x056E is configured correctly for the 12.8 Gbps lane rate.Register 0x0201 is set correctly for decimation by 4.REFCLK, Link Clock, and Frame Clock frequencies are correct.Native PHY calibration completes successfully.No Quartus warnings are reported.The Intel example design is used without RTL modifications.I also tried lane swapping and RX polarity inversion, but the result was unchanged.This 12.8 Gbps configuration has never worked even once since the beginning, whereas the 8.192 Gbps configuration works reliably on the same hardware. Could you please advise: Is there any known limitation or errata for Stratix 10 ES (1SG280LU3F50E3VGS1 L-Tile) at 12.8 Gbps?Is any additional Native PHY or transceiver configuration required for 640 MHz reference clock and 12.8 Gbps lane rate?Are there any known issues in Quartus Prime Pro 17.1 related to JESD204B RX at this operating point?Any suggestions on additional debug steps would be greatly appreciated.Cold Temperature Issue
Hallo, We used the Agilex5 device in AS configuration connect to external QSPI Flash. We apply Smart VID interface at the device demands. When we perform Cold power up at -40C the device is not configured, It seemed the device is not output from the POR, No traffic on the PMBus. Power sequence and voltage ramp time and levels are OK. Please advise Thanks Asaf218Views0likes24CommentsAgilex 5/3 FreeRTOS SMP Support
Stable Version: v25.4 Quartus Version: 25.4 Supported devices: Agilex™ 3 and Agilex™ 5 Source : https://github.com/Ignitarium-Technology/freertos-socfpga Branch/Tag: v25.4-SMP Release Date: March 30, 2026 Hello Everyone, FreeRTOS port for A55/A76 HPS now supports SMP. visit the GitHub page for instructions on how to get started. Features and comments Features Agilex3 Agilex5 Agilex3 SMP Agilex5 SMP (A55 x 2 or A76 x 2) Supported features Limitations/ Known issues A55 boot Yes Yes Yes Yes Single core boot, Dual core SMP A76 boot NA Yes NA Yes Single core boot, Dual core SMP QSPI boot Yes Yes Yes Yes SD boot Yes Yes Yes Yes eMMC boot Yes Yes Yes Yes NAND boot No No No No Clk mngr driver Yes Yes Yes Yes API to get clock speed of different blocks Reset mngr driver Yes Yes Yes Yes Peripheral reset assert/de-assert DMA driver Yes Yes Yes Yes Memory to memory transfer Only support memory to memory GPIO driver Yes Yes Yes Yes Write, read and interrupt support Timer driver Yes Yes Yes Yes User defined and free running modes UART driver Yes Yes Yes Yes Full duplex Tx and Rx DMA not supported (Planned for future release I2C driver Yes Yes Yes Yes Master mode write and read Standard and fast modes DMA not supported (Planned for future release I3C driver Yes Yes Yes Yes Master mode write and read i3c and legacy i2c devices IBI not supported (Planned for future release) SPI driver Yes Yes Yes Yes Master mode write and read DMA is not supported QSPI driver Yes Yes Yes Yes QSPI flash read/write/erase NAND driver No No No No SDM mailbox driver Yes Yes Yes Yes SDM commands with SIP_SVC SMMU enable support Yes Yes Yes Yes Static identity mapping for cache coherency SDMMC driver Yes Yes Yes Yes standard and HS speeds SDMMC and eMMC devices Fat FS support Ethernet stack Yes Yes Yes Yes TCP/IP, UDP, ICMP and DHCP IPv4 and IPv6 support USB 2.0 stack NT Yes NT Yes USB mass storage class Tested with a custom board and SOF USB 3.1 stack NT Yes NT Yes USB mass storage operation WDT diver Yes Yes Yes Yes interrupt or reset on timer expiry EDAC support Yes Yes Yes Yes Error injection and detection for EMAC, USB and QSPI blocks OCRAM not supported IOSSM driver Yes Yes Yes Yes Error injection and detection Bridge driver NT Yes NT Yes Enable, Disable Reboot mngr Yes Yes Yes Yes Warm/Cold reboot FPGA manager Yes Yes Yes Yes FPGA configuration Yes: Feature available and tested, No: Feature not available in SDK, NA : Not applicable , NT: Not tested Note: If you find any issues, please raise an issue in the GitHub page. For more support/assistance visit our website .Starting Quartus GUI fails in docker version
Hi, Recently I found out Quartus is available for docker. I started to test and compile process worked well on an existing design with 25.1 Standard Edition on both native SUSE Linux and WSL (SUSE as well). But when I wanted to start the GUI, I got back the following error (in both cases): /mnt/c/Windows/system32> docker run --net=host alterafpga/quartus-std:25.1std-all quartus *** Fatal Error: Segment Violation at (nil) Module: quartus Stack Trace: 0x289a2: abort + 0x182 (c.so.6) 0xae55a: QtPrivate::lcNativeInterface() [clone .cold] (Qt6Core.so.6) 0xaedc4: QMessageLogger::warning(char const*, ...) const (Qt6Core.so.6) 0xf9dc2: QGuiApplication::restoreOverrideCursor() [clone .cold] (Qt6Gui.so.6) 0x18e5a1: QGuiApplicationPrivate::createPlatformIntegration() + 0x641 (Qt6Gui.so.6) 0x18ef00: QGuiApplicationPrivate::createEventDispatcher() + 0x30 (Qt6Gui.so.6) 0x1461f5: QCoreApplicationPrivate::init() + 0xbe5 (Qt6Core.so.6) 0x1921b3: QGuiApplicationPrivate::init() + 0x33 (Qt6Gui.so.6) 0x18bc59: QApplicationPrivate::init() + 0x9 (Qt6Widgets.so.6) 0xb3899: AFCQ_APP::AFCQ_APP(int&, char**) + 0x13 (gcl_afcq) 0x6863a: QUI_APP::QUI_APP(int&, char**) + 0x1e (sys_qui) 0x14fb9: QGQ_APP::QGQ_APP(int&, char**) + 0x9 (sys_qgq) 0x38b8: qgq_main(int, char const**) + 0x48 (quartus) 0x3e540: msg_main_thread(void*) + 0x10 (ccl_msg) 0x5c1c: thr_final_wrapper + 0xc (ccl_thr) 0x3e60a: msg_thread_wrapper(void* (*)(void*), void*) + 0x6e (ccl_msg) 0xc046: mem_thread_wrapper(void* (*)(void*), void*) + 0x96 (ccl_mem) 0x9188: err_thread_wrapper(void* (*)(void*), void*) + 0x27 (ccl_err) 0x5c5f: thr_thread_wrapper + 0x15 (ccl_thr) 0x4050a: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xa8 (ccl_msg) 0x39d5: main + 0x26 (quartus) 0x2a28b: __libc_start_main + 0x8b (c.so.6) 0x37aa: _start + 0x2a (quartus) End-trace Is this a compatibility issue with my Linux version? Or do I make something wrong? Best regards, Istvan15Views0likes2CommentsModelSim-Intel FPGA Starter Edition 18.1 exits with code 211 when pressing Restart button
Hello, I am using ModelSim-Intel FPGA Starter Edition included with Quartus Prime Lite Edition 18.1. When I press the Restart button in the ModelSim GUI after running RTL simulation, ModelSim exits with the following message: "ModelSim is exiting with code 211. Check the transcript file for more information on the fatal error." Environment: - Quartus Prime Lite Edition 18.1 - ModelSim-Intel FPGA Starter Edition 18.1 - Windows PC - ModelSim path: C:\intelFPGA_lite\18.1\modelsim_ase\win32aloem 確認したこと: - Quartus / ModelSim は再インストールされました。 - 環境変数とPATH設定を確認しました。 - 同じプロジェクトが別のPCで正しく再起動できる場合。 - このPCではGUIの再起動ボタンを押すと問題が発生します。 - PCにはTrend Micro Apex Oneがインストールされています。 - リアルタイムスキャンからIntel FPGA / ModelSimフォルダを除外した後、ModelSimは正しく動作しました。 質問: GUIの再起動ボタンを使う場合、ModelSim-Intel FPGA Starter Edition 18.1で既知の問題として、終了コード211はありますか? また、この問題はウイルス対策ソフトやエンドポイントセキュリティソフトに関係している可能性はありますか? この問題に対するおすすめの設定や回避策はありますか? ありがとうございます。124Views0likes13CommentsImpedance measurement on power lines
We are using precision Multimeters in resistance mode and set them at manual 10K range for checking impedances on all power lines (versus ground) of our products. We established Ohm ranges for each power line of a product in order to know if the circuit looks ok before applying power. We have some products that have very sensible parts such as DDR3 memories with 0.75V±0.0375V powers and Altera FPGA with 0.9V±0.03V. By using another multimeter, we measure around 9V between the unconnected probes of different manufacturers precision multimeters set in such 10K range resistance mode. Even if the current is extremely small, we are worried that our sensible parts could be affected by this 9V “glitch”. What does Altera recommend for such measurement ? We are currently using alternative method like putting a Shunt resistor of 1K between the probes in order to keep the voltage near 0V. Of course all our range are now within 0 to 1K Ohm range and when our probes are unconnected, we always get 1.000K displayed. We can manage working with these low ranges. thanks15Views0likes2CommentsCyclone 10 GX AS x4 Configuration Compatibility with Infineon S25FS512S (Custom Flash Definition)
We are trying to use the Infineon S25FS512S QSPI NOR Flash with Cyclone 10 GX in Active Serial x4 (AS x4) configuration by creating a Custom Flash Definition based on AN229767. JTAG programming completes successfully, but FPGA configuration fails in AS x4 mode. We have performed extensive debugging and would like to understand whether this is a supported use case or if there are any known limitations. Observations Flash Programming JTAG programming completes successfully. Flash verification completes successfully. Configuration Behavior Active Serial x1 configuration works correctly. Active Serial x4 configuration fails. The FPGA successfully issues the RDID (0x9F) command. The FPGA then attempts to read the Boot Information from address 0x00000000. Logic Analyzer Observation During AS x4 configuration, the FPGA issues the EBh (Quad I/O Read) command. According to the Infineon S25FS512S datasheet, the expected transaction is: EBh → 4-byte Address → Mode Byte (8 bits) → Dummy Cycles → Data However, the captured waveform shows: EBh → 4-byte Address → Dummy Cycles → Data No Mode Byte is observed between the address and dummy cycles. Based on the S25FS512S command protocol, this could cause the flash to interpret the transaction differently and return misaligned data. We would like Altera to confirm whether this behavior is expected from the Cyclone 10 GX configuration controller. Additional Information We reviewed AN229767, but could not find any mechanism in the Custom Flash Definition to configure or insert the Mode Byte required by the EBh command. We also observed that the Custom Flash Definition supports Read Register commands only for fixed register opcodes and does not appear to support RDAR (0x65) with a register address. Questions Does the Cyclone 10 GX configuration controller support transmitting the mandatory Mode Byte required by the EBh (Quad I/O Read) command? If not, is this a known limitation of the Cyclone 10 GX configuration controller or Quartus Programmer? Is there any supported method to modify the Quad I/O Read command sequence in the Custom Flash Definition? Has Altera validated any Custom Flash Definition for the S25FS512S that can be shared as a reference? Environment FPGA: Cyclone 10 GX Flash: Infineon S25FS512S Configuration Mode: Active Serial x1 (working), Active Serial x4 (failing) Programming Method: Quartus Programmer using a Custom Flash Definition based on AN229767 We would appreciate any guidance, clarification, or a reference implementation for using the S25FS512S with Cyclone 10 GX in Active Serial x4 mode.10Views0likes1CommentCyclone IV drop in replacement confirmations
Dear Altera, If the BANK VCCIO is 1.8V and the same package but with different LE # FPGA is drop in replace. Where the original pin is a VCCA while different LE size same pin is a IO. With 1.8V on VCCIO and input fixed to VCCA aka 2.5V do this introduce any issue? As we can see the datasheet mentioned the DC input accept 3.6 or below. -> Table 1–4. Recommended Operating Conditions for Cyclone IV GX Devices (Part 2 of 2) So the C4 device have a protection forward diode to clamp the voltage when IO is set to input? As long as that pin is fixed to input state do this condition function properly? Thanks, Brian
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,344 Topics
- fpga dev tools quartus® prime software pro4,290 Topics
- FPGA Dev Tools Quartus II Software3,131 Topics
- stratix® 10 fpgas and socs1,540 Topics
- agilex® 7 fpgas and socs1,507 Topics
- arria® 10 fpgas and socs1,370 Topics
- stratix® v fpgas1,312 Topics
- arria® v fpgas and socs1,225 Topics
- cyclone® v fpgas and socs1,055 Topics
- Configuration1,043 Topics
Recent Blogs
A customer recently shared with me an interesting way they viewed the updated Altera brand: It’s like a long-time friend who had moved away for a few years but is now back and it’s time to get caught up. One of the things customers might want to 'catch up' on is Altera's efforts with regards to AI. It started when early FPGA products included the first basic digital signal processing (DSP) circuits within the FPGA fabric to improve performance for math-based logic, such as Fast Fourier transforms (FFTs) and finite impulse response (FIR) filters. These early enhancements improved general purpose FPGA-based computing but since 2015, our focus has shifted to improving AI capabilities in both silicon and software tools. DSP capabilities have gotten more sophisticated (fixed point, floating point, small and large bit precisions, etc.) and the quantity of available DSPs within a single device, have increased dramatically. Modern FPGAs are now capable of handling complex equations, especially those needed with the introduction of AI. This historical reminisce catches us up all the way until today’s news, where the latest Altera FPGA family is now broadly available to any customer who wants it; Agilex™ 5 SoC FPGAs, the first FPGAs infused with AI tensor blocks throughout the FPGA fabric. A short list of features that would be attractive to embedded or intelligent edge applications include: For those haven’t heard about Agilex™ 5 devices before today, here is how you can get started: Learn about the family. Review technical details. Download FPGA software. Free for anyone wanting access to Agilex™ 5 E-Series devices: Download Quartus® Prime Pro Test drive hardware (generally available now, lead-times may apply, via franchised distributors): Buy Altera development kits or 3rd party boards and SoMs The initial wave of board/SoM options include 9+ variants, with more coming. Evaluate AI or embedded options: Test out the FPGA AI Suite. Contact Altera sales for limited time introductory pricing. Utilize 3rd party tools (Arm DS, MathWorks) to design for the new, best-in-class Arm dual-A76 + dual-A55 based SoC subsystem or RISC-V based Nios® V soft IP processors. Altera is announcing the Agilex™ 5 family broad availability coincident with Embedded World 2024 because it is one of the key markets this mid-range FPGA family was architected for. Embedded customers clearly told us they perceive a lack of adequate compute in embedded processors, see a big need to fill security gaps, and want to add AI into their next generation systems. Agilex™ 5 devices can address all these concerns. Coming back to our initial topic, AI: GPUs are certainly a popular choice for AI training, but power consumption of GPUs for AI inferencing may be too high for intelligent edge or embedded applications. Instead of adding a separate GPU/AI semiconductor device to an embedded system (resulting in higher cost, more power, more thermal, etc.), why not add the AI function into an FPGA already planned to be used in embedded/edge equipment? For decades, FPGAs have been used in embedded/edge and communication systems for real-time control, IO connectivity, or image/data processing. The estimates on Agilex™ 5 device AI performance look good compared to equivalent class competitors. Because the FPGAs new DSP/tensor is implemented in a fine-grained architecture, it provides the FPGA designer the ability to tune for higher performance or lower power consumption, using the minimum amount of FPGA resources for the desired algorithm. Agilex™ 5 devices – AI key figures of merit: Tensor neural acceleration performance: Up to 26 / 56 TOPS ² Better performance per power efficiency versus embedded market inference GPUs. 1.7x higher frames per second per watt ³ Better raw performance versus other AI targeted FPGAs. 69% higher frames per second ⁴ There are many great reasons to look at this new family of FPGAs. If you are an architect, AI developer, or FPGA designer for embedded systems, don’t wait. As Mark Twain famously said, “The secret of getting ahead is getting started.” Don’t believe the marketing hype, try out your ideas in actual hardware, to see what is ‘possible’. Agilex™ 5 SoC FPGAs are just the latest phase in our DSP/AI journey. Altera, accelerating innovators. Come visit us at Embedded World 2024: Altera booth Hall 5, 5-135 and 5-136. Footnotes: Performance per watt: https://edc.intel.com/content/www/us/en/products/performance/benchmarks/agilex-fpga/ Theoretical peak INT8 calculations for the largest density Agilex 5 E-Series or D-Series devices. 1.7x higher frames per second per watt vs. Nvidia Jetson-class GPUs (AGX Orin) 69% higher frames per second vs. AMD/Xilinx Versal AI devices (VE2302)
19 hours ago0likes
As industries race to unlock real-time insights from massive volumes of sensor data, the need for high-performance, low-latency computing at the edge has never been greater. From medical imaging to industrial automation and autonomous robots, success depends on the seamless integration of data capture, processing, and AI-driven decision-making. That’s why Altera is proud to be an ecosystem partner of NVIDIA Holoscan, working together to enable a new class of accelerated computing platforms designed for sensor-rich, AI-powered applications. Leading the Way in High-Speed Connectivity Innovation at the edge starts with moving data fast and reliably. Altera is proud to offer the FPGA industry’s only 25G and 100G Holoscan Sensor Bridge designs, providing the high-bandwidth infrastructure needed to handle today’s most demanding Edge AI workloads. These high-speed interfaces are critical for: Streaming multiple high-resolution video or other high-bandwidth data streams Processing large radar, robotics, drone, or medical imaging datasets Enabling low-latency, deterministic decision-making in mission-critical environments “With Altera FPGAs driving these capabilities, developers can scale their applications confidently, knowing their systems won’t be bottlenecked by sensors and data movement pipelined via Holoscan Sensor Bridge into NVIDIA GPUs,” says Farhad Shafai, Altera, Head of Business Solutions and Vertical Marketing. Why Altera FPGAs + GPUs Are Better Together Modern intelligent systems require both flexibility and performance, which is why combining Altera FPGAs and GPUs is becoming the architecture of choice. Here’s how this powerful pairing works: FPGA Capability How It Enhances GPU-Based AI Sensor Connectivity and Data Ingestion FPGAs excel at interfacing directly with diverse sensors, handling custom protocols, and aggregating data streams efficiently. Ultra-Fast Processing With deterministic, low-latency performance, FPGAs can preprocess and filter data before it reaches the GPU, ensuring only the most relevant information is passed along. AI Acceleration FPGAs can be designed into your solution to pre-process and prepare your data for the most efficient AI processing by the GPU. Flexibility and Futureproofing FPGAs offer reconfigurability, allowing systems to adapt to evolving standards and algorithms without redesigning hardware. Enhanced Security With built-in hardware-level security features, FPGAs can encrypt sensor data directly at the source, helping ensure that sensitive information is protected from the edge to the compute/GPU, critical in industries like defense, and industrial automation. Together, Altera FPGAs and NVIDIA accelerated computing create an architecture that delivers both performance and adaptability, enabling developers to build smarter, faster, and more efficient systems. See It in Action: Altera’s 25G Demo on Agilex® 5 SoC FPGAs Want to see how high-speed connectivity and intelligent processing come together in real-world applications? Watch the demo: https://www.youtube.com/watch?v=ikmNKdOHbUU This demonstration highlights Altera’s latest 25G Holoscan Sensor Bridge design, enabling multi-camera sensor data flow and accelerated processing at the edge. Ready to Get Started? Developers can jump in quickly and start building with our 10G, 25G, and 100G reference designs at: Get started on GitHub https://github.com/altera-fpga/holoscan-sensor-bridge/tree/altera-release-2.6.0/fpga/altera Whether you’re building next-generation medical devices, robotics platforms, or AI-powered industrial systems, Altera and NVIDIA Holoscan provide the foundation you need to succeed. Learn More Explore Altera’s 10G – 100G Holoscan Sensor Bridge offerings at: http://www.altera.com/holoscan-sb
12 days ago1like
Smart cameras and embedded vision systems are being asked to do more at the edge. They need to capture higher-resolution video, process images in real time, support evolving sensors and interfaces, and prepare clean data for analytics or AI. At the same time, many of these systems are constrained by board area, system cost, power budgets, and long product lifecycles. That combination creates a familiar engineering challenge: how much of a real vision pipeline can be built in a device class optimized for lower logic density and cost? The Agilex® 3 4Kp30 Camera Lite reference design gives a compelling answer. It demonstrates a practical sensor-to-display camera pipeline built on Agilex 3, showing how a power- and cost-optimized FPGA can ingest a 4K image stream over MIPI CSI-2, process raw sensor data through an image signal processing pipeline, and output 4Kp30 video through DisplayPort 1.4. The reference design is a complete working vision pipeline that you can use to build your own based on your unique requirements. From sensor input to display output The reference design starts with a Raspberry Pi High Quality Camera module using the Sony IMX477 image sensor. The sensor outputs 12-bit raw Bayer data and connects to the FPGA through a MIPI CSI-2 interface. From there, the MIPI CSI-2 IP converts the incoming pixel stream into AXI4-Streaming data, making it available to the rest of the Altera® Video and Vision Processing (VVP) Suite pipeline. Inside the FPGA fabric, the design implements the major stages needed to turn raw sensor data into display-ready video. The ISP pipeline includes Black Level Correction, White Balance Correction, Demosaic, Color Correction Matrix, and a 1D LUT. The pipeline supports 12-bit raw data up to the Demosaic IP and 10-bit RGB for downstream video processing. The result is a fixed 3840 x 2160, 30 Hz video path from camera input to display output. That matters because many real products need more than a way to receive camera data. They need image correction, color processing, buffering, video formatting, display output, and software control. Agilex 3 brings those pieces together in a reference design that engineers can study, run, and adapt. A practical foundation for smart camera products For security cameras, industrial vision, smart infrastructure, robotics, retail analytics, and access control, the camera pipeline is often the first major design decision. The system must bring pixels in from the sensor, correct and format them, keep timing deterministic, and deliver data to the next stage of the product. In many cases, that next stage may be a display path, a host processor, a networking subsystem, a storage path, or an AI analytics engine. The Agilex 3 reference design is valuable because it gives developers a working foundation for that pipeline. It demonstrates the sensor input, image-processing path, video frame buffer, output mixer, and DisplayPort output using Altera IP. Developers can use it as a starting point, then adapt the pipeline for their own sensor choice, image-processing requirements, overlay needs, output path, or product-specific differentiation. In the current reference design, the video frame buffer is used for video synchronization. This is a practical detail worth highlighting because real video designs often need buffering for timing alignment, rate matching, format conversion, or system-level processing. The design uses external LPDDR SDRAM through an external memory interface for that frame buffer. More broadly, Agilex 3 SoC devices also supports LPDDR5 memory interfaces, giving production designs a path to compact memory subsystems around video and embedded processing workloads. Embedded control today, hard processor path for production systems The current Agilex 3 Camera Lite reference design uses a Nios® V soft processor running a bare-metal software application. That software discovers the hardware IP blocks, configures them, monitors feedback loops, and provides a terminal-based interface over JTAG-UART. This is a good fit for the reference design because it keeps the example compact and focused on the FPGA-resident video pipeline. For production smart camera or industrial vision systems, Agilex 3 SoC devices add another important platform option: an integrated hard processor system with dual-core Arm® Cortex®-A55 processors. That HPS is not used in this reference design, but it can be a major advantage in a product architecture. Designers can use the FPGA fabric for deterministic video ingest and image processing while using the HPS for system control, application software, communication stacks, user interfaces, sensor orchestration, security services, or higher-level product logic. This combination is especially important for embedded vision. Hardware pipelines are excellent at moving and processing pixels predictably. Software is excellent at managing the product around that pipeline. Agilex 3 gives designers both paths in the same device family: a fabric-based video processing foundation and, when needed, an integrated Arm-based processing subsystem for production software. A path toward AI-enhanced edge vision The Agilex 3 4Kp30 Camera Lite reference design is not an AI inference design. Its focus is 4K camera ingest, ISP processing, video buffering, output mixing, and DisplayPort output. That distinction is important. At the same time, the architecture points naturally toward smarter edge vision systems. Agilex 3 includes AI-capable Tensor Block architecture in the fabric, and Agilex 3 and Agilex 5 share an architecturally aligned FPGA fabric foundation. The related Agilex 5 camera reference design shows the fuller concept by combining multi-sensor 4K camera input, ISP processing, FPGA AI Suite inference, Linux software on the HPS, and display output with AI results. That gives customers a scalable design story. Agilex 3 can be the cost-optimized starting point for 4K smart camera pipelines and edge vision preprocessing. Agilex 5 can scale the concept to larger, more compute-intensive designs that integrate AI inference directly into the reference architecture. Customers can begin with the 4K vision pipeline they need today and scale toward more intelligent camera systems as product requirements evolve. Why it matters The real message of the Agilex 3 4Kp30 Camera Lite reference design is: a lower-density, cost-optimized FPGA can still implement a substantial portion of a modern vision system using available Altera IP. That includes native camera ingest, AXI4-Streaming video movement, ISP processing, frame buffering, output mixing, embedded software control, and DisplayPort output. For customers building smart cameras, industrial vision systems, surveillance endpoints, or edge AI preprocessing pipelines, this is a practical starting point rather than a blank page. With Agilex 3, designers can build compact, customizable 4K vision systems while keeping a clear path to hard processor integration, modern memory support, and future AI-enhanced processing. It is a strong example of how much capability can fit into the power- and cost-optimized segment of the Agilex portfolio. Explore the Agilex 3 4Kp30 Camera Lite reference design and use it as a starting point for your next smart camera, industrial vision, surveillance, or edge AI preprocessing system. Source links for reviewers Agilex 3 4Kp30 Camera Lite developer documentation Agilex 3 camera GitHub repository Agilex 3 FPGAs and SoCs device overview Agilex 3 HPS documentation Agilex 5 4Kp30 Multi-Sensor Camera with AI Inference documentation
14 days ago0likes
Engineers starting a new FPGA design make several important choices before they write the first line of RTL. The device they select influences the tool flow, IP base, debug method, training path, and production roadmap that follow. For teams working on cost-sensitive embedded, vision, control, DSP, and edge AI-enabled systems, the ideal starting point needs to be affordable, accessible, and serious enough to support real implementation work. Agilex® 3 brings that starting point into the modern Agilex portfolio. Built with Intel 7 technology and second-generation HyperFlex™ architecture, Agilex 3 FPGAs and SoCs extend Agilex-class fabric, efficient performance, modern I/O, embedded memory, DSP resources, and security features into power- and cost-optimized applications. The result is a practical entry point for developers who want a current-generation FPGA platform with a path that can grow beyond the first evaluation board. Start with a real Agilex device for less than $130 The Arrow AXC3000 starter kit gives developers a low-cost way to begin designing with Agilex 3. Currently listed through Arrow at $129, the kit is based on the Agilex 3 C-Series 100 device A3CY100BM16AE7S. That means developers can start with a real Agilex 3 FPGA that provides roughly 100K logic elements, 138 DSP blocks, 276 18x19 multipliers, MIPI D-PHY support, LVDS, a Secure Device Manager, internal memory, external HyperRAM, QSPI configuration flash, CRUVI HS expansion, Arduino MKR standard pads, USB-C power, and an on-board programmer and debugger. This gives first-time Agilex 3 users a compact board for labs, proofs of concept, and early design exploration while preserving a connection to production-capable architecture and tools. It also gives experienced teams a low-cost evaluation path for assessing Agilex 3 in edge, industrial, vision, and control applications. The hardware ecosystem gives developers several ways to start. In addition to AXC3000, Terasic lists Agilex 3 kits under $180, including the DE23-Lite Development Kit, Atum A3 Nano, and Atum Nios® V Starter Kit. These options support different entry paths: education and prototyping, compact FPGA development, and Nios V-focused embedded exploration. A complete set of professional tools for no cost The low-cost Agilex® 3 makes FPGA development more accessible, while a no-cost professional tool flow helps developers realize the device’s full performance and design potential. Quartus® Prime Pro Edition software is the professional design environment and is available from the Altera Download Center. For Agilex 3 devices, developers can use Quartus Prime Pro with a no-cost license, providing a fast path from installation to first compile without a separate manual licensing workflow. Quartus Prime Pro gives Agilex 3 developers a professional FPGA implementation environment from day one. The integrated flow includes synthesis, place-and-route, timing analysis, system debug, power analysis, IP integration, and example designs. Altera knows that FPGA designs can become complex quickly, even during early evaluation. Developers need strong visibility into design behavior so they can find issues, validate functionality, and keep projects moving. For that reason, Altera does not charge for system debug tool. We provide a full license for no cost for any Agilex 3 design. Developers can also use advanced Altera tools and capabilities such as DSP Builder, Power & Thermal Analyzer, FPGA AI Suite, and Nios V processor IP where they fit the design objective. That matters because the first evaluation project often becomes the foundation for production work. Design teams want to learn a flow that can carry forward. They want timing closure methods, IP, debug tools, and software habits that remain useful as the design grows. Agilex 3 gives them that continuity in a professional Quartus Prime Pro environment. Application-ready examples make the story concrete The most compelling way to evaluate a starter platform is to see it run a meaningful application. Agilex 3 is well suited for that kind of demonstration because it combines modern FPGA fabric, useful I/O, embedded memory, DSP resources, and application-oriented IP in a cost-optimized device family. A strong example is the Agilex 3 4Kp30 camera reference design. The design shows how a compact FPGA platform can support a complete video pipeline, including image sensor input, MIPI-based connectivity, image signal processing, and display output. For vision developers, that is a much more useful starting point than a generic board bring-up exercise. It connects directly to applications such as industrial vision, smart cameras, robotics, surveillance, retail analytics, and edge preprocessing. For the AXC3000 mentioned above, a GitHub repo is provided that includes several designs for the AXC3000 board: https://github.com/ArrowElectronics/Agilex-3/wiki/Agilex-3-AXC3000-Development-Platform#reference-designs The same principle applies to embedded and software-oriented development. Nios V provides a RISC-V processor path for control-plane and embedded workflows, and the Atum Nios V Starter Kit gives developers a focused way to explore that environment. As additional Agilex 3 software examples become ready for public promotion, they can extend the story into platform management, real-time control, and HPS-based use cases. A starter path that scales Agilex 3 is the accessible on-ramp to the broader Agilex portfolio and Especially Agilex 5 E-series. Developers can begin with low-cost starter hardware, use professional Quartus Prime Pro tools, and build confidence on real application examples. As designs become more demanding, the path does not stop at the entry board. More capable Agilex 3 boards and device options give teams room to expand into richer I/O, larger designs, more embedded memory, and more complete application prototypes. For software-rich embedded systems, Agilex 3 SoC devices extend the story further with a dual-core Arm Cortex-A55 hard processor system integrated alongside the FPGA fabric. That gives developers a path from simple FPGA evaluation into more powerful applications that combine programmable logic, embedded software, real-time control, and system-level processing in one platform. Need more gates? Even more powerful devices? A pin to pin migration path to Agilex 5 E-series will get you there. The same design environment can support early prototyping, design optimization, IP integration, and eventual deployment across Agilex 3 devices and the broader Agilex family.
14 days ago0likes
3 MIN READ
How a published OpenCores study connects workload behavior, fabric architecture, and software optimization. Mid-range FPGA designers rarely optimize for only one thing. A design has to fit. It has to close timing. It has to stay within the power budget. As more functions move into the same device, those requirements become harder to satisfy at the same time. That is why the combination of fabric architecture and software matters. A new Altera white paper, ”Altera Delivers Superior Performance, Power, and Logic Packing with Quartus® and Agilex® 5 FPGAs Versus AMD Kintex™ UltraScale+”, examines this challenge using twelve publicly available OpenCores benchmark designs. The study compares Agilex® 5 E-Series devices with AMD Kintex™ UltraScale+ devices using each vendor’s recommended software flow and a stamping methodology that increases utilization by replicating each design across the FPGA. FPGA performance is application-dependent, and the paper’s value is in showing how different workload types stress different parts of the FPGA architecture and implementation software, highlighting where Agilex 5 E-Series demonstrates meaningful advantages. Why Agilex 5 E-Series is well suited for these workloads Agilex 5 E-Series is designed for mid-range applications that need a balance of performance, power efficiency, and integration density. Its fabric combines HyperFlex™ architecture, adaptive logic modules, embedded M20K memory, and Quartus® Prime optimization technology. Just as important, its regular fabric structure and scalable interconnect help routing remain more predictable as utilization rises. That matters because timing closure is often limited by placement and routing pressure, not only by raw logic count. Because Agilex 5D shares the same underlying Agilex 5 fabric architecture, these fabric-level advantages extend to the D-Series as well, with higher device density, greater on-chip resource capacity, and approximately 20% higher fabric performance. Where the advantages show up For designs where routing and timing closure dominate, such as deeply pipelined processor and error-correction workloads, Agilex 5 E-Series benefits from HyperFlex retiming and register duplication. These capabilities help break up long interconnect paths, reduce critical path depth, and sustain fMAX as replicated design instances push utilization higher. For arithmetic-heavy workloads, such as trigonometric, DSP, and iterative compute kernels, Agilex 5 adaptive logic modules help pack arithmetic more locally and efficiently. Better local packing can reduce routing overhead, which becomes increasingly important as dense compute designs scale across the device. For memory-sensitive and resource-constrained workloads, including video, security, and embedded compute designs, embedded memory and logic packing become key limiters. Agilex 5 E-SeriesM20K resources and efficient ALM utilization help preserve usable logic capacity and timing margin when competing implementations may need more LUT-based memory or additional routing resources. For designs where implementation efficiency depends heavily on the tool flow, Quartus Prime advanced synthesis and physical synthesis add another part of the formula. The software can co-optimize logic, placement, and routing, helping improve utilization and power efficiency without requiring RTL changes. The proof, and what it means The published white paper provides the detailed benchmark data, but several results stand out because they connect directly to real design challenges: 22% higher geometric mean performance at high-utilization operating points. This matters because FPGA designs often become harder to close as utilization rises. Higher performance under those conditions points to better timing behavior when routing pressure, placement density, and resource contention increase. More stable achievable fMAX as utilization increases. The paper shows less frequency degradation for Agilex 5 E-Series as benchmark instances are stamped across the device. For designers, that means more predictable timing closure as the design approaches fuller device usage. 47% lower total power at iso-frequency and iso-workload conditions. This result isolates power at equivalent workload and clock frequency, showing that Agilex 5 E-Series can do the same work with significantly lower total device power in the evaluated designs. Up to 2.83x greater energy efficiency in individual workloads. This shows that the advantage is not only about reducing watts. It also reflects better work-per-watt behavior, which can help improve thermal margin, power budgets, and system-level efficiency. 17% higher effective device capacity. In this context, effective capacity reflects the amount of design logic that can be implemented while still meeting timing constraints Read the full white paper This blog highlights the key findings, but the full whitepaper provides detailed benchmark data, workload-by-workload analysis, methodology transparency, and architectural insights across all twelve OpenCores designs. Read the whitepaper to understand how Agilex 5 E devices and Quartus Prime software delivered higher performance, lower power, and greater effective design capacity across a diverse set of real FPGA workloads. Altera Delivers Superior Performance, Power, and Logic Packing with Quartus® and Agilex® 5 FPGAs Versus AMD Kintex™ Ultrascale+
14 days ago0likes