Definition
The control board (also called the controller, main board, or BB board) is the central management unit of an ASIC miner: a small single-board computer that runs the mining firmware, distributes work to the hashboards, monitors temperatures and fans, and talks to the pool over the network. It is the brain; the hashboards are the muscle.
Physically, the control board is a compact circuit board mounted at one end of the miner chassis, carrying a system-on-chip (SoC), RAM, flash storage, an Ethernet port, and the connectors that ribbon out to each hashboard. When people say a miner is “running” but producing zero hashrate, the fault is often on the control board side — not the hashboards themselves.
What the control board does in a real ASIC
The SoC on the board boots a small Linux system from onboard firmware, then launches the mining daemon (cgminer/bmminer on stock Bitmain, or alternatives like bosminer). From there the control board:
- Distributes work and collects shares. It receives jobs from the pool over the Stratum protocol and feeds them down to the ASIC chip chains on each hashboard.
- Manages the hardware bus. It drives the UART links to the ASIC chains, reads temperature sensors and EEPROMs over I2C, and controls fan PWM. On Antminer hashboards this all runs over a shared 18-pin 2×9 connector carrying SDA, SCL, TXD, RXD, ground, and a hashboard-present (PLUGO) detect line.
- Sets the operating point. Depending on platform, the board commands the PSU and an onboard PIC voltage controller to set hashboard voltage, while firmware autotuning trims frequency at runtime.
- Serves the web UI and API. A lightweight web server (lighttpd on stock firmware) exposes configuration and the cgminer API for monitoring.
The SoC platforms you will actually encounter
Not all control boards are the same — the SoC family largely determines compatibility, firmware options, and repairability:
- Xilinx Zynq 7010 (XC7Z010) — S9, S15, S17 and early S19 boards. A dual-core ARM Cortex-A9 at 667 MHz paired with FPGA fabric. The FPGA implements the UART FIFOs, I2C master, fan PWM and glitch monitor that bridge the CPU to the ASIC chains. These boards boot FSBL → FPGA bitstream → U-Boot → kernel from 256 MB NAND flash.
- BeagleBone Black / TI AM335x — used on some late S19j Pro units. A single Cortex-A8 with no FPGA; the SoC drives the ASIC UARTs directly.
- Amlogic A113D — S19j Pro+, S19 XP, S19k Pro, S21. A quad-core Cortex-A53 (originally an audio SoC) with no FPGA and, increasingly, eMMC storage and a layered secure-boot chain.
This is why a “control board” is never universal: a replacement must match the specific miner model and generation, and firmware built for a Zynq board will not run on an Amlogic board. It also explains why repair shops keep model-specific spares on hand.
Common control board failures
Because the control board concentrates so much logic in one place, its failures tend to be total rather than partial. Frequent culprits:
- Corrupted firmware or failed NAND/eMMC flash — the board powers but never boots, or reboots in a loop. Many Zynq boards can be re-flashed via SD-card recovery; Amlogic boards may require a jumper recovery procedure.
- Damaged Ethernet port or PHY — the miner runs but is unreachable on the network.
- Power-regulation faults — onboard regulators that feed the SoC fail, killing the board outright.
- Bus faults — a shorted I2C or UART line can make every hashboard report as missing even though the boards are healthy.
A practical diagnostic habit: before condemning a control board, confirm the hashboards detect on the bus and that fans report nonzero RPM. Misread sensor or detect lines frequently masquerade as board death. Our ASIC troubleshooting guides walk through isolating control-board versus hashboard faults step by step.
Understanding the control board also matters for the open-firmware movement. Because the SoC runs a standard Linux stack, the control board is where alternative firmware lives — and it is the layer D-Central’s open-source work targets to give miners more sovereignty over their own hardware. If you are sourcing replacement controllers, refurbished hashboards, or full miners, D-Central stocks model-matched parts and tested units in the shop.
In Simple Terms
The management board in an ASIC miner that runs firmware, coordinates hashboards, and connects to the network.
The control board (also called the controller, main board, or BB board) is the central management unit of an ASIC miner: a small single-board computer that runs the mining firmware, distributes work to the hashboards, monitors temperatures and fans, and talks to the pool over the network. It is the brain; the hashboards are the muscle.
Physically, the control board is a compact circuit board mounted at one end of the miner chassis, carrying a system-on-chip (SoC), RAM, flash storage, an Ethernet port, and the connectors that ribbon out to each hashboard. When people say a miner is "running" but producing zero hashrate, the fault is often on the control board side — not the hashboards themselves.
What the control board does in a real ASIC
The SoC on the board boots a small Linux system from onboard firmware, then launches the mining daemon (cgminer/bmminer on stock Bitmain, or alternatives like bosminer). From there the control board:
- Distributes work and collects shares. It receives jobs from the pool over the Stratum protocol and feeds them down to the ASIC chip chains on each hashboard.
- Manages the hardware bus. It drives the UART links to the ASIC chains, reads temperature sensors and EEPROMs over I2C, and controls fan PWM. On Antminer hashboards this all runs over a shared 18-pin 2×9 connector carrying SDA, SCL, TXD, RXD, ground, and a hashboard-present (PLUGO) detect line.
- Sets the operating point. Depending on platform, the board commands the PSU and an onboard PIC voltage controller to set hashboard voltage, while firmware autotuning trims frequency at runtime.
- Serves the web UI and API. A lightweight web server (lighttpd on stock firmware) exposes configuration and the cgminer API for monitoring.
The SoC platforms you will actually encounter
Not all control boards are the same — the SoC family largely determines compatibility, firmware options, and repairability:
- Xilinx Zynq 7010 (XC7Z010) — S9, S15, S17 and early S19 boards. A dual-core ARM Cortex-A9 at 667 MHz paired with FPGA fabric. The FPGA implements the UART FIFOs, I2C master, fan PWM and glitch monitor that bridge the CPU to the ASIC chains. These boards boot FSBL → FPGA bitstream → U-Boot → kernel from 256 MB NAND flash.
- BeagleBone Black / TI AM335x — used on some late S19j Pro units. A single Cortex-A8 with no FPGA; the SoC drives the ASIC UARTs directly.
- Amlogic AXG (A113-class) — S19j Pro+, S19 XP, S19k Pro, S21, S21 Pro, S21 XP, T21. A quad-core Cortex-A53 (originally an audio SoC) with no FPGA and, increasingly, eMMC storage and a layered secure-boot chain.
This is why a "control board" is never universal: a replacement must match the specific miner model and generation, and firmware built for a Zynq board will not run on an Amlogic board. It also explains why repair shops keep model-specific spares on hand.
Common control board failures
Because the control board concentrates so much logic in one place, its failures tend to be total rather than partial. Frequent culprits:
- Corrupted firmware or failed NAND/eMMC flash — the board powers but never boots, or reboots in a loop. Many Zynq boards can be re-flashed via SD-card recovery; Amlogic boards may require a jumper recovery procedure.
- Damaged Ethernet port or PHY — the miner runs but is unreachable on the network.
- Power-regulation faults — onboard regulators that feed the SoC fail, killing the board outright.
- Bus faults — a shorted I2C or UART line can make every hashboard report as missing even though the boards are healthy.
A practical diagnostic habit: before condemning a control board, confirm the hashboards detect on the bus and that fans report nonzero RPM. Misread sensor or detect lines frequently masquerade as board death. Our ASIC troubleshooting guides walk through isolating control-board versus hashboard faults step by step.
Understanding the control board also matters for the open-firmware movement. Because the SoC runs a standard Linux stack, the control board is where alternative firmware lives — and it is the layer D-Central's open-source work targets to give miners more sovereignty over their own hardware. If you are sourcing replacement controllers, refurbished hashboards, or full miners, D-Central stocks model-matched parts and tested units in the shop.