Repository navigation
feat(build): release LilyGo T-Echo and T-Echo Card companions - #16
Merged
Merged
Conversation
Elektr0Vodka
force-pushed
the
Feat/techo-companion
branch
from
October 18, 2026 16:30
17c5884 to
d506d99
Compare
Add LilyGo_T-Echo_companion_radio_ble and _usb to the meshcomod release list so CI builds and publishes them (.uf2 and DFU .zip). Like the Wio Tracker L1 the T-Echo is an nRF52840 without Wi-Fi, so these are the stock single-transport companions with no TCP, SNMP or manifest OTA. The e-ink ui-new UI, CAD toggle and receive filter are included. Both envs build locally: BLE uses 56.5% of flash, USB 55.7%.
ui-tiny's UITask still took a MultiSerialInterface*, the type from upstream MeshCore 1.18. meshcomod's main.cpp passes the board's own serial interface and ui-new takes a BaseSerialInterface*, so the LilyGo T-Echo Card companions (the only ui-tiny users) failed with "no matching function for call to UITask::UITask". Take the base type like ui-new does. Built: LilyGo_T-Echo_Card_companion_radio_ble (flash 52.6%, RAM 45.5%) and _usb (flash 51.8%, RAM 43.7%).
Add LilyGo_T-Echo_Card_companion_radio_ble and _usb to the release list now that ui-tiny builds again. Same single-transport nRF52840 setup as the T-Echo, with the ui-tiny UI and its CAD page.
Elektr0Vodka
force-pushed
the
Feat/techo-companion
branch
from
October 18, 2026 16:32
d506d99 to
4a0745e
Compare
Elektr0Vodka
added a commit
that referenced
this pull request
Oct 18, 2026
After #16, #17 and #18: - README: the multi-transport claim only holds for the Wi-Fi boards; add how to flash the nRF52 boards (.uf2, DFU .zip); describe nRF52 build outputs and warn that DISABLE_DEBUG=1 breaks nRF52 builds. - CAD toggle doc: the per-UI board examples now name the released boards (ui-new on the display usb_tcp boards, Wio Tracker L1 and T-Echo; ui-tiny on the T-Echo Card; ui-orig on the ThinkNode M7). - Changelog: tag the Unreleased entries with the PR that landed them.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Release the LilyGo T-Echo and T-Echo Card companions from this fork:
LilyGo_T-Echo_companion_radio_ble/_usbjoinMESHCOMOD_COMPANION_ENVS.LilyGo_T-Echo_Card_companion_radio_ble/_usbjoin it too, after a fix to the ui-tiny UI: itsUITaskstill took the upstream 1.18MultiSerialInterface*, while meshcomod'smain.cpppasses the board's own serial interface. It now takesBaseSerialInterface*like ui-new.docs/CI_RELEASES.mdandchangelog_ev.mdupdated.Why
Both are nRF52840 boards with existing upstream envs. Like the Wio Tracker L1 (#14), they have no Wi-Fi, so they get the stock single-transport companions (one image for BLE, one for USB) with no TCP, SNMP or manifest OTA. The CAD toggle and receive filter live in the shared companion code and build in. The T-Echo uses the e-ink ui-new UI, the Card the ui-tiny UI with its CAD page.
Testing
Built locally with
build.sh build-firmware(noDISABLE_DEBUG, see note):LilyGo_T-Echo_companion_radio_bleLilyGo_T-Echo_companion_radio_usbLilyGo_T-Echo_Card_companion_radio_bleLilyGo_T-Echo_Card_companion_radio_usbEach produces
.uf2+ DFU.zip. Not tested on hardware.Firmware and build impact
Four new release artifacts per companion release. No change to existing boards; the ui-tiny change only affects the T-Echo Card.
Note:
DISABLE_DEBUG=1breaks every nRF52 build (build.shpasses-UCFG_DEBUG, which the Adafruit core'srtos.cppneeds). The companion CI workflow does not set it, so CI is unaffected.Merge note: this PR, the classic ESP32 fix and the 16 MB S3 boards PR all touch
changelog_ev.md, and the two board PRs also touchbuild.sh, README anddocs/CI_RELEASES.md. Whichever merges second gets rebased.