Skip to content
Small team, full backlog, zero orders dropped. Support replies are slower than we’d like. Read our status update → Zero orders dropped. Status → 📬 Check your spam folder — most of our replies land there. We do answer. Status update → 📬 Check your spam folder. Status →

Which Antminer Control Board Do I Have?

Before you flash, unlock, recover or replace anything on an Antminer, you need one fact:
which control-board family you are holding. Bitmain shipped four — Xilinx Zynq, BeagleBone
(AM335x), Amlogic (A113D) and CVITEK (CV1835) — and they differ in recovery media, firmware
options, and whether an open firmware can run at all. The identifier below gets you to a
confident answer in under a minute, then routes you straight into the right recovery entry,
dataset row and firmware path on this site. It works with JavaScript disabled: every question
and every outcome is on this page.

Four control-board families run the Antminer fleet: Xilinx Zynq, BeagleBone (AM335x), Amlogic (A113D) and CVITEK (CV1835). The family — not the model name — decides your recovery media, your firmware options and whether the board can be unlocked at all. One model does not equal one board: the S19j Pro alone shipped with all four board types across production batches. Never assume the board from the sticker.

Step 1 — Does the miner still boot?

If you can reach the web UI or SSH in, software identification is the reliable route — it reads the silicon directly instead of guessing from the enclosure.

Software identification — the reliable route

ActionCommand / locationYou should seeWhat it proves
Read the SoC over SSH Supported cat /proc/cpuinfo Dual Cortex-A9 (Zynq) · quad Cortex-A53 AArch64 (Amlogic A113D) · single Cortex-A8 (TI AM335x BeagleBone) The CPU string names the board family directly.
BraiinsOS platform key Verified cat /etc/bos_platform A platform string such as zynq-bm3-am2 On BraiinsOS installs the prefix is the board family, stated by the firmware itself.
Web-UI build string Supported Web UI → system / overview page A build-target string naming the control-board build Stock and custom firmwares embed the board target in the build name. If the string names CV1835 / CVITEK — that is your answer.
ASIC ChipID over the chain Verified Chain enumeration (kernel log, or a firmware that reports ChipID) 0x1387 = S9-gen BM1387 · 0x1397/0x1398 = S17/S19-gen · 0x1362 = S19j Pro Identifies the ASIC generation only. It narrows the model — it must never be mapped 1:1 to a control board (an S19j Pro can carry any of the four).

Read your result

Step 2 — Look at the board. Which of these matches?

Power the miner off and look at the control board itself — the small PCB with the Ethernet jack, separate from the three hashboards. Check for an SD/microSD slot, first on the board, then under the enclosure cover. Three of the four families have a Verified physical signature; CVITEK has none — it is identified by software or by elimination.

Ignore the 18-pin hash-board connector. The 18-pin (2×9, 2.0 mm pitch) connector is shared across the Zynq-era families — it is deliberately universal, which is exactly why it identifies nothing. Verified

Why we never ask where the port sits. Forum lore says things like “micro-USB on the faceplate” or “SD slot next to the Ethernet jack.” The presence or absence of these ports is documented; their placement is not verified across board revisions — so this identifier only asks questions with verified answers.

Fallback — read the SoC part marking

Inferred The part numbers below are verified per family, but whether the printed marking is legible on your board in-situ is not guaranteed — coatings and heatsinks get in the way. If you can read the main SoC:

Result: Xilinx Zynq control board

Silicon: Xilinx Zynq-7010 (XC7Z010) — dual Cortex-A9 @ 667 MHz with an on-die Artix-7 FPGA driving the hashboard UARTs; X19-generation boards (C55/C71) use the Zynq-7007S. Verified

Era / models: S9, S15, S17, T17, S19, S19 Pro, S19j Pro (Zynq batches). Remember: later S19j Pro batches moved to BeagleBone, Amlogic or CVitek — the family is per-board, not per-model. Verified

Recovery path: SD-card boot via the J3/JP4 jumper — non-destructive, NAND untouched; revert by pulling the card and restoring the jumper. Verified U-Boot serial console over UART is the second door. Supported

DCENT_OS: this is the only family with signed public-beta artifacts — S9 (Zynq XIL1) and S19j Pro (Zynq XIL3), both with pool shares accepted on the bench. Experimental beta; never on revenue-critical hardware.

Continue:

Result: BeagleBone (AM335x) control board

Silicon: TI AM335x Sitara, single Cortex-A8, no FPGA — chain UARTs are software-driven (/dev/ttyO1–5). Verified

