We’re collecting feedback from anyone working with mender-mcu on Zephyr (or considering it). The preview release uses ESP32-S3-DevKitC as the reference platform and has generic support for MCUboot-compatible boards, and we want to understand what matters most to you. Whether that’s resource constraints, networking, integration, or something we haven’t thought of yet.
Two quick polls, then feel free to elaborate in the replies.
What are your biggest challenges running Mender on MCUs?
- Flash/RAM budget — not enough room for the update client and my application
- Network stack size — TCP/TLS takes too much of my resources
- Partition layout — getting MCUboot slots right is painful
- Artifact size constraints — images are too large for my flash layout
- Network reliability — managing connectivity and retries on constrained links
- Integration with Zephyr — build system, Kconfig, dependencies
- Testing and debugging — hard to validate the update flow end-to-end
- Certificate/TLS provisioning — managing device credentials at scale
- Other (please comment below)
0
voters
If you could choose the communication protocol between your MCU and the Mender server, what would you prefer?
- Current HTTPS — works fine for my use case
- CoAP/DTLS — lighter weight, UDP-based, similar REST model
- LwM2M — standardized IoT device management protocol (built on CoAP)
- MQTT — publish/subscribe, already using it for telemetry
- No preference — whatever uses the least resources
0
voters
If you have constraints we haven’t listed, like unusual network topologies, specific MCU families, regulatory requirements: we’d especially like to hear about those. Reply below.