Skip to content

Device Management Client 4.10.0 General Availability
Compare
Choose a tag to compare
@teetak01 teetak01 released this 08 Jul 11:43
· 17 commits to master since this release
4.10.0
3d8d83b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Device Management Client example

Changes

  • Configured the NXP_LPC54628 target to use the new upgraded Update client.

  • Updated mesh configuration in mesh_wisun.json based on the new Update client implementation.

  • Introduced new bootloaders for devices that use candidate image encryption.
    Replaced FOTA_USE_DEVICE_KEY with FOTA_USE_ENCRYPTED_ONE_TIME_FW_KEY as the default value for MBED_CLOUD_CLIENT_FOTA_KEY_ENCRYPTION due to a security vulnerability found in FOTA_USE_DEVICE_KEY.

    This is a breaking change for Mbed OS devices that use bootloaders from PDMC 4.8.0 or 4.9.0.
    If you are upgrading to Device Management Client 4.10.0 but using the bootloader from a previous release, you must explicitly define FOTA_USE_DEVICE_KEY.
    We highly recommend using the bootloader from Device Management Client 4.10.0, which fixes a security vulnerability found in the bootloader from the 4.8.0/4.9.0 releases.

  • Updated to Mbed OS 6.12.0.

Known issues

  • [Zephyr] Asynchronous DNS does not work well. The device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level by setting the DNS API selection to POSIX in the application's configuration settings.

Release notes can be found from:
https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Assets 2
Loading