Merge pull request #89 from PelionIoT/release-4.13.1

mbed-cloud-client-example 4.13.1

Author: Jenia Kogan

CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog for Izuma Device Management Client example application
 
+## Release 4.13.1 (16.02.2023)
+
+- Updated `mbedTLS` from 2.28.1 to 2.28.2 for Linux targets and updated GitHub domain for it (from ArmMbed to Mbed-TLS).
+- Updated `libcurl` from 7.85.0 to 7.87.0 for Linux targets.
+
+### Known issues
+
+- [Linux/Zephyr] 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.
+  The default DNS setting was changed to synchronous DNS.
+
 ## Release 4.13.0 (21.11.2022)
 
 - [Mbed OS] Add DISCO_L496AG board. The cellular settings are for example only.
@@ -22,21 +32,49 @@
    * If a socket error is encountered, the next try will be done with the original CoaP port `5684`.
    * After 2nd fail we alternate back to the custom port.
    * NOTE! Only port `443` can be used as an alternative customer port with Izuma Networks.
+   
+### Known issues
+
+- [Linux/Zephyr] 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:
+  - For Linux devices, set the `PAL_DNS_API_VERSION` flag to 0.
+  - For Zephyr devices, set the `DNS API` selection to POSIX.
 
 ## Release 4.12.0 (01.03.2022)
 
 - Updated to Mbed OS 6.15.1.
 - [Linux] Add a new `define_lwm2m_compliant.txt` that enables communication with a LwM2M compliant service / interoperability (IoP) testing.
 - [Mbed OS] Add a new `mbed_app_lwm2m_compliant.json` that enables communication with a LwM2M compliant service / interoperability (IOP) testing with FRDM K64F device.
 
+### Known issues
+
+- [Linux/Zephyr] 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:
+  - For Linux devices, set the `PAL_DNS_API_VERSION` flag to 0.
+  - For Zephyr devices, set the `DNS API` selection to POSIX.
+
 ## Release 4.11.2 (01.12.2021)
 
 - Updated to Mbed OS 6.15.0.
 
+### Known issues
+
+- [Linux/Zephyr] 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:
+  - For Linux devices, set the `PAL_DNS_API_VERSION` flag to 0.
+  - For Zephyr devices, set the `DNS API` selection to POSIX.
+
 ## Release 4.11.1 (11.10.2021)
 
 - Updated Parsec to 0.6.0 version. This version is compatible with Mbed TLS 2.27.0.
 
+### Known issues
+
+- [Linux/Zephyr] 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:
+  - For Linux devices, set the `PAL_DNS_API_VERSION` flag to 0.
+  - For Zephyr devices, set the `DNS API` selection to POSIX.
+
 ## Release 4.11.0 (17.09.2021)
 
 - Application restructuring:
@@ -49,6 +87,13 @@
 - Added a demonstration of FOTA component update. Placed component registration and callback examples in `source/fota_platform_hooks_imp.cpp`.
 - [Linux] Added demonstration of FOTA combined update. Placed subcomponent registration and callback examples in `source/fota_platform_hooks_imp.cpp` under the `MBED_CLOUD_CLIENT_FOTA_SUB_COMPONENT_SUPPORT` flag.
 
+### Known issues
+
+- [Linux/Zephyr] 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:
+  - For Linux devices, set the `PAL_DNS_API_VERSION` flag to 0.
+  - For Zephyr devices, set the `DNS API` selection to POSIX.
+
 ## Release 4.10.0 (07.07.2021)
 
 - NXP_LPC54628 target configured to use the new upgraded Update client with `FOTA_USE_ENCRYPTED_ONE_TIME_FW_KEY` key.
@@ -62,10 +107,20 @@
 * Updated to Mbed OS 6.12.0.
   - Changed LED configuration from `LED_RED` to `LED1`.
 
+### Known issues
+
+- [Zephyr] Asynchronous DNS does not work well. 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 in the application's configuration settings. 
+
 ## Release 4.9.1 (17.06.2021)
 
 * No changes.
 
+### Known issues
+
+- [Zephyr] Asynchronous DNS does not work well. 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 in the application's configuration settings. 
+
 ## Release 4.9.0 (21.05.2021)
 
 * [Mbed OS] Increased `SN_COAP_BLOCKWISE_MAX_TIME_DATA_STORED` stored time to 15min for mesh to account for long retransmission chains during blockwise transfers.
@@ -78,6 +133,11 @@
 * Updated to Mbed OS 6.9.0.
 * [Linux] Updated Mbed TLS to 2.25.0.
 
+### Known issues
+
+- [Zephyr] Asynchronous DNS does not work well. 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 in the application's configuration settings. 
+
 ## Release 4.8.0 (24.03.2021)
 
 * Updated to Mbed OS 6.8.0.

README.md

