Kaj SchittecatandClaude Opus 5
7ce1b3f48c
beta_86 flipped the T-Display P4's default C6 backend to esp-hosted. Current V1 units ship the C6 with esp-hosted firmware and are fine; OLDER units still carry the factory ESP-AT firmware, and on those the SDIO stream never frames. That turned into a board that will not boot at all, reported by three people so far (#600 jalevdev, myshoeisonfire on Discord, and Kaj's own unit), each with the same signature: H_SDIO_DRV: len[25970]>max[1524] OR offset[25697] != exp[12], Drop Two separate things made a co-processor mismatch fatal, and both had to go. 1. The UI was behind the C6. hostedInitBLE() ran unconditionally at setup, a hosted handshake, with ui_task.begin() ~80 lines later. The LEGACY backend always started its worker AFTER the UI, which is exactly why a dead C6 used to cost Wi-Fi and nothing else; the hosted path was wired in ahead of it. Both backends now start at the end of setup, after the UI, with a note saying nothing C6-dependent may move above it. 2. esp-hosted resets the host. CONFIG_ESP_HOSTED_HOST_RESTART_NO_COMMUNICATION_ WITH_SLAVE=n covers one path; the one that actually fires is H_TRANSPORT_RESTART_ON_FAILURE in sdio_drv.c, about 10 s after the connect attempt, and it is on by default. Now off. The failure still arrives as ESP_HOSTED_EVENT_TRANSPORT_FAILURE, which is what an application should act on instead of the transport rebooting the board underneath it. Measured on an ESP-AT unit, 45 s captures, same hardware: as shipped 5 resets, host restarts, UI never appears reorder only 2 resets, host restarts, UI appears then dies reorder + config 0 resets, 0 restarts, UI stays up The C6 is still unreachable on that unit, as it must be - it is the wrong firmware for it. It now costs Wi-Fi and BLE and nothing else. Also here, both needed before this can ship: * The ESP-AT build gets its own artifact name (tdisplay-p4-at, and the matching -lcd/-lr2021 combinations). Both backends used to answer "tdisplay-p4", so an ESP-AT unit's self-update would have fetched the hosted bin and put itself straight back into the loop, recoverable only over USB. That is the T-Deck Max bug again (a Max self-updating to Pro firmware) and would have been the fourth time this table shipped wrong. * The keyboard expansion probe prints a one-shot bus scan. "It does not work" has three causes that are indistinguishable from outside: not clipped on, clipped on but unpowered, or present and failing bring-up. An unpowered board does not NACK cleanly either - its pull-ups are dead, the lines sit low through its ESD diodes, and every transaction returns ESP_ERR_INVALID_STATE, which reads like a driver fault. The scan says which it is in one line. Co-Authored-By: Claude Opus 5 <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, Heltec V4 + TFT and other boards (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
See DEVICES.md for the full support matrix, install paths and per-board status.
- LilyGo T-Deck / T-Deck Plus — env
LilyGo_TDeck_companion_radio_touch(stable) - Heltec V4 + TFT + CHSC6x touch — env
heltec_v4_tft_companion_radio_usb_tcp_touch(stable) - Tanmatsu (ESP32-P4) — built from
tanmatsu/(ESP-IDF), ships via the Tanmatsu app store — sideload guide for running your own build - Elecrow ThinkNode M9 — env
ThinkNode_M9_companion_radio_touch(beta) — keyboard & d-pad guide - RAK WisMesh Tap V2 (RAK3312) — env
rak_tap_v2_companion_radio_touch(beta) - LilyGo T-Lora Pager — envs
tlora_pager_lr1121_companion_radio_touch/tlora_pager_sx1262_companion_radio_touch(beta) — keyboard shortcuts - Heltec V4-R8 + Expansion Kit V2 — env
heltec_v4_r8_tft_companion_radio_usb_tcp_touch(beta) - LilyGo T-Display P4 — built from
tdisplay_p4/(ESP-IDF); AMOLED + SX1262 by default, withWADA_P4_LCD=1for TFT-LCD andWADA_P4_LR2021=1for LR2021 (beta) - Attaky Mesh Series — env
attaky_mesh_series_companion_radio_touch(beta) - Elecrow CrowPanel Advance 3.5 — env
crowpanel_35_companion_radio_touch(beta, hardware validation pending; requires an SX1262 in the expansion slot)
Architecture
This repo holds only the app: the companion_radio glue, the ui-touch
LVGL UI, each board's 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.
Lua apps use the on-device SDK described in LUA_APPS.md. For WAV/MP3 playback, including a ready-to-sideload transport test app and exact SD and internal-storage paths, see AUDIO_PLAYBACK_TESTING.md. Region discovery, known-region management, and per-channel flood scopes are described in REGIONS.md.
Offline map tiles
Builds with a microSD card expose a Transfer app for authenticated browser
uploads over the local Wi-Fi network. WadaMesh accepts unpacked 256x256 PNG XYZ
tiles in a z/x/y.png directory tree.
To create a compatible pack with QGIS:
- Add a map source whose licence and service terms explicitly permit offline
or bulk use. A self-hosted source is also suitable. Do not bulk-download
from
tile.openstreetmap.org: the official OSM tile policy prohibits offline downloads from that community service. - Frame only the area needed in the QGIS map canvas. Tile counts quadruple at every added zoom level, so a small region and a practical range such as zoom 8 through 16 are preferable to exporting an entire country at zoom 19.
- Open Processing Toolbox → Raster tools → Generate XYZ tiles (Directory).
- Use the map-canvas extent, choose minimum and maximum zooms within 3–19, select PNG, set tile width and height to 256, leave Use inverted tile Y axis (TMS conventions) disabled, and select an output directory.
- Confirm the output contains paths such as
12/2048/1362.png. If obtaining an existing pack instead, extract it first and confirm it has the same XYZ directory layout and that its provider permits offline use and redistribution.
To upload the pack:
- Connect the device and the browser to the same Wi-Fi network.
- Open Transfer from the device's app drawer, visit the displayed URL, and enter the six-digit session code.
- Choose Offline OSM map (/tiles), select the generated output folder, and start the upload. The browser ignores unrelated files and uploads valid tiles sequentially while preserving their coordinates.
- Existing tiles are skipped by default, allowing an interrupted upload to be resumed. Enable Replace existing map tiles when intentionally refreshing a pack.
- Close Transfer after completion. In Map options, disable Topographic map and enable Tiles from SD card. Disable Wi-Fi to verify that the uploaded area renders offline.
Individual PNG tiles must be no larger than 256 KB. Keep the map provider's required attribution and licence information with any pack you distribute.
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
pio run -e crowpanel_35_companion_radio_touch # CrowPanel Advance 3.5
# or just `pio run` to build the configured default environments
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.