Device Management Client 4.9.1

Device Management Client

• Fixed the incorrect overriding of CoAP retransmission buffer size.

Platform Adaptation Layer (PAL)

• [Zephyr] Fixed a memory leak on DNS handling.

Known issues

• The earlier revisions of LPCXpresso 546XX have a different QSPI chip than some of the later revisions. The application needs to specify the chip at compile time. Select the correct QSPI chip in the board configuration file (define_NXP_LPC54628.txt). This depends on the board revision.
• [PAL tests] PAL file system and PAL update tests currently support external SD card storage. Support for other storage types will be added in future releases.
• [PAL tests] PAL TLS test (TCPHandshakeWhileCertVerify_threads) is not working on Mbed OS 5.13.0.
• Update client full resume doesn't work. If the image download was interrupted, a full download starts from the beginning.
• Update client image encryption feature is going to be improved in the next PDMC release with a bootloader change. Customers that are planning to release an Mbed OS based device to production, that is using an external flash, are advised to wait for the next PDMC release.

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

• Firmware update installation of very large images on Raspberry Pi3B or Pi3B+ may result in a mmc0 timeout failure. This is a generic Raspberry Pi3 issue. See RPI issue #2392.
• Firmware update from one Linux distribution version to another does not work. For example, firmware update from Yocto distribution Morty to Rocko is not currently possible because of Linux version-dependent files (device tree) in the BOOT partition. Therefore, you must update within one major version of a distribution.
• 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.
• The Device Management Client application must run as root to have access rights to perform the firmware update.
  • This is not the most secure way to handle this issue, so a more secure implementation will come later.
• Yocto distribution has only been tested in developer certificate mode.
• Yocto distribution used does not yet support Raspberry Pi4.

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.

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.