Device Management Client 4.0.0 General Availability

• Updated to Mbed OS 5.14.0.
• [Linux] Updated Mbed TLS to 2.19.1.
• The example application initialization is now done in multiple steps. This ensures the succcessful initialization of the Device Management Client library. It needs to be properly initialized before the memory intensive components (for example nanostack mesh stack).
• Removed CY8CKIT_062_WIFI_BT_PSA, which is no longer supported starting from Mbed OS 5.13.1.
• [Linux] Fixed busy-loop when stdin is not connected.
• Added default behavior for optionally created Factory Reset Resource located under the Device Object /3/0/5.
• You can overwrite both Reboot and Factory Reset Resource default behavior by implementing corresponding handler functions.
• Added support for Discovery L475VG IOT01A target board (configs/wifi.json).
• Added PSA support for NUCLEO_F411RE target board (configs-psa/wifi.json).
• Added PSA support for Linux (define_linux_psa.txt).
• Changed NUCLEO_F411RE Wi-Fi configuration to use ESP8266 module instead of the deprecated X-Nucleo IDW01M1.
• Unified Wi-Fi configuration files. configs/wifi.json and configs-psa/wifi.json now include all supported Wi-Fi configurations except the minimum configuration example, which is still in configs/wifi_esp8266_minimal.json.
• New application feature to introduce random delay for Device Management Client registration after the network connection has been established. You can use this feature to stabilize large mesh-type networks with high latency and limited bandwidth. By default, it is enabled for mesh-type networks and disabled for other configurations. To enable the random delay, define STARTUP_MAX_RANDOM_DELAY in seconds.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 3.4.0 General Availability

• Added PSA configuration for K66F (configs-psa/eth_v4.json).
• Updated usage of new Update Authorization API, which enables update priority feature set_update_authorize_priority_handler instead of set_update_authorize_handler.
• Use set_message_delivery_status_cb to ensure that a POST trigger on the unregister resource (/5000/0/1) does not result in closing the network connection before client is able to send the final ACK to server.
• [Linux] Updated Mbed TLS to 2.18.1.
• [Mbed OS] Removed the legacy ESFS-SOTP configurations from the applications. Only KVstore is supported for client storage.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 3.3.0 General Availability

• Updated to Mbed OS 5.13.0.
• Added support for Wi-SUN mesh on Nucleo F429ZI (configs/mesh_wisun.json).
• Added PSA support for Linux PC.
  • PSA configuration (define_linux_psa.txt) for PSA-enabled Linux PC.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 3.2.0 General Availability

• Updated to Mbed OS 5.12.4.
• Added delta tool to the example application.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 3.1.1 General Availability

• 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 mbed_app.json.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 3.1.0 General Availability

• Updated to Mbed OS 5.12.1.
• [Linux] Updated Mbed TLS to 2.17.0.
• General optimization on default stack-sizes and TLS configurations for all configurations.
  • Dropped the lwIP buffers from 32 KiB to 12 KiB.
  • Flash savings from 7 KiB to 20 KiB.
  • RAM savings from 7 KiB to 34 KiB.
• Introduced new configs/wifi_esp8266_minimal.json which demonstrates the bare minimum needed for full client functionality.
  • The configuration uses shared event-queue from main thread, instead of using a separate thread for events. This saves 10.5 KiB RAM.
  • New application flag MCC_MINIMAL disables several features only designed to enhance user experience, and removes other non-critical features.
  • Disabled Button and LED usage by default.
  • Disabled error descriptions.
  • Disabled usage of some helper functions like fcc_verify().
  • Resources generated by the application are disabled on this profile.
  • Changed the KVStore and firmware candidate storage to internal flash configuration. This saves 4 KiB RAM and 34 KiB ROM as you don't need to pull in SDDriver or related components.
  • Altogether, these optimizations save 43 KiB flash and 31 KiB RAM in respect to the configs/wifi_esp8266_v4.json profile. (49 KiB flash and 39 KiB RAM vs. 3.0.0 release version).
  • Currently, the minimal profile supports only TCP.
• Minimal configuration is optimimal for boards with about 1024 KiB of flash. If you use it with boards with only 512 KiB flash, you need to enable the external storage for a firmware update candidate and KVstore. The following changes would be needed:
  • Change the bootloader to the block_device variant.
  • Change the target offsets to match the block_device bootloader.
  • Change the update storage to point to the external storage.
  • Change the KVstore configuration to match the external storage configuration.
  • See the porting guide for reference.
