Mistake on this page? Email us

Mbed Cloud Client 1.3.1 General Availability (GA)

Changes since the previous release

Mbed Cloud Client

  • Improved tracing of CoAP packages.
  • Added an API to enable sending of the resource value as a part of the registration message.
    • Only the following value types are allowed:
      • STRING
      • INTEGER
      • FLOAT
      • BOOLEAN
  • A fix for sending an empty ACK with blockwise messages.
  • Replaced TCP_KEEPALIVE with CoAP PING.
    • Interval is controlled via MBED_CLIENT_TCP_KEEPALIVE_INTERVAL parameter.
  • Fixed the possible overflow in bootstrap errors.
  • Now, a token is used to verify BS, register, update register and unregister responses.
  • A fix for sending empty CoAP requests.
  • A fix for the internal timer.
  • PAL is used for asynchronous handling of DNS.

Mbed Cloud Update

Using PAL for asynchronous handling of DNS enables firmware update with mesh.

Platform Adaptation Layer (PAL)

  • A fix to crash when enabling mbed-tls traces.
  • Removed the thread-priority requirement.
  • Fixed the file system compatibility issue with Mbed OS 5.8/5.9.

Mbed Cloud Client example

  • Updated to Mbed OS 5.8.1.
  • The platform-specific code has been rewritten to have common implementation which can be shared with other Cloud applications (source/platform/).
    • Enabled multipartition support for an application.
    • Enabled LittleFS support.
    • Enabled autoformat/autopartition for the storage (controllable via compile-time flags).

Mbed OS

Known issues

Mbed OS

  • DTLS handshake fails on Ublox ODIN-W2, issue #6545.
  • Cloud Client registration does not work with IAR compiled binary if using Thread or 6LoWPAN, issue #3466.


  • 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 the sourceware issue 20116 for details.
    • We have implemented a workaround for this issue to decrease its likelihood. This issue may still occur in certain circumstances.
  • The Mbed Cloud 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 and a more secure implementation will come later.
  • Yocto distribution has only been tested with developer certificate mode.

Mbed Cloud Client 1.3.1 Third Party IP report

Mbed Cloud Client uses some open source Third Party IP (TPIP). This table lists the TPIPs whose sources we included:

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

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