Highlights | The Mender MCU Client now supports FreeRTOS, running as a native ESP-IDF component, delivering fail-safe A/B firmware updates with automatic rollback through the ESP-IDF bootloader. ESP-IDF devices are managed in the same Mender tenant as your Zephyr and Linux devices and, like Zephyr devices, typically use the cost-effective Micro device tier.
Microcontroller support in Mender now reaches beyond Zephyr. A preview of Mender for FreeRTOS, built on Espressif's ESP-IDF framework, is available for testing with the ESP32-S3 as the reference device.
Note: This is a preview and is not yet recommended for production use. For example, APIs and configurations may change in the official release version. Your feedback will directly shape the official release.
To get started, follow the Mender documentation for FreeRTOS (ESP-IDF), using the reference board ESP32-S3-DevKitC.
Mender MCU Client on FreeRTOS (ESP-IDF): What’s included
The Mender MCU Client now supports FreeRTOS. ESP-IDF, Espressif's official development framework, runs on FreeRTOS, and a large share of ESP32-based products are built on it. Until now, teams using ESP-IDF had to switch to Zephyr or build their own software update stack to get managed updates from Mender. The preview brings the same robust software updates to ESP-IDF applications, without requiring an RTOS change.
Leverage a native ESP-IDF component
The Mender MCU Client is added to your project as a regular ESP-IDF component. Declare mender-mcu as a dependency in main/idf_component.yml, and the ESP-IDF component manager fetches it on the next idf.py build. All client options are exposed through Kconfig, under Component config → Mender client in idf.py menuconfig, or set directly in sdkconfig.defaults.
Rely on fail-safe A/B updates with automatic rollback
Mender uses ESP-IDF's native over-the-air (OTA) software update mechanism and bootloader through the new esp-ota Update Module. The device maintains two OTA app partitions: the active partition runs the current firmware, and the inactive one receives the new update.
On the first boot of a new image, the bootloader marks it as “pending verification.” The Mender MCU Client confirms the update once it successfully starts. If the new firmware crashes or fails to report success, the bootloader reverts to the previous image on the next reboot; the device is never bricked. The esp-ota Update Module automatically enables the bootloader's rollback support.
Generate Mender Artifacts at build time
idf.py build produces a ready-to-deploy Mender Artifact, build/<project name>.mender, alongside the firmware binary. Upload it to the Mender Server and deploy it as with any other Artifact. The device type defaults to the ESP-IDF target (i.e., esp32s3), so Mender ensures the firmware reaches only compatible devices.
Utilize the same client API as Zephyr
The Mender MCU Client API is shared between Zephyr and FreeRTOS (ESP-IDF). The application provides an identity callback (e.g., the MAC address from esp_read_mac()) and a restart callback, then registers the esp-ota Update Module before activating the client. Teams already familiar with Mender on Zephyr can leverage their existing knowledge. The ESP-IDF reference application also shows a complete integration.
Secure connections out of the box
The client verifies the server certificate with ESP-IDF's certificate bundle, which works with hosted Mender without extra configuration. For an on-premise server with a self-signed certificate, add its CA certificate to a custom certificate bundle.
Managing FreeRTOS (ESP-IDF) devices in Mender
FreeRTOS (ESP-IDF) devices join the same Mender tenant as your existing fleet. Inventory, filtering, device groups, and deployment reports work the same for every device, so mixed fleets of FreeRTOS (ESP-IDF), Zephyr, and Linux devices can be managed simultaneously.
The Micro Device Tier
Like Zephyr devices, FreeRTOS (ESP-IDF) devices typically use the Micro device tier, which is built for resource-constrained devices and priced at about half of the Standard device tier.
|
Device Tier |
Micro |
Standard |
|
Maximum Artifact size |
5 MB |
10 GB |
|
Polling intervals |
Updates: 1 week |
Updates: 30 minutes |
The weekly polling intervals match the recommended production defaults for update checks and inventory reports for the Mender MCU Client. Free Trial accounts retain relaxed polling intervals across the included 5 Micro and 5 Standard devices to enable quick iteration during preview testing.
Reference devices
The ESP32-S3 is the reference device for Mender for microcontrollers, now supporting both Zephyr and FreeRTOS (ESP-IDF). Raspberry Pi 4 and 5 remain the reference devices for Linux-based operating systems.
|
Reference device |
Operating system |
Device Tier (default) |
|
ESP32-S3 |
Zephyr, or |
Micro |
|
Raspberry Pi 4 and 5 |
Linux (for example, Yocto or Debian-based) |
Standard |
Get started with Mender on FreeRTOS (ESP-IDF)
The preview supports ESP-IDF 6.0, with Espressif's ESP32-S3-DevKitC as the reference board. A device with 8 MB of flash leaves ample room for two OTA app partitions.
At a high level, integration takes six steps:
- Sign up for a Mender Free Trial and copy your Tenant Token from the Mender UI.
- Add the mender-mcu component to your project's main/idf_component.yml.
- Define a partition table with otadata, two OTA app partitions (ota_0 and ota_1), and small mender and mender_logs partitions for persistent client data and deployment logs.
- Set the flash size, partition table, Artifact name, and Tenant Token in sdkconfig.defaults, and make sure Wi-Fi or Ethernet is enabled.
- Register the identity and restart callbacks. Leverage the esp-ota Update Module, then activate the Mender MCU Client.
- Run idf.py build, flash the device, and upload the generated .mender Artifact to deploy the next release over-the-air.
The full walkthrough is in the Mender documentation for FreeRTOS (ESP-IDF), including the reference partition table and configuration snippets.
What's next
The FreeRTOS (ESP-IDF) support will follow the same path as the Zephyr integration. A public preview of the ESP32-S3 is currently available and will be refined based on community feedback. Then, an official release will be available for the Micro device tier. Testing on specific boards and applications now is the best way to ensure the official release fits your products.
Share your feedback
Share your experience with the FreeRTOS (ESP-IDF) preview and suggestions for future improvements in the Mender Hub General Discussions forum. We especially want to hear which ESP32 variants and ESP-IDF versions you build on, and how the integration fits your existing ESP-IDF projects.
If you encounter any issues with the preview, please report them in the Mender JIRA issue tracker with detailed reproduction steps and system information.
Recent articles
Incident debrief: Mender email invitations abused for spam emails
Achieving compliance and security for static medical devices
Official release: New component orchestration offers system-level software updates to multi-component products in Mender
Learn why leading companies choose Mender
Discover how Mender empowers both you and your customers with secure and reliable over-the-air updates for IoT devices. Focus on your product, and benefit from specialized OTA expertise and best practices.


