Commit Graph

3 Commits

Author SHA1 Message Date
ruv 786e834dae release(firmware): refresh release_bins with the #893 CSI fix → v0.6.7
The pre-built binaries in release_bins/ were v0.6.6 (May 21) and shipped
the MGMT-only promiscuous filter, so display-less boards flashed from them
got yield=0pps (#893/#866/#897 — the root cause of the "can't reproduce /
it's fake" reports). Rebuilt every flashable variant from main (which has
the #893 display-gated DATA-frame fix) and refreshed the binaries:

- top-level ESP32-S3 8MB (sdkconfig.defaults) — esp32-csi-node.bin +
  bootloader (partition-table/ota_data unchanged — code-only fix)
- esp32-csi-node-4mb.bin (ESP32-S3 4MB, sdkconfig.defaults.4mb)
- c6-adr110/ (ESP32-C6, sdkconfig.defaults.esp32c6) — the exact firmware
  hardware-verified on COM6 (CSI yield 0→27 pps, presence/motion alive,
  no #396 crash)
- s3-adr110/ (same production S3 8MB config)

Left untouched: s3-fair-adr110/ (a non-production size-comparison build,
features stripped — not a board anyone flashes for sensing).

version.txt → 0.6.7; SHA256SUMS regenerated for the changed variant dirs.
Display boards keep MGMT-only (preserves the #396 crash protection);
display-less boards now capture DATA frames and stream CSI.

Co-Authored-By: claude-flow <ruv@ruv.net>
2026-06-02 11:18:03 +02:00
ruv c58f49f21a fix(firmware): add vTaskDelay(1) yields in process_frame() at tier>=2 to fix WDT storm (#683)
At edge tier>=2 on N16R8 PSRAM boards, `process_frame()` runs
`update_multi_person_vitals()` (4 persons × 256 history samples) plus
`wasm_runtime_on_frame()` back-to-back before returning to `edge_task()`.
The existing `vTaskDelay(1)` in `edge_task()` only fires *after*
`process_frame()` returns — under sustained 30 pps CSI load on PSRAM
boards this leaves IDLE1 on Core 1 starved long enough for the 5-second
Task Watchdog Timer to fire.

Fix: add two `vTaskDelay(1)` calls inside `process_frame()`, both gated
on `s_cfg.tier >= 2`:
1. After `update_multi_person_vitals()` (Step 11)
2. After `wasm_runtime_on_frame()` dispatch (Step 14)

Tier 0/1 paths are unaffected. Validated on COM7 (N16R8 board):
`Edge DSP task started on core 1 (tier=2)`, no WDT panics in 20 s.

Also bump firmware version 0.6.5 → 0.6.6 and refresh all 6 release_bins
with the new build (8MB + 4MB variants, built 2026-05-21).

Fix-marker RuView#683 added to scripts/fix-markers.json.

Co-Authored-By: claude-flow <ruv@ruv.net>
2026-05-21 09:20:21 -04:00
rUv aeb69315d8
fix(firmware): refresh release_bins to v0.6.5 — fixes node_id=1 on all nodes (#679)
release_bins/ was built from v0.4.3.1 and predated the early-capture
node_id fix (PRs #232/#375/#385/#390). Every device flashed from those
binaries emitted node_id=1 regardless of provisioned ID, making
multi-node deployments appear as a single node.

Changes:
- Rebuild all 6 release_bins/ binaries from v0.6.5 source (2026-05-20)
  - esp32-csi-node.bin (8 MB, 1,110,384 bytes)
  - esp32-csi-node-4mb.bin (4 MB, 894,352 bytes)
  - bootloader.bin, partition-table.bin, partition-table-4mb.bin, ota_data_initial.bin
- Add release_bins/version.txt (0.6.5 / git-sha: d72e06fc8)
- README: add Step 0 "Pre-built binaries" flash command with version reference;
  update expected boot output to show early-capture log line
- provision.py: fix write-flash → write_flash (esptool v4.10+ underscore API)

Validated on real hardware (COM7 — ESP32-S3 N16R8, node_id=2):
  I (396) csi_collector: Early capture node_id=2 (before WiFi init, #232/#390)
  I (406) main: ESP32-S3 CSI Node (ADR-018) — v0.6.5 — Node ID: 2

Closes #679
2026-05-20 15:01:56 -04:00