Antminer S17 & T17 Firmware: Stock, Braiins OS+, VNish & LuxOS by Control Board

The S17 and T17 generation is the one the internet has quietly stopped serving. Bitmain’s own download portal has moved on, LuxOS does not list these models at all, and the pages that still rank for “Antminer S17 firmware” are mostly distributors hosting files with no hash and no stated origin. Meanwhile the machines are still hashing, still being repaired, and still being bought second-hand as space heaters and starter units. This page is the decision layer for them: every real firmware option including stock, matched to the control board and the chip it actually supports, plus an honest inventory of the nineteen archive files D-Central mirrors for this generation, each with a published SHA-256. We host these for bench work and we say exactly what each one attests about itself. D-Central repairs this hardware in Montreal, and this is the page we would want a customer to have read first.

Jump to: BM1397 vs BM1396 · the am2 board · firmware options · install reality · what we hold, and what we do not

BM1397 vs BM1396: the split that decides which image is yours

This family looks like seven models. Electrically it is two, and confusing them is the most common error in S17-era flashing advice.

🔴 BM1396 is the “e” chip, and only the “e” chip. It is not the “Plus” chip and it is not an S19-generation part. The S17+ and T17+ are BM1397, the same silicon as the plain S17 and T17. The two chips are register-compatible — they share the 0x51/0x41 header family — which is exactly why the mistake survives: an image built for the wrong one can look like it is talking to the board right up until it is not. They are distinct silicon and they are not interchangeable in a repair. D-Central’s own open-source firmware source encodes the split explicitly, mapping only the s17e and t17e board targets to the BM1396 identity.

The T17e figures above come from Bitmain’s own AMTC maintenance guide: 78 chips arranged as 13 domains of 6, at 1.35 V per domain and roughly 17.65 V across the board, on an APW9+ supply. Note the unit — voltage on these boards is set per domain, not per chip. Per-chip frequency tuning is a real feature that several firmwares offer; per-chip voltage is not a thing this hardware does, and copy that claims it is describing something else.

One control board, and it still has an SD slot

Almost everything that makes newer Antminers difficult to flash is absent here. This whole generation runs on the Xilinx Zynq am2 control board — a single family, with an SD-card slot, a working boot rail, and no Amlogic lock and no CVitek eMMC-first BootROM to work around. There is no March 2024 install lock on a machine built in 2019.

That is the good news and it is genuinely rare in 2026: an S17 or T17 is one of the last Antminers you can still recover and reflash entirely on your own bench, with a card reader and a copy of the right image. It is also why the mirror below matters more on this generation than on any other — the hardware is fully open and the files are the scarce part.

If you are not certain what is in front of you, run the control-board identifier first; it works even on a dead board. Board internals are in the ASIC control board reference.

The firmware options

Dev-fee figures below are each vendor’s own published number, checked August 2026 — ranges are printed as ranges, not flattened, and a pool fee is never presented as a dev fee.

DCENT_OS on the S17 and T17, stated exactly. D-Central’s own firmware is the only fully open-source option on this table — GPL-3.0 end to end, where Braiins OS+’s mining binary is closed and VNish and LuxOS are closed. It registers board targets for the whole am2 generation, and every one of them is management-only: the hash boards are not energised. The source comment on the family reads “S17 family — management-only until promotion”. There is no S17 or T17 install, the loader refuses the target before it dispatches, and exactly one board target in the entire tree is open for a public-beta first install — the Antminer S9, not anything on this page. If you own an S17 and want to run open-source firmware today, the honest answer is Braiins OS+’s SD image, and we will say so on our own page rather than sell you a roadmap. Where our firmware does run, and on what evidence, is on the DCENT_OS pages.

One consumer-protection note that belongs on every firmware page, and it applies hardest to abandoned hardware: VNish’s own FAQ warns that “free / no-devfee” builds of its firmware circulating on lookalike domains are fake and may carry hidden fees. Old machines attract exactly that kind of re-hosting. Download only from a vendor’s own listed domains, and verify what you downloaded: how to verify mining firmware authenticity and the mining firmware security guide.

Install reality

Scope note: each vendor documents its own procedure, and the vendor’s document outranks this page for the vendor’s image.

What we hold, and what we do not