Era / models: late-2021+ S19j and S19j Pro on the S19J_IO_BOARD_V2. Verified

Recovery path: reflash the internal SD card under the enclosure cover. Verified

DCENT_OS: S19j Pro BeagleBone runtime path has hashed in the lab, but it is lab-gated — no signed public install artifact for this family.

Continue:

Result: Amlogic (A113D) control board

Silicon: Amlogic A113D, quad Cortex-A53 (AArch64), no FPGA, a single UART multiplexed across all chains. No SD slot; the recovery rail is the micro-USB OTG port. Verified

Era / models: latest S19j / S19j Pro batches, S19 XP, S19k Pro, S21, T21. On the S21 the voltage path is TAS5782M DACs — there is no PIC on that board. Verified

Recovery path — date-dependent: micro-USB OTG reflash (USB_Burning_Tool) Verified — but Bitmain stock firmware from September 2025 onward disables the micro-USB recovery handler, and the March-2024 lock already gates custom firmware. Which stock build your board carries decides everything: check the firmware lock tracker before you plan a flash.

DCENT_OS: in-place install on stock Amlogic is blocked (AMLCtrl boundary); only a lab-gated runtime window exists. Not shipped for this family.

Continue:

Result: CVITEK (CV1835) control board

Silicon: CVITEK CV1835, no FPGA, chains multiplexed through uart_trans.ko. Supported Application CPU: dual-core ARM Cortex-A53 (aarch64) at a supported ~1.0 GHz — the «RISC-V» figure some sources repeat traces to a vendor PDF mislabeled CV1835 that actually documents the CV1812H. Verified

Era / models: recent S21/T21 batches, T19, S19j Pro, S19k Pro, S19 XP, S19j XP, L9. Supported

Recovery path: the boot ROM loads bl1.bin + bl2.bin from a FAT32 volume — an analysis path only. Persistent custom installs are blocked (eFuse-locked signed FIP chain), and vendor “custom” firmwares for this family run as parasitic overlays that revert to stock on cold boot. Verified Supported

DCENT_OS: blocked — marked not-attempted. No unsigned persistent boot path exists on this family, from anyone.

Continue:

Result: still unidentified

Without board access or network access there is no honest answer from the model sticker alone — the same model ships with different boards. A dead board with unreadable silicon is not a dead end either — it just moves the identification into the recovery workflow, which is organized by family for exactly this reason. If your board carries Braiins BCB100 or other aftermarket markings, it is not a Bitmain board and these terminals don’t apply — start from the reference dataset below.

After you identify the board

The family decides the next move. Zynq boards recover over the SD slot with the boot jumper —
start at the SD-card recovery guide. Amlogic
boards live or die by their stock firmware date — check the
firmware lock tracker before planning anything.
Every family has a dedicated entry in the
control-board recovery playbook and a full dataset row
(SoC, models, chip family, host interface, flash notes) in the
ASIC control board reference. If the board itself is
the casualty, the replacement
board buying guide
covers sourcing, and our repair bench covers
everything else. Symptom still undiagnosed? Walk the
Antminer troubleshooting decision tree
its board-dependent forks link back here.

How do I identify my Antminer control board without opening the case?

If the miner boots, don’t open anything: read cat /proc/cpuinfo over SSH.
Dual Cortex-A9 means Xilinx Zynq, quad Cortex-A53 means Amlogic A113D, single Cortex-A8 means
BeagleBone AM335x. On BraiinsOS, cat /etc/bos_platform names the board family
directly. The software route is more reliable than any visual check.

Which Antminer control boards have an SD-card slot?

Xilinx Zynq boards carry an SD slot on the board itself with a boot jumper (J3/JP4) beside it.
BeagleBone boards boot from an SD card mounted inside the enclosure cover. Amlogic boards have no
SD slot at all — their recovery rail is a micro-USB OTG port, and stock firmware from September
2025 onward blocks it.

Does every Antminer S19j Pro use the same control board?

No — and this is the trap that bricks boards. The S19j Pro shipped with four different control
boards across batches: Xilinx Zynq, BeagleBone, Amlogic and CVitek. Recovery media and firmware
compatibility are properties of the board, not the model name. Identify first, flash second.

Does the hash-board connector identify the control board?

No. The 18-pin (2×9, 2.0 mm pitch) hash-board connector is shared across the
Zynq-era families — it is deliberately universal, which is exactly why it cannot discriminate
between board types. Use the SD-slot/micro-USB signals or software identification instead.