Nextion's seven firmware files cannot be in the repo, so the repo now ships their SHA-256 hashes (src/nxhmi/firmware.sha256, Editor 1.68.2.3035) and every build checks the files against them. The files live in the git-ignored firmware/ folder; `nxhmi firmware --from <Editor folder>` copies them, `nxhmi firmware` reports ok / missing / wrong hash. build-tft and the MCP tool take --firmware-dir / firmware_dir (also NXHMI_FIRMWARE_DIR) instead of the Editor folder. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nextion firmware files (not in the repo)
Every .tft that Nextion Editor compiles embeds seven of Nextion's own firmware files. They are
Nextion's property, so this repo cannot ship them. To use nxhmi build-tft, copy them from your
own Nextion Editor installation into this folder. Git ignores everything here except this
README.
| File | |
|---|---|
input.bin, asp0.dll, cd0.dll, qr0.bin, syscom.bin, h0-0.dll, h1-0.dll |
from the Editor's install folder, usually C:\Program Files (x86)\Nextion Editor |
The .dll files are display firmware pieces, not Windows libraries.
Copy and check them in one step:
python -m nxhmi firmware --from "C:\Program Files (x86)\Nextion Editor"
python -m nxhmi firmware # check only: ok / missing / wrong hash per file
The builder checks every file against its SHA-256 in
src/nxhmi/firmware.sha256 before each build. The hashes belong to
Nextion Editor 1.68.2.3035, the version the builder was measured against. Files from another
Editor version are refused: they differ, and the output would no longer match what the Editor
produces. To check by hand: cd firmware && sha256sum -c ../src/nxhmi/firmware.sha256.
To keep the files elsewhere, pass --firmware-dir <folder> to build-tft or set
NXHMI_FIRMWARE_DIR.