Device Management Client Lite 1.4.0

Device Management Client Lite

• Fixed bug where client assumed that event_id and event_type are both 0 when event handler is initialized. Added definition PDMC_CONNECT_STARTUP_EVENT_TYPE -1 to LWM2M interface. Client uses it initializes connection event handler.
• Removed the need_reboot = false option in the fota_component_add() API. When registering a component, the need_reboot option must always be true.
• Updated to support Mbed OS 6.8.0. Baremetal Mbed TLS is now only supported with Mbed OS version 6.8.0 and later.
• The new Connection ID (CID) feature eliminates unnecessary DTLS handshake traffic between the client and the cloud during reconnection. To have the client persist the CID during reboot, the application can call the pause() API before shutting down the application. This call stores the CID context in persistent memory for use after reboot. The client then uses the CID to establish a secure connection to the cloud without requiring a DTLS handshake. The PROTOMAN_USE_SSL_SESSION_RESUME feature flag, which controls this feature, is enabled by default for Mbed OS and disabled by default for other platforms.
  • Added a compile-time check to require the mandatory Mbed TLS flags are defined when the Connection ID feature (PROTOMAN_USE_SSL_SESSION_RESUME) is enabled.
• Fixed FOTA full resume.
• Changes to implementation of update candidate image encryption:
  • Added new FOTA_USE_ENCRYPTED_ONE_TIME_FW_KEY option to MBED_CLOUD_CLIENT_FOTA_KEY_ENCRYPTION.
  • Replaced FOTA_USE_DEVICE_KEY with FOTA_USE_ENCRYPTED_ONE_TIME_FW_KEY as the default value for MBED_CLOUD_CLIENT_FOTA_KEY_ENCRYPTION due to security vulnerability found in FOTA_USE_DEVICE_KEY.
  • Using FOTA_USE_ENCRYPTED_ONE_TIME_FW_KEY is a breaking change and requires a new bootloader that support this feature.
  • Deprecated the FOTA_USE_DEVICE_KEY option, which will be removed in a future version.
• Added fota_app_postpone_reboot(). Calling this API postpones device reboot, which is required to complete the FOTA process, until the device application explicitly initiates reboot.
• Changed fota_app_defer() behavior such that the FOTA candidate image download or install resumes only after the device application explicitly calls fota_app_resume().
• Support calling fota_app_reject() after calling fota_app_defer().
• Fix: Support for resuming installation after an unexpected interruption (for example, power loss) of a component image.
• Added support for updating device firmware with a cloud-encrypted update image.
  • Enabled by the MBED_CLOUD_CLIENT_FOTA_ENCRYPTION_SUPPORT option.
  • Limitation: Not supported when MBED_CLOUD_CLIENT_FOTA_CANDIDATE_BLOCK_SIZE isn't 1024.
• Fixed coverity issues.
• Fixed compilation for Client Lite Linux, release mode. KVStore failed to compile in release mode.
• Fixed a bug that prevented Firmware-Over-the-Air (FOTA) from running successfully after devices were provisioned in the production flow.
• Fixed update flow when the update candidate version is 0.0.10.
• Fota block device configuration changes: FOTA_INTERNAL_FLASH_BD changed to FOTA_INTERNAL_FLASH_MBED_OS_BD, FOTA_CUSTOM_BD changed to FOTA_CUSTOM_MBED_OS_BD, added default block device configuration FOTA_DEFAULT_MBED_OS_BD.
• Changed FOTA application interface APIs:
  • fota_app_on_install_authorization(uint32 token) to fota_app_on_install_authorization() (removed token).
  • fota_app_on_download_authorization(uint32_t token, ...) to fota_app_on_download_authorization(...) (removed token).
  • fota_app_authorize_update() to fota_app_authorize() (reverted to the deprecated API).
  • fota_app_reject_update() to fota_app_reject() (reverted to the deprecated API).
  • fota_app_defer_update() to fota_app_defer() (reverted to the deprecated API).
