Device Management Client 4.13.1

Device Management Client example

• Updated mbedTLS from 2.28.1 to 2.28.2 for Linux targets and updated GitHub domain for it (from ArmMbed to Mbed-TLS).
• Updated libcurl from 7.85.0 to 7.87.0 for Linux targets.

Factory Configurator Client example

• Updated mbedTLS from 2.28.1 to 2.28.2 for Linux targets and updated GitHub domain for it (from ArmMbed to Mbed-TLS).

Device Management Client

• Improved error logging for certificate enrollment misconfiguration.
• Fixed a failure in FOTA for developer flow in PSA mode. The mechanism of going through a storage reset if the compiled credential file differs from the stored credentials did not work well with PSA. Read a certificate instead of a private key that we can't read in PSA mode.
• Only synchronous DNS is currently supported.
  • [Linux] Change the default DNS to synchronous, by setting PAL_DNS_API_VERSION flag to 0.
  • [Zephyr] Change the default DNS to synchronous, by setting DNS API selection to POSIX.
    Note: For Linux devices with version >= 4.11.0, or Zephyr device with version >= 4.9.0 you should override the default DNS setting to synchronous in the application level.

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.

Mbed OS

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

• PSA is in preview level and as such isn't ready for production yet.
  • You can't update the precompiled PSA binary through firmware update. You can only update the application, itself.
  • K64F:
    • You can use the board in PSA mode (without real hardware PSA implementation).
    • The configuration file that allows this is placed under the configs-psa folder in the example.
    • The PSA mode adds RAM consumption (static +3.5KB) and flash/ROM consumption (+18.5KB).
    • Arm and Partners are optimizing the solution in future releases.

Linux

• 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 by setting the PAL_DNS_API_VERSION flag to 0.
• 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.
• Yocto release support for client has been deprecated - if you need it, please contact us.
• Primary offering for Linux embedded distributions is our Izuma Edge-solution via LmP.

Zephyr OS

• 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 by setting the DNS API selection to POSIX.
• Configuration MBED_CLOUD_CLIENT_CUSTOM_URI_PORT is not available for Zephyr. If you need, contact us and we will add it. Enabling it now makes the image break the size limit and linking fails.

Device Management Client Third Party IP report

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

NXP SDK

Additional TPIP for NXP SDK:

Keil SDK

Renesas SDK

Additional TPIP for Renesas SDK (FSP):

Secure Device Access (SDA)

If you enable Secure Device Access (SDA), you will use some additional TPIP:

Mbed OS

You also get more TPIP with the Mbed OS release, itself. See its LICENSE.md file for details.