Skip to content

Device Management Client 4.11.0 General Availability
Compare
Choose a tag to compare
@teetak01 teetak01 released this 21 Sep 09:10
· 15 commits to master since this release
4.11.0
3693858
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Device Management Client example

Known issues

  • [Linux/Zephyr] Asynchronous DNS does not work well, and 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:
    • For Linux devices, set the PAL_DNS_API_VERSION flag to 0.
    • For Zephyr devices, set the DNS API selection to POSIX.

Changes

  • Application restructuring:
    • M2MInterfaceFactory::create_resource() function used for creating object and resources.
    • Replaced the deprecated status APIs with the on_status_changed() API.
    • Removed the MCC_MEMORY flag.
    • Replaced the MCC_MINIMAL flag with the PDMC_EXAMPLE_MINIMAL flag.
  • Updated to Mbed OS 6.14.0.
  • Updated Mbed TLS to 2.27.0 in pal-platform.
  • Added a demonstration of FOTA component update. Placed component registration and callback examples in source/fota_platform_hooks_imp.cpp.
  • [Linux] Added demonstration of FOTA combined update. Placed subcomponent registration and callback examples in source/fota_platform_hooks_imp.cpp under the MBED_CLOUD_CLIENT_FOTA_SUB_COMPONENT_SUPPORT flag.

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

Assets 2
Loading