• On Linux targets, all FOTA related files (candidate, header and so on) were moved to the the configuration directory (PAL/KVstore).
• Require defining MBED_CLOUD_CLIENT_FOTA_LINUX_SINGLE_MAIN_FILE in Linux MCCE, Testapp or any Linux app that has a single file update.

Release notes can be found from:
https://www.pelion.com/docs/pelion-client-lite/latest/release-notes/index.html

Device Management Client Lite 1.3.0

Device Management Client Lite

• Fixed the COAP_MSG_CODE_RESPONSE_BAD_REQUEST and COAP_MSG_CODE_RESPONSE_FORBIDDEN responses. Now client re-bootstraps when the server rejects registration.
• Fixed a memory leak that occurred because Device Management Client Lite did not release memory when the connection was closed.
• Fixed several issues related to Firmware-Over-the-Air (FOTA) updates.

Release notes can be found from:
https://www.pelion.com/docs/pelion-client-lite/latest/release-notes/index.html

Device Management Client Lite 1.2.1

Device Management Client Lite

Fixed handling of partially written (due to power-cut) flash pages while installing the firmware candidate.

Release notes can be found from:
https://www.pelion.com/docs/pelion-client-lite/latest/release-notes/index.html

Device Management Client Lite 1.2.0

New features and changes

Application and bootloader support for manifest version 3. This enables support for FOTA library features:

• Update download resume (currently not supported for differential updates) - resume download in case power or connectivity loss.
• Support firmware candidate encryption (useful for external storage) - disabled by default.
• Component update - allow an application to register custom components and installers.
• Semantic version - firmware version is reported based on the semantic version format.
• Firmware version is reported on the /14/0/2 resource.
• Manifest tool v2.0.0 is required to work with this FOTA library.
• Update x.509 certificate is replaced with a public key in uncompressed point format (X9.62) - requires less memory.
• An application can defer the update.

Device Management Client Lite

• Fixed an issue where Client Lite would trigger sleep-callback during the bootstrapping process.
• Changed the notification handler to send a notification only when crossing the "less than" or "greater than" notification threshold values.

Release notes can be found from:
https://www.pelion.com/docs/pelion-client-lite/latest/release-notes/index.html

Device Management Client Lite 1.1.1

Client Lite 1.1.0 sends an additional component update object (/14) as part of its registration message even though the client does not support it yet. The update service has changed recently to handle the client differently, so there is no backward compatibility. Client Lite 1.1.0 cannot successfully update firmware. As part of this patch release, component update is behind a feature flag that is disabled in Client Lite release.

Release notes can be found from:
https://www.pelion.com/docs/pelion-client-lite/latest/release-notes/index.html

Device Management Client Lite 1.1.0

• Added support for using baremetal Mbed TLS version in Mbed OS builds instead of the default Mbed TLS that comes with Mbed OS.

  There is a script ./setup_optimized_mbedtls.sh available under the mbed-cloud-client/tools folder. When you run the script, it sets up your Client Lite, Mbed OS and application to use the baremetal version of Mbed TLS instead of the default one. Use the config file baremetal_mbedtls_config.h with this TLS configuration. To restore your default Mbed TLS configuration of Mbed OS, run the clean_optimized_mbedtls.sh script.

• Fixed the registry_type of LwM2M to uint16_t instead of int16_t.

• Fixed the handling of OPAQUE type resource notifications. Previously, the notifications were sent out without payload and with a wrong content-type.

The software is alpha quality, which means:

All client features are not in place yet.
APIs may change.
Documentation is not perfect.
Memory (RAM/ROM) consumption is not in target level.

Release notes can be found from:
https://www.pelion.com/docs/pelion-client-lite/latest/release-notes/index.html

Device Management Client Lite 1.0.0

Client Lite 1.0.0 is the first preview release with support for:

• NRF52840_DK and easyRF BG96 Cellular.
• DISCO_L475VG_IOT01A and in-built ISM43362-M3G-L44 Wi-Fi.

The software is alpha quality, which means:

• All client features are not in place yet.
• APIs may change.
• Documentation is not perfect.
• Memory (RAM/ROM) consumption is not in target level.

Release notes can be found from:
https://www.pelion.com/docs/pelion-client-lite/latest/release-notes/index.html