D-Central keeps an archive of older images and manufacturer service documents for bench work. It is a mirror, not an official channel, it is excluded from search indexes, and it exists because this hardware outlives its vendor download pages. Every file carries a published SHA-256 and an honest provenance record — including Source: Unknown on 107 of the 112 files, because we could not establish where they came from and saying so is the point. What we can establish is what each file attests about itself, read from inside the file rather than guessed from its name.

This generation is the deepest part of that archive: nineteen binaries and ten manufacturer PDF records.

What we do not hold: any current build from any vendor. Everything above is an archival copy from 2019–2022, kept because the machines outlived the pages that used to serve them. For a current image, use Braiins’ SD download or VNish’s own site, both linked in the options table. The full record, filterable by filename, hash or attested author, is on firmware mirror provenance.

When it stops being a firmware question

On seven-year-old hardware it very often is not a firmware question. A chain that reads zero after a reflash, a board that boots nothing, a unit that drops a hashboard under load — that is a bench job, and on this generation it is usually a solvable one. D-Central repairs the whole family at component level in Montreal: S17, S17+, S17e, T17, T17+ and T17e repair. If the control board is the casualty, identify it first, then match it against the control board parts category.

Record last verified: 2026-08-19.

Antminer S17 and T17 firmware questions

Which firmware can I run on an Antminer S17 or T17?

Three real options in 2026. Bitmain stock, which still exists as signed user-OM-…-sig packages and which we mirror for six of the seven models. Braiins OS+, which no longer lists this generation among supported devices but does still publish an SD-card image whose stated scope is exactly “S17, S17 Pro, S17+, S17e, T17, T17+, T17e” — that is the current vendor channel and the one to start with. And VNish, whose model menu names the S17, S17 Pro, S17+ and T17. LuxOS does not list this generation at all, and D-Central’s own DCENT_OS is management-only on every board target in the family — there is no S17 or T17 install.

Which ASIC chip is in an S17+ or a T17e?

The S17+ is BM1397 — the same chip as the plain S17, the S17 Pro, the T17 and the T17+. The T17e is BM1396, which is the “e” chip and only the “e” chip, shared with the S17e. BM1396 is not the “Plus” chip and it is not an S19-generation part. The two are register-compatible and share the 0x51/0x41 header family, which is why the confusion persists, but they are distinct silicon and are not interchangeable in a repair.

Can I still flash an S17 without a vendor’s remote install service?

Yes, and that is unusual now. The whole generation runs on the Xilinx Zynq am2 control board, which has a working SD-card slot and no Amlogic lock and no CVitek eMMC-first BootROM in the way. There is no March 2024 install lock on a 2019 machine. An S17 or T17 is one of the last Antminers you can recover and reflash entirely on your own bench with a card reader and the right image.

Does LuxOS support the Antminer S17?

Luxor’s own published compatibility table covers the S19 and S21 generations and carries no row for the S17, S17 Pro, S17+, S17e, T17, T17+ or T17e. We checked it in August 2026 and report that as an observed absence in the vendor’s documentation, not as a judgement — LuxOS is aimed at current fleet hardware, and this generation is not that.

Does D-Central host S17 and T17 firmware downloads?

We mirror nineteen binaries and ten manufacturer PDF records for this generation — the deepest part of our archive — each with a published SHA-256 and an honest provenance record. Six are Bitmain signed stock packages, four are VNish-attested 2.0.4-era builds, two are Braiins OS+ SD images whose OpenPGP signature is present but whose key we have not verified against a Braiins-published key, and the rest are SD recovery and bench-service sets. It is a mirror, not an official channel, and it is excluded from search indexes. For a current image, go to the vendor. The firmware we publish and maintain is our own: DCENT_OS, GPL-3.0, in public beta — and it does not run this generation.

Related pages

• Which Antminer control board do I have? — the identifier
• ASIC control board reference — the Xilinx Zynq am2 board
• ASIC chip reference — BM1396, BM1397 and the rest of the genealogy
• S17 in the miner database
• SD card firmware flashing & recovery guide
• Restore stock firmware on an ASIC miner
• Firmware mirror provenance — SHA-256 and attested origin for every file
• How to verify mining firmware authenticity
• Mining firmware security: official sources, verification & infection response
• ASIC firmware lock & security event tracker
• Mining firmware comparison: BraiinsOS+ vs VNish vs LuxOS
• Antminer S19j Pro firmware — the next generation’s decision layer
• Antminer S17 repair (Montreal bench)