• K66F default configuration now provides the full Client feature. This target enables all the RAM/ROM intensive features by default.
  • Enabled certificate enrollment client features.
  • Increased the main stack size to reflect higher RAM requirements for features.
• [MbedOS] Stop using CellularBase() as it is deprecated in Mbed OS, use CellularInterface() instead.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 3.0.0 General Availability

• Updated to Mbed OS 5.12.0.
• [Mbed OS] Use asyncronous DNS by default for all targets.
• [Mbed OS] Preview support for Platform Security Arhitecture (PSA) enabled boards.
  • PSA configuration for PSA-enabled Cypress PSoC6 and NXP LPC55S69 boards. Configuration is in the configs-psa/ folder.
  • Both PSA-enabled boards use ESP8266 Wi-Fi.
  • PSA configuration for K64F board.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 2.2.1 General Availability

• Updated to Mbed OS 5.11.5.
• Added KVStore support for Nucleo F411RE.
• Changed the board configuration for Nucleo F429ZI to use internal flash profile.
• Added bootloaders for the legacy_storage configurations as part of the application repository. Explicitly defined the target offsets for each bootloader to provide more clarify on the board configuration.
• By default, MBED_CLOUD_CLIENT_STL_API is set to 0 in mbed_lib-json. This disables the deprecated client APIs completely in SimpleM2MResourceString and SimpleM2MResourceInt classes. MBED_CLOUD_CLIENT_STD_NAMESPACE_POLLUTION is 0 also by default. It disables the namespace pollution of code that includes MbedCloudClient.h with using namespace std;. With these changes you can save extra ROM overhead of ~15 KB on ROM budget, depending on the compiler toolchain used.
• Added Python3 support for Device Management end-to-end tests.
  • Updated the minimum required version of Mbed Python SDK to 2.0.5.
  • Updated the minimum Icetea version to 1.2.1.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 2.2.0 General Availability

• Updated to Mbed OS 5.11.4.
• [Mbed OS] Client 2.2.0 has fixed the internal initialization of ns_hal_init(), which fixes the issue of double initialization of memory when using Mesh network stacks.
  • Removed the application configurations of mbed-client.event-loop-size for most configurations. The application uses the default configuration defined in mbed-client, or from Mbed OS for Mesh network stacks.
  • For Wi-Fi stacks, mbed-client.event-loop-size needs to be 2048.
• [Linux] Updated CMake minimum version to 3.5.
• [pal-platform] Deprecated the fullBuild option in build tools.
• [Mbed OS] By default, application configuration updated to use secure storage implementation through KVstore.
  • K66F now uses internal flash for both storing client credentials and the update image.
  • All other boards have been changed to use LittleFS instead of FAT file system by default. FAT file system is not power-loss resilient and should not be used in embedded devices.
  • Old SOTP-ESFS based storage configuration files are still available in the configs/legacy_storage folder.
  • NUCLEO F411RE board still uses SOTP-ESFS implementation, as non-TRNG boards are not yet supported in new KVStore-based storage.
  • Legacy Wi-Fi configuration wifi_esp8266_v4_legacy.json introduced in the 2.1.1 release has been removed.
• Moved the network init call to main() and added network disconnect call to end of main().
• Removed extern block evice reference from platform-common.
• Added TESTS/PAL/test.py script to help run PAL porting tests.
• Added basic Device Management acceptance end-to-end tests that use the Icetea test framework.

Release notes can be found from:

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 2.1.1 General Availability

• Updated to Mbed OS 5.11.0.

• Modified WiFi configuration configs/wifi_esp8266_v4.json to support new ESP8266 Wi-Fi chip having 2 MB or more flash and ESP8266 AT firmware 1.7.0, with serial flow control (UART0_CTS, UART0_RTS) pins and reset pin (EXT_RSTB) connected. For production devices, we recommend that you upgrade your ESP8266 to this version and connect those control pins to corresponding pins on the target hardware.

• Previous Wi-Fi ESP866 is supported via new configs/wifi_esp8266_v4_legacy.json file.

  Note: With legacy ESP8266 Wi-Fi with 1 MB flash, the minimum supported firmware version is now 1.6.2. Without flow control and reset pin connected the device will eventually disconnect and fail to re-connect. ESP8266 firmware has to be version 1.7.0 (or later) to enable flow control and only boards with 2 MB flash or more can take that firmware in.

https://cloud.mbed.com/docs/current/release-notes/device-management-client.html