Documentation

Mistake on this page? Email us
Docs › Release notes › Previous versions › Device Management Client Lite 1.1.0 release notes (preview)

Device Management Client Lite 1.1.0 release notes (preview)

New features

  • Added support for DISCO_L475VG_IOT01A board with Altair ALT1250_PPP Nb-IoT modem.
  • Added support for K64F ESP8266 Wi-Fi with an optimized version of Mbed TLS.
  • Added support for delta updates.
  • General code optimizations and improvements in application configurations.

Device Management Client Lite

  • Added support for using baremetal Mbed TLS version in Mbed OS builds instead of the default Mbed TLS that comes with Mbed OS.

    There is a script ./setup_optimized_mbedtls.sh available under the mbed-cloud-client/tools folder. When you run the script, it sets up your Client Lite, Mbed OS and application to use the baremetal version of Mbed TLS instead of the default one. Use the config file baremetal_mbedtls_config.h with this TLS configuration. To restore your default Mbed TLS configuration of Mbed OS, run the clean_optimized_mbedtls.sh script.

  • Fixed the registry_type of LwM2M to uint16_t instead of int16_t.

  • Fixed the handling of OPAQUE type resource notifications. Previously, the notifications were sent out without payload and with a wrong content-type.

Example application

  • Added Pelion E2E test library v0.2.6.

  • Updated to Mbed OS 5.15.3, compatible also with Mbed OS 6.0.0-alpha-3.

  • Added support for NB-IoT Altair modem on DISCO_L475VG_IOT01A board.

  • Removed "ppp-cell-iface.apn-lookup" and "ppp-cell-iface.baud-rate" from mbed_app.json, as they are obsolete (removed in Mbed OS 6.0). See details in example issue #3.

  • Workaround for GCC LTO issue #12871 in Mbed OS 6.0.0 Alpha 3 to pico_lte_size.json.

  • Added support for delta-tool and delta updates.

  • Added new configuration mbed_app_baremetal_tls.json for K64F and ESP8266 Wi-Fi to compile for baremetal optimized Mbed TLS configuration:

    1. In the mbed-cloud-client/tools folder, run ./setup_optimized_mbedtls.sh.
    2. To compile, run:
    mbed compile -m K64F -t GCC_ARM --app-config mbed_app_baremetal_tls.json --profile profiles/pico_lte_size.json --profile mbed-os/tools/profiles/extensions/minimal-printf.json

Known issues

The software is alpha quality, which means:

  • It is tested to compile only with the GCC_ARM compiler.
  • All client features are not in place yet.
  • APIs may change.
  • Documentation is work in progress.

Client Lite development is in progress so there are some known issues to keep in mind while using the APIs:

  • NRF52840_DK board uses J-Link. It has some stability issues when flashing the board. Sometimes, it ends up in "read only" mode. To fix this, unplug the USB cable and plug it back in.

  • API definitions and behavior may not be stable and may change in future releases.

  • The logs show:

    Resource created
Error code : 7

    You can ignore this error.

  • NRF52840_DK does not compile with ARMC6 compiler.

  • The device preserves certificates between device flashes (using .hex flashing). If you want the device to pick new developer credentials, you need to clear the storage for example with pyocd erase --mass-erase or use the configuration option storage-reset-dev-credentials in mbed_app.json. The device creates a new Device ID if it is not found in KVStore. Please note that developer certificate limits number of devices to 100.

  • NRF52840_DK board does not work with Block-wise sizes smaller than 512.

Previous Next