We detect you are using an unsupported browser. For the best experience, please visit the site using Chrome, Firefox, Safari, or Edge. X
Maximize Your Experience: Reap the Personalized Advantages by Completing Your Profile to Its Fullest. Update Here
Stay in the loop with the latest from Microchip. Update your profile while you are at it. Update Here
Complete your profile to access more resources. Update Here

What is a System-on-Chip (SoC) FPGA?

System-on-Chip (SoC) FPGAs


An SoC is a computer system embedded into a single chip that integrates a processor, key peripherals/interfaces and system functions, so it can run firmware, and often an OS, and directly control real-world I/O without needing lots of companion chips.

Our SoCs also include an FPGA fabric on the same device, so you can run embedded software on the processor while using programmable logic to add custom I/O, acceleration and real-time interfaces. We offer two common embedded FPGA options:

  • SmartFusion® 2 SoC integrates an Arm® Cortex®-M3 core for MCU-class control
  • PolarFire® SoC FPGA integrates a multi-core RISC-V® MPU cluster to support Linux®, bare metal and real-time workloads in one chip

Key Components of a SoC


An SoC typically includes these building blocks (in embedded systems terms):

  • Microprocessors (MPUs): Run your application firmware, Real-Time Operating System (RTOS) or Linux
  • Memory subsystem: On-chip SRAM plus external memory interfaces, such as DDR, to hold code and data
  • FPGA fabric: Programmable logic that lets you add custom peripherals, real-time I/O and hardware acceleration alongside the MPU, without changing the processor software model
  • Peripherals: Built-in I/O blocks like timers and communication interfaces to connect to sensors, control loops and networks
  • Clock/reset management: Generates and manages clocks and resets so that the system runs reliably and can be optimized for power/performance
  • Security hardware: Features include secure boot and encryption to protect code, data and device access, and embedded crypto-processors

Benefits of SoC Integration


Smaller Systems

Smaller Systems

SoC integration helps build smaller, simpler embedded systems by combining the MPU and common system functions into one device.

Lower Power

Lower Power and Reduced Cost

By minimizing chip-to-chip I/O and removing controllers and glue logic, SoC integration reduces board area, lowers platform power and reduces the Bill of Materials (BoM) costs.

Reliability and Faster Development

Reliability and Faster Development

Fewer external components improve system reliability and speed development by reducing integration risk.

Programmable Fabric

Programmable Fabric

PolarFire and SmartFusion 2 SoC FPGAs include on-chip programmable fabric (up to 500K logic elements), which can replace external logic and allow integration of custom interfaces or acceleration without adding more chips.

How a System-on-Chip Works


An SoC works like a small, embedded computer condensed into a single device. Your software runs on the built-in processor, which takes inputs from sensors, networks and user controls through integrated interfaces, makes decisions and then drives outputs to motors, actuators, data links and displays, all without needing a separate CPU board.

In our SoC FPGAs, the processor multicore complex runs one or more applications, and the on-chip FPGA fabric can be configured to add custom, real-time I/O or acceleration. Software handles system control and algorithms, while the FPGA implements the specialized hardware pieces so you can adapt interfaces and performance without redesigning the whole system.

SoC vs. Microcontroller vs. Microprocessor


What is the difference between an MCU, MPU and SoC?

An MCU is optimized for deterministic control. An MPU provides higher compute and typically runs Linux®. An SoC integrates processing with more system functions to reduce board complexity.

When should I use a microcontroller?

Use an MCU for sensors, motor control, simple connectivity and real-time control. MCUs usually run bare metal or an RTOS and need limited external memory.

When should I use a microprocessor?

Use an MPU when the design needs Linux, higher compute, external DDR memory, advanced software stacks or companion chips for system functions.

When should I use an SoC?

Use an SoC when you need MPU-like processing plus integrated system functions in one device to simplify the board and embedded software model.

Applications of SoCs


SoCs are widely used for embedded computing, connectivity and real-time control in a compact, power-efficient design. Common applications include:

  • Connected devices such as gateways, sensors and smart edge nodes
  • Industrial equipment like PLC-style controllers, predictive maintenance systems, and secure communications endpoints
  • Machine vision systems for smart cameras, inspection, and video analytics
  • Motor-control and power-control platforms in factory automation
  • Robotics systems that combine real-time control with sensor fusion
  • Smart electronics such as building automation panels, medical instruments and secure Human-Machine Interface (HMI) devices

These applications often benefit from the FPGA fabric by adding deterministic I/O, custom interfaces and hardware acceleration alongside an embedded MPU.

Get Started With SoC-Based Design


  • To get started with our PolarFire SoC FPGAs, use a combination of embedded software and FPGA hardware workflow, which is built around the Libero® SoC Design Suite and our Mi-V RISC-V ecosystem.
  • Start by installing Libero SoC Design Suite, which provides the integrated FPGA design flow (from RTL/IP integration through programming) and includes SmartHLS for C/C++-based, high-level synthesis to accelerate hardware creation
  • Next, build your hardware platform in Libero Design Suite using Microchip IP library, which includes pre-validated Microchip and partner IP cores, to assemble interfaces and subsystems quickly
  • For software, use our Mi-V RISC-V® ecosystem for toolchains, OS options, middleware and design resources aligned to PolarFire SoC development
  • To move faster, pull proven RISC-V resources, such as reference designs, Linux examples and BSP assets, from our PolarFire SoC GitHub page

 

 

Live Chat

Need Help?

Privacy Policy