@@ -1,11 +1,6 @@
 # Device Management Client reference application for connectivity
 
 The [`mbed-cloud-client-example`](https://github.com/PelionIoT/mbed-cloud-client-example) is a reference application that uses [Izuma Device Management Client library](https://github.com/PelionIoT/mbed-cloud-client) and demonstrates how to build a connectivity application.
-
-This readme offers tutorial for:
-1. [Device Management Client connection to a standard OMA LwM2M server tutorial.](pdmc-connection-to-standard-lwm2m-server-tutorial.md)
-2. [Device Management Client migration tutorial.](pdmc-migration-tutorial.md)
-
 More documentation in: https://developer.izumanetworks.com
 
 

TESTS/README.md

@@ -8,7 +8,7 @@ Basic requirements for Pelion capabilities:
 
 Installation of the test-library:
 
-- Install the prerequisites listed in the README of the [pelion-e2e-python-test-library](https://github.com/ARMmbed/pelion-e2e-python-test-library).
+- Install the prerequisites listed in the README of the [pelion-e2e-python-test-library](https://github.com/PelionIoT/pelion-e2e-python-test-library).
 - Configure your API-key as instructed in the same README.
 
 

TESTS/pelion-e2e-python-test-library.lib

@@ -1 +1 @@
-https://github.com/PelionIoT/pelion-e2e-python-test-library/#43e62c4a457c7c2568759dacc22948b59a459705
+https://github.com/PelionIoT/pelion-e2e-python-test-library/#c23d5a5b2aca16d4b5257f0486a6d1b53501e3f9

mbed-cloud-client.lib

@@ -1 +1 @@
-https://github.com/PelionIoT/mbed-cloud-client/#bed292c4a7778cbc55ac01fc832e2469d439c7f1
+https://github.com/PelionIoT/mbed-cloud-client/#cdacedb38db21eec59684af3e23556a69e6d1317

pal-platform/SDK/ZephyrOS/src/main.cpp

@@ -1,4 +1,5 @@
 /* Copyright (c) 2021 Pelion
+ * Copyright (c) 2023 Izuma Networks
  *
  * Licensed under the Apache License, Version 2.0 (the "License");
  * you may not use this file except in compliance with the License.
@@ -24,7 +25,7 @@ extern "C" int mbed_cloud_application_entrypoint(void);
 
 void main(void)
 {
-	printf("Pelion Device Management Client Example\r\n");
+	printf("Izuma Device Management Client Example\r\n");
 
     struct net_if *iface = net_if_get_default();
 

pal-platform/pal-platform.json

@@ -34,11 +34,11 @@
     },
     "middleware": {
       "mbedtls": {
-        "version": "2.28.1",
+        "version": "2.28.2",
         "from": {
           "protocol": "git",
-          "location": "https://github.com/ARMmbed/mbedtls.git",
-          "tag": "mbedtls-2.28.1"
+          "location": "https://github.com/Mbed-TLS/mbedtls.git",
+          "tag": "mbedtls-2.28.2"
         },
         "to": "Middleware/mbedtls/mbedtls"
       },
@@ -61,11 +61,11 @@
         "to": "Middleware/parsec_se_driver/parsec_se_driver"
       },
       "curl": {
-        "version": "7.85.0",
+        "version": "7.87.0",
         "from": {
           "protocol": "git",
           "location": "https://github.com/curl/curl.git",
-          "tag": "curl-7_85_0"
+          "tag": "curl-7_87_0"
         },
         "to": "Middleware/curl/curl"
       }
@@ -81,20 +81,20 @@
     },
     "middleware": {
       "mbedtls": {
-        "version": "2.28.1",
+        "version": "2.28.2",
         "from": {
           "protocol": "git",
-          "location": "https://github.com/ARMmbed/mbedtls.git",
-          "tag": "mbedtls-2.28.1"
+          "location": "https://github.com/Mbed-TLS/mbedtls.git",
+          "tag": "mbedtls-2.28.2"
         },
         "to": "Middleware/mbedtls/mbedtls"
       },
       "curl": {
-        "version": "7.85.0",
+        "version": "7.87.0",
         "from": {
           "protocol": "git",
           "location": "https://github.com/curl/curl.git",
-          "tag": "curl-7_85_0"
+          "tag": "curl-7_87_0"
         },
         "to": "Middleware/curl/curl"
       }
@@ -109,20 +109,20 @@
     },
     "middleware": {
       "mbedtls": {
-        "version": "2.28.1",
+        "version": "2.28.2",
         "from": {
           "protocol": "git",
-          "location": "https://github.com/ARMmbed/mbedtls.git",
-          "tag": "mbedtls-2.28.1"
+          "location": "https://github.com/Mbed-TLS/mbedtls.git",
+          "tag": "mbedtls-2.28.2"
         },
         "to": "Middleware/mbedtls/mbedtls"
       },
       "curl": {
-        "version": "7.85.0",
+        "version": "7.87.0",
         "from": {
           "protocol": "git",
           "location": "https://github.com/curl/curl.git",
-          "tag": "curl-7_85_0"
+          "tag": "curl-7_87_0"
         },
         "to": "Middleware/curl/curl"
       }
@@ -201,11 +201,11 @@
     },
     "middleware": {
       "mbedtls": {
-        "version": "2.28.1",
+        "version": "2.28.2",
         "from": {
           "protocol": "git",
-          "location": "https://github.com/ARMmbed/mbedtls.git",
-          "tag": "mbedtls-2.28.1"
+          "location": "https://github.com/Mbed-TLS/mbedtls.git",
+          "tag": "mbedtls-2.28.2"
         },
         "to": "Middleware/mbedtls/mbedtls"
       },

pal-platform/pal-platform.py

@@ -508,7 +508,7 @@ def fetch(self, dst, name):
             git_fetch(self.location, self.tag, dst, self.submodules, **self.stream_kwargs)
         except Exception as e:
             logger.error(e)
-            logger.error("** failed to fetch %s from git - please check that remote is correct and avialable **", name)
+            logger.error("** failed to fetch %s from git - please check that remote is correct and available **", name)
             sys.exit()
 
 class LocalSource(Source):

west.yml

@@ -10,7 +10,7 @@ manifest:
     - name: izuma-dm
       repo-path: mbed-cloud-client
       remote: PelionIoT
-      revision: bed292c4a7778cbc55ac01fc832e2469d439c7f1
+      revision: cdacedb38db21eec59684af3e23556a69e6d1317
       path: modules/lib/izuma-dm
     - name: zephyr
       remote: zephyrproject-rtos