ruvnet/RuView v0.8.14-esp32

ESP32 firmware v0.8.14-esp32

on GitHub

ESP32 firmware 0.8.14 prerelease

This maintenance release fixes the ESP32-C6 onboarding device digest and adds explicit OTA key provisioning. It integrates the reviewed firmware changes in PR #2247.

• Onboarding now reads the six-byte base MAC through the matching ESP-IDF API and retains PSA SHA-256 hashing. The previous API could write eight bytes on C6/H2.
• provision.py --ota-psk-file PATH accepts a 64-character hexadecimal OTA key. The host cache records only whether OTA was configured. Resupply the key when rewriting a configured board's NVS, or explicitly use --clear-ota-psk to disable OTA.
• Legacy cached OTA keys are hidden during inspection and removed on the next successful state write. NVS provisioning still replaces the entire partition; consult the firmware README before provisioning an existing board.
• Download guidance now distinguishes the supported board variants and historical checked-in binaries.

The release workflow builds and packages ESP32-S3 display (8 MB), ESP32-S3 headless (4 MB), and ESP32-C6 (4 MB) bundles from this exact tag. Check the outer archive SHA256SUMS.txt and the extracted bundle's SHA256SUMS.txt before selecting or flashing images. The workflow checks the built application version against version.txt.

Qualification: CI builds and host regression tests only. This prerelease has no new physical-board qualification, sensing-accuracy result, or performance claim. A successful build is not proof of operation on a particular board.

Build provenance: Firmware CI run 38276415438, from merge commit 441349137008ce30ec0f147ccba0d4aaf65ddee5. The published archives were downloaded and verified against GitHub asset digests and both SHA-256 manifests; image headers, partition bounds, and application descriptors match the documented variants and version.

Toolkit compatibility: The published @ruvnet/ruview 0.9.2 was installed and checked against all three actual firmware release bundles using read-only flash plans. It resolved four checksum-verified images per bundle with the correct chip and flash size, including the C6-specific filenames. These checks did not access or flash hardware and do not constitute physical-board qualification.