You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+23-15Lines changed: 23 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,32 +1,40 @@
1
1
# Changelog for Pelion Device Management Client example application
2
2
3
-
## Release 4.8.0 (19.04.2021)
3
+
## Release 4.9.0 (20.05.2021)
4
+
5
+
*[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.
6
+
*[Mbed OS] Updated ISM43362 Wi-Fi driver to #09a71bf with fix to mutex handling.
7
+
* Removed unregister resource `5000/0/1` from the application. Device Management Client library now implements OMA resource ` 1/0/4`, which supports deregistration.
8
+
* Removed delta-tool from the application.
9
+
* The current supported version (2.2.0 or later) of [manifest-tool](https://github.com/PelionIoT/manifest-tool) provides the functionality internally.
10
+
* Updated cURL to 7.76.0 in `pal-platform`.
11
+
* Fixed Atmel SE configuration.
12
+
* Updated to Mbed OS 6.9.0.
13
+
*[Linux] Updated Mbed TLS to 2.25.0.
14
+
15
+
## Release 4.8.0 (24.03.2021)
4
16
5
17
* Updated to Mbed OS 6.8.0.
6
18
* Updated cURL to 7.75.0 in `pal-platform`.
7
19
* Updated parsec-se-driver to 0.4.0.
8
-
* Updated to Pelion end-to-end test library v0.2.10.
20
+
* Updated to Pelion E2E test library v0.2.10.
9
21
* Removed support for SXOS platform in the application.
10
-
* Consolidated the K64F ESP8266 configuration to `wifi_esp8266_minimal.json`.
11
-
*Removed K66F PSA.
12
-
*`DISCO_L475VG_IOT01A` target bootloader increased from 36kB to 38kB.
22
+
* Consolidated the K64F ESP8266 configuration to wifi_esp8266_minimal.json.
23
+
* K66F PSA has been removed.
24
+
* DISCO_L475VG_IOT01A target bootloader was increased from 36kB to 38kB.
13
25
* Introduction of upgraded Update client:
14
26
* The new features of the upgraded Update client:
15
27
* Component update.
16
28
* Resume after power failure.
17
29
* Defer firmware update installation.
18
30
* Candidate encryption on external storage.
19
-
* Configured Mbed OS non-mesh and Linux targets to use the new upgraded Update client.
20
-
21
-
<spanclass="notes">**Note:** To use legacy Update client in your Mbed OS non mesh target, please refer to the configurations in PDMC example 4.7.1.</span>
22
-
31
+
* Mbed OS non-mesh and Linux targets are configured to use the new upgraded Update client.
32
+
* Note - if you wish to use legacy Update client in your Mbed OS non mesh target, please refer to the configurations in PDMC exmaple 4.7.1.
23
33
* Legacy Update client is still used in Mbed OS mesh targets and SDK's targets (NXP, Renesas).
24
-
* Upgraded update client bootloaders are located in prebuild-bl folder. Legacy bootloaders are located in tools folder.
25
-
* On `K64F`, `NUCLEO_F411RE` and `DISCO_L475VG_IOT01A` targets, the update candidate is stored encrypted on the external storage encrypted.
26
-
27
-
* Created migration documentation guide for existing customers who wish to migrate legacy Update client to the new Update client.
28
-
29
-
<spanclass="notes">**Note:** After you migrate to the new Update client, only the "Component update" feature is available. To use other features of the new Update client, reflash the device with the new configuration and new bootloader.</span>
34
+
* Upgraded update client bootloaders are located in prebuild-bl folder. Legacy bootloaders are located in tools folder
35
+
* On K64F, NUCLEO_F411RE, DISCO_L475VG_IOT01A targets, the update candidate is stored encrypted on the external storage encrypted.
36
+
* Migration documentation guide was created for existing customers that wish to migrate legacy Update client to the new Update client - [TBD Link to https://github.com/PelionIoT/mbed_Cloud_Docs/pull/1689/files].
37
+
* Note - once migrated to new Update client, only "Component update" feature will be available. For using other features of new Update client, the device needs to be reflashed with the new configuration and new bootloader.
0 commit comments