@@ -6,6 +6,79 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
and this project adheres to
7
7
[ Semantic Versioning] ( https://semver.org/spec/v2.0.0.html ) .
8
8
9
+ ## [ 1.16.0] - 2024-10-24
10
+
11
+ ### 🔥 Removed
12
+
13
+ - Removed support for Zephyr < 2.7.0
14
+ - Removed support for nRF-Connect SDK < 1.9.2
15
+ - Removed support for ESP-IDF < 4.4.0
16
+
17
+ Please [ contact us] ( https://mflt.io/contact-support ) if you need support for
18
+ earlier versions!
19
+
20
+ ### 🐛 Fixed
21
+
22
+ - General:
23
+
24
+ - Correct an issue where ` eMemfaultRebootReason ` is expressed as a 4-byte type
25
+ instead of 2-bytes when compiling with Clang with high optimization, when
26
+ targeting ARM. This results in Coredumps tagged as ` Unknown ` instead of the
27
+ correct reason code.
28
+
29
+ ### 📈 Added
30
+
31
+ - General:
32
+
33
+ - Add a pair of optional user-provided functions,
34
+ ` memfault_reboot_tracking_load() ` / ` memfault_reboot_tracking_save() ` , to
35
+ allow users to provide their own implementations for saving and loading
36
+ reboot tracking data. This is useful when the default implementation is not
37
+ suitable for the platform or when the user wants to store the data in a
38
+ different location.
39
+
40
+ - The
41
+ [ Stable Sessions Device Vital] ( https://docs.memfault.com/docs/platform/memfault-core-metrics#stable-sessions )
42
+ added in SDK version ` 1.15.0 ` is fully available and no longer considered
43
+ experimental.
44
+
45
+ - Add an optional ` memfault_port_coredump_save_begin() ` callback, for use by
46
+ Memfault ports. This allows ` memfault_platform_coredump_save_begin() ` to be
47
+ implemented by the platform instead, for custom pre-coredump operations.
48
+ Thanks to @finger563 for reporting this issue in
49
+ [ #77 ] ( https://github.com/memfault/memfault-firmware-sdk/issues/77 ) !
50
+
51
+ - Improved API docs for events and data packetizer components by noting
52
+ restrictions for use in ISR contexts
53
+
54
+ - Zephyr:
55
+
56
+ - Update the Qemu app to support the ` nucleo_l496zg ` board, with support for
57
+ the Zephyr ` bbram ` subsystem, and implement the new
58
+ ` memfault_reboot_tracking_load() ` / ` memfault_reboot_tracking_save() `
59
+ functions to demonstrate the functionality.
60
+
61
+ - ESP-IDF:
62
+
63
+ - New Kconfig setting, ` CONFIG_MEMFAULT_ENABLE_REBOOT_DIAG_DUMP ` , to print the
64
+ ESP-IDF reboot reason code on system boot, for debugging purposes. This
65
+ feature is disabled by default.
66
+
67
+ ### 🛠️ Changed
68
+
69
+ - General:
70
+
71
+ - Update support links to refer to the preferred site
72
+ < https://mflt.io/contact-support > instead of the Memfault support email.
73
+ This link will redirect to a form where questions can be sent to the
74
+ Memfault support team.
75
+
76
+ - nRF-Connect SDK:
77
+
78
+ - Changed the Kconfig symbol ` MEMFAULT_REBOOT_REASON_GET_CUSTOM ` to be ` imply `
79
+ instead of ` select ` when the nRF-Connect SDK is enabled. This permits users
80
+ to disable the ` nrfx ` -based reboot reason tracking if needed.
81
+
9
82
## [ 1.15.0] - 2024-10-13
10
83
11
84
### 📈 Added
@@ -1361,8 +1434,9 @@ earlier versions!
1361
1434
- Improve FOTA support for nRF-Connect SDK 2.4+, by improving the technique
1362
1435
used to find the correct Memfault server root cert. Memfault uses a fast CDN
1363
1436
to improve OTA payload delivery, which uses a different root cert than the
1364
- Memfault device server. Please contact <[email protected] > immediately if
1365
- you encounter any cert-related issues.
1437
+ Memfault device server. Please
1438
+ [contact support](https://mflt.io/contact-support) immediately if you
1439
+ encounter any cert-related issues.
1366
1440
1367
1441
# ## 💥 Breaking Changes
1368
1442
0 commit comments