CONTROL BOARDS · DISAMBIGUATION

The model name is not enough

Two Antminers can carry the same sticker, the same series and the same hashrate, and still need two different firmware files. The firmware runs on the control board, not on the case label. Read the board before you name a file

Updated 2026-08-09 · release 1.3.5 stable

The four control board families

How to read the board in your device

• Power the device down and open the compartment with the control board: it is the small board carrying the network socket, not a hash board
• Find the main chip and match it against the table above. The position of the chip is the fastest tell: next to the SD slot means Amlogic, centre of the board means Xilinx
• A plugged-in daughter board means BeagleBone, and there is nothing else to check
• The web interface of the firmware already running on the device also reports the platform, which saves opening the case

The models where the name is ambiguous

Fourteen model names cover more than one board. For these, the sticker on the case does not identify the file, so the board has to be read first:

The exact build id, file name, file size and SHA-256 for every model and board combination is published in the machine-readable catalog and in the full disambiguation table.

Why this matters before you download anything

A wrong file is not a failed install. It is a device that does not come back up on its own and needs the recovery procedure for its particular board. The order that avoids this is always the same: identify the board, look up the one build that belongs to it, verify the SHA-256 of the downloaded file, then flash. The verification guide covers the checksum step on Windows, macOS and Linux.

Board families and build assignments are generated from the published firmware catalog and refreshed with every release. Flashing always remains the owner's action on the owner's hardware