Skip to content

ROM log early boot crash workaround#323

Open
SukuWc wants to merge 1 commit into
mainfrom
SUKU-rom-log-boot-patch
Open

ROM log early boot crash workaround#323
SukuWc wants to merge 1 commit into
mainfrom
SUKU-rom-log-boot-patch

Conversation

@SukuWc

@SukuWc SukuWc commented Feb 17, 2026

Copy link
Copy Markdown
Member

Summary

Test plan

ROM log workaround with fresh boards

  • First boot on fresh chip (eFuse not yet burned)
  • Subsequent boots (eFuse already burned to GPIO_HIGH)
  • Verify ROM logs are suppressed after first boot

ROM log workaround with known incorrectly configured boards

  • Boot on board with eFuse burned incorrectly to GPIO_LOW
  • Verify that board boots with the current firmware build

🤖 Generated with Claude Code

@SukuWc SukuWc force-pushed the SUKU-docker-ci-build-fixes branch from 9a936b9 to 769c2e8 Compare February 17, 2026 08:44
@SukuWc SukuWc force-pushed the SUKU-rom-log-boot-patch branch from dd57080 to b1c8542 Compare February 17, 2026 08:44
@SukuWc SukuWc changed the base branch from SUKU-docker-ci-build-fixes to main July 1, 2026 13:55
Port to post-restructure layout (esp32s3/). Replace the build-time
esp_efuse_startup.c patch with a runtime call to
esp_efuse_set_rom_log_scheme() in app_main, and flip sdkconfig to
CONFIG_BOOT_ROM_LOG_ALWAYS_ON=y to avoid esp-idf#12894.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@SukuWc SukuWc force-pushed the SUKU-rom-log-boot-patch branch from b1c8542 to 7802eac Compare July 1, 2026 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant