tft: firmware files from a local firmware/ folder, checked by SHA-256
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>
This commit is contained in:
1 parent
0287cf21e4
commit
85422a1ef4
14 files changed
+259
-44
No files matched your search
@@ -40,7 +40,9 @@ Back up the user's file first (copy it) unless they said not to; edits write in
|
||||
- `build_tft` compiles to `.tft` without the Editor's compiler, but only for model NX4832T035 and a
|
||||
small subset (pages, hotspots, plain text, int variables, timers, touch caps, pictures, fonts,
|
||||
plain script); it says
|
||||
what it cannot compile. It needs the Editor's install folder for the firmware files. Its
|
||||
what it cannot compile. It needs Nextion's seven firmware files in the repo's `firmware/` folder
|
||||
(git-ignored; the user copies them with `nxhmi firmware --from "<Editor folder>"`). Each build
|
||||
checks them against `src/nxhmi/firmware.sha256` and refuses missing or other-version files. Its
|
||||
output is byte-identical to the Editor's for the test projects but has never been loaded onto
|
||||
a display -- tell the user, and never upload it yourself.
|
||||
- Pictures: `add_picture` returns an id for `pic` / `picc` (crop) / `pic2` etc. Works for Basic
|
||||
|
||||
Reference in new issue
Block a user