Stabilize T-Beam full companion startup

This commit is contained in:
mikecarper
2026-08-16 11:00:55 -07:00
parent bcedfdd019
commit a514b2a6d5
8 changed files with 138 additions and 48 deletions
+6 -5
View File
@@ -181,11 +181,12 @@ service on ports 5001 and 5002. See the
[full Companion guide](./companion_radio_full.md) for its build, terminal mode,
and complete update-source workflow.
The LilyGo T-Beam 1W Full Companion maps a triple click of the physical button
labeled `17` to a persistent WiFi on/off toggle. Turning WiFi off closes the
WebConfig, Companion TCP, mOTA, and MQTT network services while USB, BLE, the
display, GPS, and LoRa remain available. The same triple click turns WiFi back
on even after reboot.
The LilyGo T-Beam 1W Full Companion maps one press of the physical `BOOT` button
(GPIO0) to a persistent WiFi on/off toggle. Turning WiFi off closes WebConfig,
Companion TCP, mOTA, and MQTT network services while USB, BLE, the display, GPS,
and LoRa remain available. Another BOOT press turns WiFi back on even after
reboot. WiFi/WebConfig starts first; BLE starts two seconds later so the ESP32-S3
can reserve the setup server's internal heap before both radios run together.
The companion loads runtime credentials saved in NVS. A non-placeholder
compile-time `WIFI_SSID`/`WIFI_PWD` can be used as a first-boot fallback, but
+15 -12
View File
@@ -80,21 +80,24 @@ clock and keeps GPS awake. Full Companion transports remain available in both
states; WiFi modem sleep stays enabled when BLE is present because coexistence
requires it. The selected state is retained after reboot.
On the LilyGo T-Beam 1W Full Companion, triple-click the physical button
labeled `17` to turn the ESP32 WiFi radio and all WiFi services off or on. The
screen confirms `WiFi: OFF` or `WiFi: ON`, and the selected state is retained
after reboot. When WiFi is off, TCP ports 5000-5002, WebConfig, and MQTT are
stopped; USB, BLE, the display, GPS, and LoRa continue to operate. Triple-click
button 17 again to restore WiFi, including the saved station or setup-AP mode.
On the LilyGo T-Beam 1W Full Companion, press the physical `BOOT` button once
to turn the ESP32 WiFi radio and all WiFi services off or on. The screen confirms
`WiFi: OFF` or `WiFi: ON`, and the selected state is retained after reboot. When
WiFi is off, TCP ports 5000-5002, WebConfig, and MQTT are stopped; USB, BLE, the
display, GPS, and LoRa continue to operate. Press BOOT again to restore WiFi,
including the saved station or setup-AP mode. On boot, BLE starts two seconds
after WiFi/WebConfig so their peak startup allocations do not overlap.
Artifacts are written to `out/` by default.
On 4 MB ESP32 boards, the full target uses a single 3 MB application
partition so WiFi, BLE, WebConfig, and source-only mOTA fit together. Flash
the generated `-merged.bin` when first installing this partition layout.
Boards with 8 MB or more retain dual application partitions. Heltec V2 and
TLora V2 use 100 contacts, 8 group channels, and a 16-frame offline queue in
this combined profile because of internal DRAM limits.
On 4 MB ESP32 boards, the full target uses a single 3 MB application partition
so WiFi, BLE, WebConfig, and source-only mOTA fit together. The T-Beam 1W Full
Companion uses that same LilyGo factory-compatible boot layout on its 16 MB
flash because this source-only role does not install updates into a second app
slot. Flash the generated `-merged.bin` when first installing this partition
layout. Other boards with 8 MB or more retain dual application partitions.
Heltec V2 and TLora V2 use 100 contacts, 8 group channels, and a 16-frame offline
queue in this combined profile because of internal DRAM limits.
The nRF52 target inherits the board's ordinary USB Companion installation
format and adds BLE plus the serial mOTA source. It does not enable an SD cache