[masarray]

Why

Public Waveshare ESP32-P4-ETH-M v3.2 feedback exposed a real silicon-revision incompatibility in the M3.H.3 pre-v3 firmware. Current Studio rightly blocks revision >= v3, but the distribution has no matching image.

Delivered

• PRD: electrical-engineer first, offline one-action setup/update/recovery UX; compact status, no jargon, no fake progress; U01–U14 acceptance.
• ARD: immutable separate pre-v3/v3.x binaries, typed manifest v2 with strictly compatible v1 reader, ROM revision + qualified board profile + image/header/SHA proof, reused SmartSessionController/FirmwareManager/FirmwareWorker ownership, fail-closed stage machine and 300-second total budget, true post-boot identity check, tested espflash v3.2 gate, v1.3/v3.2 physical evidence before stable.
• AGENTS: mandatory provisioning invariants, preventing naive 'toggle revision' fixes, unsafe retries or noisy QML workarounds.

Explicit safety and scope

• Docs only; does not claim v3.2 support is already implemented.
• Does not change binaries, source, timing, chip Kconfig, stable M3.H.3 assets/tags or other active M4 PRs.
• No automatic reset/flash on detection; no --force, erase-all, eFuse changes or auto retry after a partial write.
• User-confirmed interruption for running SV/PTP; exact-build postflight or explicit failure.
• Pinned Rust espflash v4.5.0 tested separately on v3.2; ESP-IDF Python esptool support is not assumed sufficient.
• Reuse existing CI routing, build outputs separated per silicon and exact-head packaging.

Vendor references

Espressif 2026 v3.2 PCN/advisory, ESP-IDF chip revision and esptool documentation, Waveshare dual-revision build guide, espflash v4.5 release evidence, NCSC firmware authentication guidance. Linked in documents.

Next engineering milestone: dual-profile firmware+Studio installer implementation with deterministic negative tests and separate v3.2 HIL preview; no modification of existing official stable artifacts.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-03T11:43:44.522317Z	179d760	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.