Mistake on this page? Email us

Device Management Client 2.1.1 General Availability (GA)


  • Support for Mbed OS 5.11.0.
  • Updated Mbed TLS 2.15.1.


Device Management Client example

  • Updated to Mbed OS 5.11.0.

  • Modified WiFi configuration configs/wifi_esp8266_v4.json to support new ESP8266 Wi-Fi chip having 2 MB or more flash and ESP8266 AT firmware 1.7.0, with serial flow control (UART0_CTS, UART0_RTS) pins and reset pin (EXT_RSTB) connected. For production devices, we recommend that you upgrade your ESP8266 to this version and connect those control pins to corresponding pins on the target hardware.

  • Previous Wi-Fi ESP866 is supported via new configs/wifi_esp8266_v4_legacy.json file.

    Note: With legacy ESP8266 Wi-Fi with 1 MB flash, the minimum supported firmware version is now 1.6.2. Without flow control and reset pin connected the device will eventually disconnect and fail to re-connect. ESP8266 firmware has to be version 1.7.0 (or later) to enable flow control and only boards with 2 MB flash or more can take that firmware in.

Device Management Connect client

Client handles packet duplication correctly. This resolves the case where Client was occasionally unable to reconnect. This is fixed in CoAP 4.7.2, which is part of Mbed OS 5.11.0.

Known issues

Mbed OS

We recommend going through Mbed OS release notes for known issues and their latest status.


  • Firmware update from one Linux distribution version to another does not work. For example, firmware update from Yocto distribution Morty to Rocko is not currently possible, as there are Linux version-dependent files (device tree) in the BOOT partition. Therefore, you must update within one major version of a distribution.
  • glibc versions 2.23 and 2.24 have a bug in thread creation. It can cause random crashes with Linux.
    • If possible, update glibc to version 2.25 (or newer). See sourceware issue 20116 for details.
    • We have implemented a workaround for this issue to decrease its likelihood. This issue may still occur under certain circumstances.
  • The Device Management Client application must run as root to have access rights to perform the firmware update.
    • This is not the most secure way to handle this issue, so a more secure implementation will come later.
  • Yocto distribution has only been tested in developer certificate mode.

Device Management Client 2.1.1 Third Party IP report

Device Management Client uses some open source third-party IP (TPIP). This table lists the TPIP and sources:

Original License Description
cn-cbor MIT Factory configurator client (FCC) uses cn-cbor: A constrained node implementation of CBOR in C, with slight modifications. The code is at mbed-cloud-client/factory-configurator-client/secsrv-cbor.
Unity MIT Platform Adaptation Layer (PAL) tests use Unity framework from ThrowTheSwitch. The code is at mbed-cloud-client/mbed-client-pal/Test/Unity.

You also get more TPIP with the Mbed OS release itself (for example lwIP and FATFS).