An industrial edge node needs power where there may be no outlet. It also needs a network link and I/O that talks to sensors and actuators. The PolarBerry from Sundance DSP puts all three on one 55 x 85 mm module. It is built around a Microchip PolarFire SoC FPGA, and it can take its power from the Ethernet cable.
This article explains where PolarBerry fits in industrial automation. It also covers why Power over Ethernet (PoE) matters on the plant floor. Finally, it shows how the Raspberry Pi compatible header shortens the path from prototype to a secure, deployed system.
What PolarBerry is
PolarBerry is a system on module (SoM). That means a small board carries the processor, memory and power circuits, so the carrier board does not have to. According to the Sundance DSP product page, it uses the MPFS250T-FCVG484 device with 250k logic elements.
Sundance DSP’s PoE article and Microchip’s device table give the exact figure as 254,000, with 784 math blocks. The module also carries 4 GB of DDR4, 4 GB of eMMC and 128 MB of SPI NOR flash for booting.
For I/O, the same page lists a Gigabit RJ-45 port, a second 100/1000BASE-T interface on the carrier connector, and two CAN 2.0 PHYs. There are also four high-speed transceivers rated from 250 Mbps to 12.7 Gbps. Samtec connectors link the module to a carrier. A Sundance DSP, PCIe carrier can also give it access to an FMC slot.
The processor side is a hardened RISC-V cluster. Sundance DSP’s PoE sensor article describes one E51 monitor core and four U54 application cores. All five run at 625 MHz and share a 2 MB L2 cache. So you can run Linux on some cores while others handle hard real-time tasks.
Why PolarFire SoC suits the factory edge
An edge controller in a factory has to meet tight timing, stay cool in an enclosure, keep working through upsets and resist attack. PolarFire SoC deals with each of these in the silicon itself.
Deterministic cores next to Linux
Control loops need timing you can predict. A 2018 Electronic Design article explains that each core can switch off features such as the branch predictor, so its timing becomes deterministic. The same article notes asymmetric multiprocessing (AMP), where each core runs its own software. For example, one U54 core can run a bare metal motor loop while the others run Linux and the network stack.
Microchip’s own PolarFire SoC workshop slides describe the same approach. They use L2 Loosely Integrated Memory with branch prediction turned off for deterministic hard real-time work.
Low power and instant-on
The same Microchip slides claim “up to 50% lower power” for the mid-range PolarFire family, although they do not state the baseline for that comparison. They also describe the device as instant-on and non-volatile. Because the FPGA configuration lives on the die, the fabric does not load a bitstream from external flash at power-up. Sundance DSP notes that the board is operational almost immediately after power is applied.
At 16 W maximum for the whole module, Sundance DSP’s article says no fan is needed. Instead, convection through a metal enclosure or a heat spreader is enough. That matters in a sealed cabinet, since a fan is one more part that wears out.
SEU immunity
A bit flip in an FPGA’s configuration can silently change the logic it runs. Microchip’s slides state that the PolarFire FPGA configuration is SEU immune, where SEU means single event upset.
The reason is physical. The configuration is held as charge in oxide-isolated floating gates, whereas a particle hit can change the state of an SRAM cell. In practice, no configuration scrubbing is needed. SECDED also protects the processor memories, correcting single-bit errors and detecting double-bit errors.
Security built into the device
Security is now part of the design brief for industrial products. The ISA/IEC 62443 series sets requirements for secure industrial automation and control systems. Part 4-2 covers the technical security requirements for components, so product suppliers need hardware that can support it.
PolarFire SoC covers much of the hardware side. For example, Microchip’s slides list DPA-resistant bitstream programming, anti-tamper, a physically unclonable function (PUF), a true random number generator and a side-channel resistant crypto coprocessor.
The SoC adds secure boot, physical memory protection and immunity to Spectre and Meltdown. Sundance DSP’s secure edge guide adds a practical point. With no external bitstream at power-up, an attacker has no bus to sniff and no image to clone.
Still, a secure chip is only one part of compliance. Certification under IEC 62443 applies to the full product and its development process.
The diagram below answers a simple question: what sits where on the module?
Figure 1: PolarBerry building blocks, grouped by layer. Data from the Sundance DSP product page and PoE article, and Microchip’s PolarFire SoC slides (254k logic elements, 784 math blocks; the product page rounds this to 250k).
Why PoE matters on the plant floor
Power over Ethernet sends low-voltage DC power down the same twisted-pair cable that carries data. Cisco’s industrial PoE brief puts the main benefit plainly. PoE removes the need to run extra copper cabling and steel conduit to each device.
Fewer cables, lower cost
Every new sensor or controller on a line needs a power feed. With PoE, each node needs one cable instead of two. Sundance DSP makes the same point for PolarBerry. There is no separate power supply, barrel jack or 5 V run, so cabling drops from two runs per node to one.
Central power, central control
With PoE, the switch becomes the power source, and that changes how you run a site. The Cisco brief notes that a UPS can back up the switches, so the powered nodes share one protected supply. Network equipment can also monitor power use and shut off devices that are not in use.
For PolarBerry, Sundance DSP says the node powers up and down with the switch. So, because the switch controls port power, you can reset a node from the network without a site visit.
However, there are limits. Cisco states that PoE typically reaches up to 100 meters (328 feet) over standard Ethernet cable. It also warns that both the switch and the powered devices must be rugged enough for heat, moisture, dust and vibration.
Which PoE class does PolarBerry need?
IEEE has published three generations of PoE. The Ethernet Alliance overview of 802.3bt gives the history. First, 802.3af (2003) delivered about 13 W to devices, and 802.3at (2009) raised this to 25.5 W. Then 802.3bt lifted it to 71.3 W by using all four pairs in the cable.
Each standard sets power by class. The switch, or power sourcing equipment (PSE), supplies more than the powered device (PD) receives, since the cable loses some on the way.
The chart below answers the sizing question. It shows the power at the switch and at the device for each class, against the 16 W PolarBerry module.
Figure 2: IEEE PoE power classes. Class 3 and below deliver at most 13 W to the device, which is below the 16 W module rating.
Classes 1 to 3 fall below the line, so a plain 802.3af port cannot run the module at full load. Sundance DSP’s article reaches the same conclusion. PolarBerry needs a PoE+ (802.3at) switch, which supplies up to 30 W at the port and about 25.5 W at the device.
An 802.3bt switch also works if its port supports Class 4 or higher. The Ethernet Alliance notes that PoE devices interoperate across generations, but a port only delivers the power it is built to supply. In fact, an 802.3bt switch is not required to support every class, so check the port rating before you deploy.
PoE is an ordering option. The product page lists it “by request”, and the PoE boards are pin-compatible with the carrier-powered version. So you can develop on a carrier and switch to PoE for deployment without a new layout.
How the RPi connector speeds up development
PolarBerry carries a 40-pin header that follows the Raspberry Pi layout. On a Raspberry Pi, the official documentation describes two rows of 20 pins at 3.3 V logic. Some pins also serve as I2C, SPI, UART and PWM.
Sundance DSP describes the supply of off-the-shelf RPi HATs as vast. Some follow the formal HAT rules. The raspberrypi/hats repository defines these as a full-size 40-pin connector, an ID EEPROM and a mechanical spec. In December 2023, Raspberry Pi published a preliminary HAT+ specification to update the 2014 original.
What the header connects to
On PolarBerry the header is wired straight into the SoC. Sundance DSP’s RPi connector article gives the split. Of the GPIOs, 20 go to the FPGA fabric and 6 go to the processor subsystem, plus one I2C and one UART.
All signals are 3.3 V logic. That matches the Pi, but check any add-on board for 3.3 V compatibility first.
The fabric pins are the important part. Because they land in programmable logic, you can build a custom protocol, a precise timer or a high-rate capture engine in hardware. The product page notes that these pins can be assigned to SPI, UART, CAN or other interfaces.
From breadboard to field in fewer steps
Sundance DSP lists the add-on board types that suit the header. They include sensor boards, relay and industrial I/O boards, motor controllers, PLC interface hardware, encoder interfaces and camera modules. So a team can build a working rig from boards it can buy, before it designs any custom hardware.
Sundance DSP is also designing an FMC-RPi module that brings a Raspberry Pi header and eight PMOD headers to VITA 57.1 FMC carriers. Its technical deep dive says the module is still in the design phase. The same article argues that off-the-shelf HATs and PMODs can compress months of hardware work into days or weeks. According to Sundance DSP, the approach works best for proof of concept, research and low-volume products.
The flow below shows a typical path from prototype to a deployed PolarBerry node. It is a conceptual sequence built from the Sundance DSP tool and boot notes, not a fixed procedure.
Figure 3: A conceptual development path for a PolarBerry based edge node.
Secure by default in the field
Field units also need a safe way to update and recover. Sundance DSP’s reflashing guide describes the boot chain. The Hart Software Services (HSS) start from internal eNVM, then U-Boot runs, and then Linux loads from eMMC.
To reflash, HSS goes over the onboard USB-JTAG bridge, U-Boot over UART, and Linux over Ethernet using TFTP. The guide explains that Sundance DSP’s SOM1-SoC leaves out a USB-OTG port and a removable SD card on purpose, for security, and boots from onboard eMMC instead. PolarBerry also boots from eMMC, and its product page lists no SD card slot.
Where PolarBerry fits in industrial automation
These features suit several jobs on the plant floor. The product page names industrial automation, industrial control systems and IP cameras among its targets. In practice, that covers several node types:
- A PoE-powered sensor hub that reads vibration, pressure or temperature boards on the header and filters the data in the fabric.
- A small motion or I/O controller that uses the two CAN PHYs and a deterministic U54 core, with Linux handling the user interface and logging.
- A vision or inspection node that pre-processes camera data in the FPGA and sends only results upstream.
That last pattern is how Sundance DSP uses the board in its unattended ground sensor design. The node processes sensor data locally and sends short, encrypted results over the same cable that powers it. The same idea suits industrial edge computing, where raw data stays at the machine.
Ethernet itself is also gaining deterministic features. The IEEE TSN task group develops Time-Sensitive Networking. Its goal is bounded latency and low packet loss over IEEE 802 networks. Programmable logic gives you room to add protocol features later, but check which protocol IP your design actually needs.
Getting started
If you are new to PolarFire SoC, Sundance DSP’s secure edge guide sets out a sensible learning path. Start with a simple Libero design, such as a blinking GPIO or a UART. Next, boot Linux on the RISC-V cores. Only then move on to secure boot, PUF-based keys and the crypto engine.
For an industrial team, the practical plan is short. Prototype on the RPi header with boards you can buy, and prove the timing in the fabric. Then order the PoE version and plug it into a PoE+ switch. To discuss PolarBerry for your application, start from the PolarBerry product page and contact Sundance DSP.
References
- Sundance DSP: PolarBerry FPGA module with RISC processors
- Sundance DSP: PolarBerry: A PoE-Powered RISC-V Platform Built for Unattended Ground Sensors
- Sundance DSP: Using the PolarBerry RPI Connector
- Sundance DSP: Architecting the Secure Edge: A Guide to Learning High-Reliability FPGA SoC Development with PolarFire and PolarBerry
- Sundance DSP: Unbricking and Reflashing U-Boot and Linux on the PolarFire SoC (SOM1-SoC and PolarBerry)
- Sundance DSP: FMC-RPi VITA 57.1 FMC
- Sundance DSP: FMC-RPi Technical Deep Dive: Bridging FPGA and Raspberry Pi Ecosystems
- Microchip: PolarFire SoC, Different and Unique SoC Solution (CERN 3rd SoC Workshop, 2023)
- Electronic Design: Hard-Core RISC-V Cores Mate with FPGA
- Ethernet Alliance: Overview of 802.3bt, Power over Ethernet standard
- Cisco: PoE for Industrial Automation: Power, Data and Control over a Single Cable
- Raspberry Pi: Raspberry Pi hardware documentation
- Raspberry Pi: raspberrypi/hats repository
- Raspberry Pi: Double standards
- ISA: ISA/IEC 62443 Series of Standards
- IEEE 802.1: Time-Sensitive Networking (TSN) Task Group
