Device Management Client 3.1.1
Device Management Client example
- Updated to Mbed OS 5.12.2.
- Fixed the application initialization issue in production flow. This fixes a regression caused by 3.1.0 release.
- Fixed a compilation issue of Nucleo F429ZI board with the root-level
- Older versions of Device Management SDK for Python (v2.03 or older) sent PUT payload with content type JSON, which is an unsupported content type for Client. Client version 2.2.1 no longer accepts PUT requests with unsupported data types. We recommend that you update to SDK v2.0.5 or later, which sends the requests with correct content type (text/plain).
We recommend that you read the Mbed OS release notes for known issues and their latest status.
- In UDP mode, bootstrap fails with smallest SSL fragment length.
- PSA is in preview level and as such not ready for production yet.
- You cannot update the pre-compiled PSA binary through firmware update. You can only update the application itself.
- Cypress PSoC6:
- Issues with storage. Random failures can occur in testing.
- The native Wi-Fi driver is feature-rich and as such it is quite large (400 KB) and with PSA included (220 KB) there is not much space for the OS and application.
- Client has been tested with ESP8266 (due to flash size) without flow control, because flow-control does not work with this board yet. ESP8266 without flow-control will not work reliably.
- NXP LPC55S69:
- The board has only 640 KB flash. PSA takes 192 KB out of it.
- You can use the Client example (with firmware update and bootloader) with
releaseprofile due to the flash size limitation.
- Only ARMC6 is supported for compilation.
- You can use the board in PSA mode (without real HW PSA implementation).
- The configuration file that allows this is placed under
configs-psafolder in the example.
- The PSA mode adds RAM consumption (static +3.5 KB) and flash/ROM consumption (+18.5 KB).
- Arm and partners are optimizing the solution in future releases.
- Firmware update installation for very large images on Raspberry Pi3B or Pi3B+ may fail with
mmc0 timeoutfailure. 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, as there are Linux version-dependent files (device tree) in the
BOOTpartition. Therefore, you must update within one major version of a distribution.
glibcversions 2.23 and 2.24 have a bug in thread creation. It can cause random crashes with Linux.
- If possible, update
glibcto version 2.25 (or newer). 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.
- If possible, update
- The Device Management Client application must run as
rootto 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.
Device Management 3.1 Client Third Party IP report
Device Management Client uses some open source third-party IP (TPIP). This table lists the TPIP and sources:
|cn-cbor||MIT||Factory configurator client (FCC) uses
|Unity||MIT||Platform Adaptation Layer (PAL) tests use Unity framework from ThrowTheSwitch. The code is at mbed-cloud-client/mbed-client-pal/Test/Unity.|