Preserve separate TLora Full transports within RAM budget
This commit is contained in:
1 parent
6765100c3a
commit
8d76923a4e
11 files changed
+207
-37
No files matched your search
@@ -620,6 +620,11 @@
|
||||
|
||||
return (profiles || []).filter(function (profile) {
|
||||
const target = String(profile && profile.target || "");
|
||||
// TLora cannot fit UART, MQTT and ESP-NOW together. Its normal Full
|
||||
// UART image and Full MQTT observer are both intentional choices.
|
||||
if (/^LilyGo_TLora_V2_1_1_6_repeater_observer_mqtt_?-full-usb-wifi$/i.test(target)) {
|
||||
return true;
|
||||
}
|
||||
// Same-partition ESP32 migrations publish the ordinary target's Full
|
||||
// image with its established mOTA identity. The former observer-named
|
||||
// Full image remains in the release for deployed devices that still use
|
||||
|
||||
@@ -49,8 +49,11 @@ The direct observer and Full-matrix paths use the same `full-usb-wifi-ota`
|
||||
artifact and runtime output controls. The ordinary bulk release publishes one
|
||||
Full OTA identity per exact ESP32 board and role. Audited plain targets keep
|
||||
their identity while compiling the combined observer/ESP-NOW sources; G2 keeps
|
||||
its deployed observer identity. T-Beam SX1262/SX1276 and TLora V2 choose the
|
||||
observer in the ordinary release. Their plain Full recipes remain available
|
||||
its deployed observer identity. T-Beam SX1262/SX1276 choose the observer in
|
||||
the ordinary release. TLora V2 retains two Full images because UART, MQTT
|
||||
and ESP-NOW together exceed its internal RAM budget: the normal repeater
|
||||
provides UART plus ESP-NOW, and the observer provides MQTT plus ESP-NOW.
|
||||
T-Beam plain Full recipes remain available
|
||||
as explicit alternatives with different routing capacities. Build one with
|
||||
`bash build.sh build-firmware <target> --full-exact`, then deliberately install
|
||||
it over LoRa with `ota pull <MID8> flash` and `ota install` on compatible
|
||||
@@ -204,10 +207,9 @@ available from a canonical image:
|
||||
target remains directly buildable with its bridge-on default but is omitted
|
||||
from bulk releases. Browser OTA pauses ESP-NOW while leaving RS-232 running;
|
||||
`stop ota` restores ESP-NOW when its saved setting is on.
|
||||
- Full Heltec V3, Wireless Stick Lite V3, RAK3112 and LilyGo T-LoRa V2.1-1.6
|
||||
MQTT repeaters retain RS-232 alongside MQTT and ESP-NOW. The first three
|
||||
use UART2 with RX on GPIO5 and TX on GPIO6; T-LoRa uses UART2 with RX on
|
||||
GPIO34 and TX on GPIO25. Use `set rs232.enabled on|off` and
|
||||
- Full Heltec V3, Wireless Stick Lite V3 and RAK3112 MQTT repeaters retain
|
||||
RS-232 alongside MQTT and ESP-NOW. They use UART2 with RX on GPIO5 and
|
||||
TX on GPIO6. Use `set rs232.enabled on|off` and
|
||||
`get rs232.running` independently of `mqtt.enabled` and `espnow.enabled`.
|
||||
`bridge.baud` and `bridge.uart` configure the UART. Old MQTT preferences
|
||||
do not enable this newly added UART; its saved intent needs a validated
|
||||
@@ -216,6 +218,12 @@ available from a canonical image:
|
||||
verifies the linked UART driver even when compiling observer sources for a
|
||||
normal repeater, and resumed release selection rejects Full images without
|
||||
that proof.
|
||||
- LilyGo T-LoRa V2.1-1.6 retains a normal Full UART/ESP-NOW repeater and a
|
||||
separate Full MQTT/ESP-NOW observer. Real triple-transport qualification
|
||||
fell 6,496 bytes short of the required internal heap, including the UART
|
||||
driver allowance. The normal UART remains on RX GPIO34 and TX GPIO25;
|
||||
use `bridge.enabled` or `rs232.enabled` to control it. Both Full identities
|
||||
remain in bulk releases instead of reducing routing capacity or RAM margins.
|
||||
- MeshTower V2 repeaters use
|
||||
`Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors` as the one
|
||||
canonical target. Its SD OTA target `0A9DBBF0`, hardware ID
|
||||
|
||||
@@ -26,7 +26,8 @@ Open each board's [USB console](https://flasher.meshcore.io/console) at
|
||||
get bridge.type
|
||||
```
|
||||
|
||||
The answer can be `espnow`, `mqtt+espnow`, or `rs232+espnow`. Confirm the
|
||||
The answer can be `espnow`, `mqtt+espnow`, `rs232+espnow`, or
|
||||
`mqtt+rs232+espnow`, depending on the image. Confirm the
|
||||
independent ESP-NOW control is present with `get espnow.enabled` and
|
||||
`get espnow.running`. The `espnow` commands select this transport without
|
||||
changing another bridge in a combined image.
|
||||
|
||||
@@ -208,9 +208,11 @@ supported, `set mqtt.enabled on|off` for MQTT. Newly combined ordinary
|
||||
repeaters start with ESP-NOW off until explicitly enabled, including the first
|
||||
upgrade from unmarked legacy preferences. Later reboots preserve that setting.
|
||||
On combined RS-232 boards without MQTT, `bridge.enabled` controls the UART.
|
||||
Full Heltec V3, WSL3, RAK3112 and T-LoRa V2.1 MQTT images also retain RS-232;
|
||||
Full Heltec V3, WSL3 and RAK3112 MQTT images also retain RS-232;
|
||||
use `set rs232.enabled on|off` and `get rs232.running` for their independent
|
||||
UART. MQTT and ESP-NOW use one 2.4 GHz radio, so when both are enabled the ESP-NOW bridge channel must
|
||||
UART. T-LoRa V2.1 keeps two Full choices due to its internal RAM limit:
|
||||
the normal repeater has UART plus ESP-NOW, and the observer has MQTT plus
|
||||
ESP-NOW. MQTT and ESP-NOW use one 2.4 GHz radio, so when both are enabled the ESP-NOW bridge channel must
|
||||
match the connected WiFi access point's fixed channel. ESP-NOW-only mode does
|
||||
not require WiFi credentials. Its runtime
|
||||
`bridge.format` setting chooses the peer protocol: `wrapped` (the
|
||||
|
||||
@@ -30,6 +30,10 @@ MQTT connections, OTA scratch and transient allocations. ESP32 images with
|
||||
RS-232 reserve another 8 KiB even when UART defaults off: 4 KiB for the
|
||||
source-bounded bridge object and 4 KiB for the UART driver and buffers. This
|
||||
keeps runtime UART enablement in the budget beside MQTT and ESP-NOW.
|
||||
T-LoRa V2.1-1.6 cannot fit all three transports: the qualified linked triple
|
||||
image had 190,488 available internal bytes against 196,984 required bytes.
|
||||
Its ordinary release retains separate UART/ESP-NOW and MQTT/ESP-NOW Full
|
||||
images; the memory policy and routing capacities remain unchanged.
|
||||
A 160x80 ST7735
|
||||
framebuffer needs 25,602 bytes; an OLED allowance is 4 KiB. nRF52 Full with that
|
||||
color framebuffer must have at least 72 KiB available before startup allocations.
|
||||
|
||||
Reference in new issue
Block a user