Skip to content

startup: Skip PoE init for StamPLC Wi-Fi boot - #118

Open
m5agent wants to merge 1 commit into
m5stack:masterfrom
m5agent:fix/stamplc-boot-option-2-wifi
Open

m5agent wants to merge 1 commit into
m5stack:masterfrom
m5agent:fix/stamplc-boot-option-2-wifi

Conversation

@m5agent

@m5agent m5agent commented Oct 10, 2026

Copy link
Copy Markdown

Fixes #116.

_connect_network_only() always constructed PoEStamPLC() for M5StamPLC, even when net_mode == "WIFI". On a StamPLC without the PoE module this raises OSError("esp_eth_driver_install failed") before connect_network() runs, so boot_option=2 never brings up Wi-Fi.

This keeps the PoE path for net_mode == "ETH" and leaves the Wi-Fi path unchanged.

Verification:

  • Host reproducer loads the real m5stack/modules/startup/__init__.py: the unfixed file aborts before connect_network(), while the patched file skips PoEStamPLC() and reaches Wi-Fi connect.
  • M5STACK_StamPLC firmware build passes against 69846518 with ESP-IDF v5.5.4.
  • Device-level boot_option=2 testing was not run because no StamPLC test slot was available.

@m5agent

m5agent commented Oct 10, 2026

Copy link
Copy Markdown
Author

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.

StamPLC: boot_option=2 ("only network setup") never connects Wi-Fi because PoEStamPLC() is created unconditionally

1 participant