Mistake on this page? Email us

Pelion Device Management Client Lite 0.6.0 preview release

This is a patch release for the sixth increment of the Device Management Lite preview release.

New features

  • Script support for the Client Lite production flow. Production process for Client Lite.
  • Mbed OS 5.10 support with an updated developer flow (breaking change on application level), see Client Lite tutorial.
  • Improved update flow removing the need of manually modifying the HTTP-based upload URI address to CoAP address, when making firmware updates. Client Lite now accepts a direct HTTP URI and internally makes a CoAP download through this address.
  • Support for Mesh networks such as Thread and 6LoWPAN.
  • The example application uses the global event queue provided by Mbed OS. This reduces the dynamic memory usage by client.

Fixed issues

Client Lite example application
  • Fixed Lite OMA Object definitions for Objects 10252 and 10255 to match the Update Client implementation.
  • Mbed TLS configuration: Enabled size optimizations for software implementation of AES, saving 6200 bytes of ROM.
  • Enabled buffered serial.
  • Updated to Mbed OS 5.10.2.
  • The application now gets the network interface status through console logs.
  • The application now uses Mbed OS 5.10 network interfaces directly and the dependency to easy-connect.lib is removed.
  • The application now uses Mbed OS bootloader binaries and the new Mbed OS feature FEATURE_BOOTLOADER. This feature makes the combine_bootloader_with_app.py script obsolete. We have removed the obsolete script.
    • The bootloader is now automatically combined with the application binary at compile time:
      • mbed-client-lite-example-restricted.bin is the binary you need to flash to the development board.
      • You can use mbed-client-lite-example-restricted_update.bin for the firmware update as long as the prerequisites for firmware update are fulfilled. (See the application tutorial).
  • Introduced a new script generate_firmware_images.py. It allows you to generate one or more firmware images ready to be flashed to a device.
  • Updated the application default lifetime to 3600s, thus reducing multiple registration update messages from client to server.
  • Updated the size-optimized compilation profiles for Mbed OS 5.10.
  • Partial configurations for the NRF52_DK board are now removed. The board configurations will be returned after it fulfills all the client requirements and passes testing.
  • The application is now running on the global event queue from the main thread, thus reducing the need for another thread to run the event loop. This saves dynamic and static memory.
  • Added the support for K64F board with Mesh network.
Device Management Client Lite
  • Implemented the handling of downloading URL into a URI query parameter.
  • The Device Management Update Client configuration now supports mapping of an external download protocol definition to internal configurations. This is needed for download protocol selection in Device Management Client. The default for Client Lite is CoAP download.
  • Fixed occasional Wi-Fi hardfaults observed during long test runs.
  • Fixed a recoverable CoAP error (service unavailable) to resume the firmware download.
  • Enabled CoAP message duplication detection by default.
  • Fixed firmware download failure during registration update.
Update with Client Lite
  • A new profile flag ARM_UC_PROFILE_MBED_CLIENT_LITE is used to enable the correct profile for Client Lite.
  • Added support for sending update Resource data as part of the Client registration message, thereby reducing network traffic between Client and Device Management.
  • Optimized static RAM usage by reusing the static object ManifestManagerContext during the initialization.
  • HTTP URI can now be used as a parameter in the CoAP GET API.
  • Fixed the issue with campaign not completing when there is a payload hash mismatch during the firmware update operation.
  • Added support for passing the HTTP URI instead of CoAPs to the generate-manifest script.
  • Fixed the memory leak in URI handling when receiving the manifest from cloud.

Known issues

If the size of the firmware to be uploaded is larger than the space available for storing it, the download fails (as it should), but a proper error code is not propagated to Device Management.

Important Information for this Arm website

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.