Skip to content

Pin ESP-IDF to v6.1-beta1 (ride the betas toward v6.1 GA)#40

Merged
ewowi merged 1 commit into
mainfrom
idf-v6.1-beta1
Jul 7, 2026
Merged

Pin ESP-IDF to v6.1-beta1 (ride the betas toward v6.1 GA)#40
ewowi merged 1 commit into
mainfrom
idf-v6.1-beta1

Conversation

@ewowi

@ewowi ewowi commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

What

Moves the pinned ESP-IDF from the rolling release/v6.1 branch commit (v6.1-dev-5215, 2026-06-08) to the tagged v6.1-beta1 pre-release (commit b1d13e9f, 2026-06-24, +168 commits). Both local (setup_esp_idf.py) and CI (the esp-idf-ci-action Docker tag in release.yml) move together, so the two build environments stay identical.

Why

Ride the tagged betas toward v6.1 GA (targeted late July 2026) rather than jumping straight from the dev branch to GA. This surfaces any breakage from the v6.1 delta incrementally — one beta at a time — instead of all at once at the GA re-pin, and swaps a moving branch tag for a fixed, signed pre-release pin.

Verified locally (macOS, against the real beta1 toolchain)

Variant Result
esp32 (classic) ✅ builds clean, 17% app free — no API breakage across the 168-commit delta
esp32p4-eth-wifi ✅ builds clean, 60% free — esp_hosted + esp_wifi_remote compile + link
esp32p4-eth runtime (P4-NANO) ✅ boots clean, 139 FPS on Ethernet

P4-WiFi boot crash (esp-idf #18759) — still present on beta1

The P4-WiFi variant was flashed to the P4-NANO on beta1 and still bootloops with the known upstream crash, verbatim:

sleep_clock: sleep_clock_icg_init(142): failed to allocate memory for system sleep clock ICG
cpu_start: init function 0x400f7d74 has failed (0x101), aborting  →  reboot loop

Expected: the beta1 delta's sleep-retention commits are ESP32-S31-specific, and pmu_sleep_clock_icg.c (the crashing file) is unchanged. The CONFIG_PM_ENABLE-gating fix #18759 needs has not landed. So esp32p4-eth-wifi stays held out of the release matrix; only esp32p4-eth ships for the P4. This PR does not change that — it's a build-de-risking pin bump, not a P4-WiFi fix.

What CI validates here

release.yml (triggered by this PR touching .github/workflows/release.yml + moondeck/build/**) builds every ships=True variant against the v6.1-beta1 Docker image — the CI-side confirmation of the local macOS builds above.

Notes

  • The eventual v6.1 GA re-pin is a separate deliberate re-test pass (per docs/building.md § ESP-IDF version).
  • No src/ changes — this is purely the IDF pin (setup script, CI Docker tag, building.md).

🤖 Generated with Claude Code

Moves the pinned ESP-IDF from the rolling release/v6.1 branch commit (v6.1-dev-5215, 2026-06-08) to the tagged v6.1-beta1 pre-release (commit b1d13e9f, 2026-06-24, +168 commits). Riding the tagged betas toward v6.1 GA surfaces any breakage from the v6.1 delta incrementally rather than all at once at the GA re-pin, and gives a fixed, signed pin for both local and CI instead of a moving branch tag.

Not yet built or hardware-tested against beta1 — this commit only moves the pin; the ESP32 build + full hardware re-test pass (all variants) runs against the beta1 toolchain before this merges. Known open question: the P4-WiFi boot crash (esp-idf #18759, sleep_clock_icg_startup_init OOM) — the beta1 delta's sleep-retention commits are ESP32-S31-specific, not P4, and pmu_sleep_clock_icg.c is unchanged, so beta1 is unlikely to fix it; a bench try on the P4-NANO confirms either way.

Scripts / MoonDeck:
- setup_esp_idf.py: PINNED_IDF_COMMIT / PINNED_IDF_VERSION → b1d13e9f / v6.1-beta1; the drift-recovery hint fetches the tag instead of the branch.

Docs / CI:
- release.yml: the esp-idf-ci-action Docker tag release-v6.1 → v6.1-beta1 (a fixed signed image, so CI and local build the identical tree, not the rolling branch tag); cache key bumped to invalidate.
- building.md: the clone commands, the tested-version line, and the § ESP-IDF version rationale updated for the beta1 tag pin and the ride-the-betas-to-GA strategy.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 35356121-da89-4a71-86fc-9674c9f7a7c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch idf-v6.1-beta1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ewowi ewowi merged commit 3724c4f into main Jul 7, 2026
5 of 15 checks passed
@ewowi ewowi deleted the idf-v6.1-beta1 branch July 7, 2026 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ESP32-P4: sleep_clock_icg_startup_init aborts with ESP_ERR_NO_MEM when CONFIG_PM_ENABLE is disabled (IDFGH-17859)

1 participant