DualMeck: Dualmesh Boot Loader Now Available #14
pelgraine
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Meck-P4 v0.7.1 + DualMesh: Dual-Boot for the T-Display P4
Run Meck and a second firmware on the same T-Display P4, switching between them from a touch menu -- no PC needed after the first flash. This release packages Meck-P4 v0.7.1 for use with the DualMesh Boot Launcher, a fork of Mikhail-Za's DualMesh with the firmware-specific branding removed so any firmware can occupy either slot.
All of this has been tested on hardware: the launcher flashed via the MeshCore Web Flasher, and Meck installed from SD and booted alongside a second MeshCore firmware (Wadamesh) in the other slot.
What's in this release
Pick the Meck image matching your display SKU. Both are 6.24 MB and go in slot 0 (10.75 MB) -- they do not fit slot 1 (3.625 MB), which is free for a second, smaller firmware.
These app-only images are not interchangeable with the normal Meck release. The standard
meck-p4-0.7.1merged binary flashes a standalone device over USB and cannot be installed into a launcher slot; these app-only images install into a slot and cannot be flashed standalone at0x0. Same firmware, same v0.7.1 feature set (full release notes here), different packaging.Setting it up
1. Flash the launcher (once)
This erases the device, including a standalone Meck install and its NVS settings. If Meck is already on the device with history and settings you care about, take a full backup first -- the DualMesh README covers restoring it.
dualmesh-launcher-merged.binOr with esptool:
On macOS the T-Display P4 appears as
/dev/cu.wchusbserial*(not/dev/cu.usbmodem*) -- runls /dev/cu.*to find it. On Linux it is typically/dev/ttyACM0, on Windows a COM port likeCOM3. Use the right-side USB-C port (the data port).The launcher comes up with two slot cards, both
(empty).2. Install Meck from SD
firmwareat the rootA brief cyan flash of the screen when installing or switching firmware is normal.
3. Optionally, install a second firmware
Any app-only ESP32-P4 image that fits goes in slot 1 the same way. Wadamesh (3.21 MB) is confirmed working there. The DualMesh README explains what makes an image compatible and how to carve an app-only image out of another project's merged release.
Switching between firmwares
Once booted into Meck, the device stays in Meck across resets. To get back to the launcher:
tap anywhere for menuLet the countdown run out and it boots straight back into the last-used firmware, so day to day the launcher stays out of your way.
What to know before you rely on it
nvsregion after the initial flash, and installing to one slot does not affect the other./sdcard/firmware. It is also where Meck keeps message history, notes, and tones, so you want one regardless.Reporting Issues
The Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues work for anything reproducible -- say whether you are running standalone or under DualMesh, and which slot. Launcher-specific problems belong on the DualMesh fork's issues.
License
Meck-specific code is MIT; the combined Meck firmware binary is effectively GPL-3.0 when distributed. The DualMesh launcher is GPL-3.0.
# Meck-P4 v0.7.1 + DualMesh: Dual-Boot for the T-Display P4Run Meck and a second firmware on the same T-Display P4, switching between them from a touch menu -- no PC needed after the first flash. This release packages Meck-P4 v0.7.1 for use with the [DualMesh Boot Launcher](https://github.com/pelgraine/DualMesh-Boot-Launcher-for-LilyGo-T-Display-P4), a fork of [Mikhail-Za's DualMesh](https://github.com/Mikhail-Za/DualMesh-Boot-Launcher-for-LilyGo-T-Display-P4) with the firmware-specific branding removed so any firmware can occupy either slot.
All of this has been tested on hardware: the launcher flashed via the MeshCore Web Flasher, and Meck installed from SD and booted alongside a second MeshCore firmware (Wadamesh) in the other slot.
What's in this release
dualmesh-launcher-merged.bin0x0, oncev0_7_1-meck-tft.binv0_7_1-meck-amoled.binPick the Meck image matching your display SKU. Both are 6.24 MB and go in slot 0 (10.75 MB) -- they do not fit slot 1 (3.625 MB), which is free for a second, smaller firmware.
These app-only images are not interchangeable with the normal Meck release. The standard
meck-p4-0.7.1merged binary flashes a standalone device over USB and cannot be installed into a launcher slot; these app-only images install into a slot and cannot be flashed standalone at0x0. Same firmware, same v0.7.1 feature set ([full release notes here](https://github.com/pelgraine/Meck-P4/releases/tag/0.7.1)), different packaging.Setting it up
1. Flash the launcher (once)
This erases the device, including a standalone Meck install and its NVS settings. If Meck is already on the device with history and settings you care about, take a full backup first -- the DualMesh README covers restoring it.
dualmesh-launcher-merged.binOr with esptool:
On macOS the T-Display P4 appears as
/dev/cu.wchusbserial*(not/dev/cu.usbmodem*) -- runls /dev/cu.*to find it. On Linux it is typically/dev/ttyACM0, on Windows a COM port likeCOM3. Use the right-side USB-C port (the data port).The launcher comes up with two slot cards, both
(empty).2. Install Meck from SD
firmwareat the rootA brief cyan flash of the screen when installing or switching firmware is normal.
3. Optionally, install a second firmware
Any app-only ESP32-P4 image that fits goes in slot 1 the same way. Wadamesh (3.21 MB) is confirmed working there. The DualMesh README explains what makes an image compatible and how to carve an app-only image out of another project's merged release.
Switching between firmwares
Once booted into Meck, the device stays in Meck across resets. To get back to the launcher:
tap anywhere for menuLet the countdown run out and it boots straight back into the last-used firmware, so day to day the launcher stays out of your way.
What to know before you rely on it
nvsregion after the initial flash, and installing to one slot does not affect the other./sdcard/firmware. It is also where Meck keeps message history, notes, and tones, so you want one regardless.Reporting Issues
The Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues work for anything reproducible -- say whether you are running standalone or under DualMesh, and which slot. Launcher-specific problems belong on the DualMesh fork's issues.
License
Meck-specific code is MIT; the combined Meck firmware binary is effectively GPL-3.0 when distributed. The DualMesh launcher is GPL-3.0.
This discussion was created from the release DualMeck: Dualmesh Boot Loader Now Available.
All reactions