Device Management Client 4.1.0

Deprecation notes

• Deprecated M2MFirmware class.
• Deprecated PAL_UDP_MTU_SIZE. Use DTLS fragmentation support through mbed-client-pal.pal-max-frag-len instead.

Device Management Client example

• [Mbed OS] Replaced X-Nucleo IDW01M1 with the ESP8266 Wi-Fi module in mbed_app.json.
• Added reset pin for the ESP Wi-Fi module on the Nucleo F411RE configuration.
• Added flow control and reset pins for the ESP Wi-Fi module on the LPC55S69 configuration.
• Updated bootloaders to v4.1.0. LPC55S69_NS bootloader is retained in v4.0.1.
• [Mbed OS] Optimized Wi-SUN configuration for 100-node networks.
• Increased application default lifetime to 24 hours (mbed_cloud_client_user_config.h).
• Updated to Mbed OS 5.14.2.

Factory Configurator Client example

• Bugfix: The storage is deleted only after the first message is received from the factory tool and not upon initialization.
• [Mbed OS] Updated to Mbed OS 5.14.2.

Secure Device Access Client example

• [Mbed OS] Updated to Mbed OS 5.14.2.

Device Management Client

• Deprecated M2MFirmware class.
• Fixed handling of the write attribute step. Previously, it did not store the value-change history correctly.
• Fixed compilation issues caused by disabled update features. Previously, update-related configuration was mandatory even if the feature itself was disabled.
• Removed support for the obsolete and undocumented write attribute STP. It was an alias for documented attribute ST.
• [Linux] Added missing internal sub-component dependencies to CMakeLists.txt.
• Added randomization to reconnection timer calculations.
• Increased the library default MBED_CLOUD_CLIENT_LIFETIME to 86400 seconds.

Platform Adaptation Layer (PAL)

• Shortened one long filepath to mitigate compilation issues in Windows platforms due to too long file path.
• [Linux] Added O_SYNC flag for pal_plat_fsOpen() to ensure critical certificate data is written out without delays.
• TLS: Added an option to run Mbed TLS allocations in a static buffer.
• DTLS: Cancel DTLS timer event when cleaning up the TLS context.
  • In some cases, a DTLS timer event can remain in the running state even if the whole TLS context is destroyed.
  • This can happen, for example, when the client goes into a reconnect loop or when switching from bootstrap flow to LwM2M registration.

Known issues

• [PAL tests] PAL filesystem and PAL update tests currently support external SD card storage. Support for other types of storage will be added in future releases.
• [PAL tests] PAL TLS test (TCPHandshakeWhileCertVerify_threads) is not working on Mbed OS 5.13.0.
• Client resource size is limited to 64 KiB. For example, large binary objects (opaque resources) cannot exceed 64 KiB.
  • For example large pictures (or other large binary objects) should be uploaded to a different hosting service and use the LwM2M resources for passing the URI for that type of objects.
  • Alternatively, you can split a large object into chunks, and expose those chunks through multiple opaque resource instances.
• [Mbed OS] The device may stall at certificate renewal when compiling with the PSA configuration.

Mbed OS

We recommend that you read the Mbed OS release notes for known issues and their latest status.

• PSA is in preview level and as such not ready for production yet.
  • You cannot update the pre-compiled PSA binary through firmware update. You can only update the application itself.
  • NXP LPC55S69:
    • The board has only 640 KB flash. PSA takes 192 KB out of it.
    • You can use the Client example (with firmware update and bootloader) with release profile due to the flash size limitation.
    • Only ARMC6 is supported for compilation.
  • K64F:
    • You can use the board in PSA mode (without real HW PSA implementation).
    • The configuration file that allows this is placed under configs-psa folder in the example.
    • The PSA mode adds RAM consumption (static +3.5 KB) and flash/ROM consumption (+18.5 KB).
    • Arm and partners are optimizing the solution in future releases.

Linux

• The current Yocto version Sumo does not support Rapsberry Pi4B.
• Firmware update installation of very large images on Raspberry Pi3B or Pi3B+ may result in a mmc0 timeout failure. This is a generic Raspberry Pi3 issue. See RPI issue #2392.
• 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 later). 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.
• Yocto distribution used does not yet support Raspberry Pi4.

Device Management Client Third Party IP report

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

You also get more TPIP with the Mbed OS release itself, see their LICENSE.md for details.