Kaj SchittecatandClaude Opus 4.8
b986f49e1a
the_mesh was the single biggest static internal-DRAM consumer at 42 KB (dominated by the MAX_CONTACTS=100 ContactInfo array inside it). Internal DRAM (~320 KB) is the scarce resource on the ESP32-S3 — Wi-Fi/BLE DMA + heap fight over it, and the V4 was hitting ~99% on map-tile load (issue #47b). PSRAM (8 MB) is plentiful. Place the whole the_mesh object in PSRAM via placement-new into a heap_caps_malloc (MALLOC_CAP_SPIRAM) block and bind a reference, so every the_mesh.foo() call site is unchanged. The constructor still runs at the SAME static-init point as the old direct global (PSRAM is already up then), so timing and behaviour are identical; only the address moves off internal DRAM. Falls back to internal RAM if PSRAM is absent. ESP32-only (STM32/RP2040 keep the plain global). The contacts array rides along inside the object — no vendored-core change. Measured on heltec_v4 (.dram0.bss): 124160 -> 82000 B = ~41 KB internal DRAM freed. Verified on the T-Deck: clean boot, [BOOT] mesh ok, reason=0, zero panic markers. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
A real touchscreen UI for your mesh radio. · open source · GPL-3.0
Touch-UI MeshCore companion-radio firmware for the LilyGo T-Deck / T-Deck Plus and Heltec V4 + TFT (ESP32-S3).
An LVGL touch UI — map, chat, contacts, channels, settings — split out of
meshcomod. The app depends on a
MeshCore fork via PlatformIO lib_deps.
Boards
- LilyGo T-Deck / T-Deck Plus — env
LilyGo_TDeck_companion_radio_touch - Heltec V4 + TFT + CHSC6x touch — env
heltec_v4_tft_companion_radio_usb_tcp_touch
Architecture
This repo holds only the app: the companion_radio glue, the ui-touch
LVGL UI, the two boards' glue/variants, and platformio.ini. The MeshCore
core is not vendored here — it's pulled as a library via lib_deps from the
ALLFATHER-BV/meshcomod monorepo
(the same repo as the non-touch firmware), pinned by a lean source-only core-*
git tag. The touch-app files this repo owns (TouchPrefsStore, WifiRuntimeStore,
the transports, …) are dropped from the lib via -DMC_VENDORED_TOUCH_APP so they
aren't compiled twice. The build is byte-identical to the original in-tree
meshcomod firmware.
Build
PlatformIO pulls the core fork and all libraries automatically:
pio run -e heltec_v4_tft_companion_radio_usb_tcp_touch # Heltec V4 TFT
pio run -e LilyGo_TDeck_companion_radio_touch # LilyGo T-Deck
# or just `pio run` to build both
Flash with the NVS-preserving 4-component chain (bootloader / partitions /
boot_app0 / firmware at 0x0 / 0x8000 / 0xe000 / 0x10000) so saved Wi-Fi
credentials survive — not a merged image, which 0xFF-pads and wipes NVS.
Contributing
Contributions are welcome — see CONTRIBUTING.md. One topic per PR; inbound contributions are accepted under the project's GPL-3.0 license.
License
GPL-3.0-or-later — see LICENSE. wadamesh is copyleft: anyone who distributes a build or a fork must also make their source available under the GPL. This keeps the UI open and concentrates community effort instead of fragmenting it into closed forks.
wadamesh incorporates and depends on MeshCore (MIT, © Scott Powell / rippleradios.com) and other third-party components — see NOTICE for the full list and their licenses. MeshCore-derived files keep their MIT notices; the combined work is distributed under the GPL (MIT is GPL-compatible). The MeshCore fork that wadamesh builds against stays MIT on purpose, so its Wi-Fi/BLE hooks remain upstreamable to MeshCore.