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 inmbed-client
, or from Mbed OS for Mesh network stacks. - For Wi-Fi stacks,
mbed-client.event-loop-size
needs to be 2048.
- Removed the application configurations of
- [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 tomain()
and added network disconnect call to end ofmain()
. - 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