@@ -6,6 +6,55 @@ 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.13.0] - 2024-10-07
10
+
11
+ ### 📈 Added
12
+
13
+ - FreeRTOS:
14
+
15
+ - The SDK now has a config to control whether to split CPU usage per core when
16
+ building for a multi-core device. Enable this setting by adding
17
+ ` #define MEMFAULT_FREERTOS_RUNTIME_STATS_MULTI_CORE_SPLIT 1 ` to
18
+ ` memfault_platform_config.h ` . This setting is disabled by default.
19
+
20
+ - ESP-IDF:
21
+ - Added a Kconfig, ` CONFIG_MEMFAULT_FREERTOS_RUNTIME_STATS_MULTI_CORE_SPLIT ` ,
22
+ to control ` MEMFAULT_FREERTOS_RUNTIME_STATS_MULTI_CORE_SPLIT ` . This Kconfig
23
+ is enabled by default for multi-core devices.
24
+
25
+ ### 🛠️ Changed
26
+
27
+ - FreeRTOS:
28
+
29
+ - Changed previous idle task run time percent metrics to measure CPU usage
30
+ (i.e. the complement of the idle task run time)
31
+ - Renamed the following metrics:
32
+ - Single-Core + Multi-Core Default:
33
+ - ` idle_task_run_time_percent ` -> ` cpu_usage_pct `
34
+ - Multi-Core Split:
35
+ - ` idle0_task_run_time_percent ` -> ` cpu_usage_pct `
36
+ - ` idle1_task_run_time_percent ` -> ` cpu1_usage_pct `
37
+
38
+ - ESP-IDF:
39
+
40
+ - Unknown or unclassified reboot reason codes returned by ` get_reset_reason() `
41
+ are now correctly recorded as ` kMfltRebootReason_Unknown ` instead of
42
+ ` kMfltRebootReason_UnknownError ` (` UnknownError ` is reserved for an
43
+ "unexpected" reboot path, where ` Unknown ` is used when the reboot reason
44
+ cannot be determined).
45
+
46
+ ### 🚩 Deprecated
47
+
48
+ Support for the following vendor platform versions is deprecated in this
49
+ release, and will be removed in the following release:
50
+
51
+ - ESP-IDF < ` v4.4 ` (Jan 26, 2022)
52
+ - Zephyr < ` v2.7.0 ` (Oct 16, 2021)
53
+ - nRF-Connect SDK < ` v1.9.2 ` (Jul 14, 2022)
54
+
55
+ Please
[ contact us
] ( [email protected] ) if you need support for earlier
56
+ versions!
57
+
9
58
## [ 1.12.0] - 2024-09-25
10
59
11
60
### 📈 Added
@@ -79,6 +128,17 @@ and this project adheres to
79
128
80
129
# ## 📈 Added
81
130
131
+ - General :
132
+
133
+ - Add two new core metrics, `MemfaultSdkMetric_os_name` and
134
+ ` MemfaultSdkMetric_os_version` . These are string metrics that map to the OS
135
+ / platform name and version string respectively, and are included in the the
136
+ ELF at build time, and processed out-of-band by Memfault for NCS, Zephyr,
137
+ and ESP-IDF. They **are not** ever transmitted over the air (no bandwidth
138
+ impact). For example, for Zephyr these metric string values would be
139
+ ` zephyr` and `3.7.0` for a project on Zephyr v3.7.0. These metrics are
140
+ attributes by default and will not be counted towards attribute quotas.
141
+
82
142
- Zephyr :
83
143
84
144
- Add the following built-in WiFi metrics for Zephyr devices, enabled by
@@ -162,17 +222,6 @@ and this project adheres to
162
222
163
223
# ## 📈 Improvements
164
224
165
- - General :
166
-
167
- - Add two new core metrics, `MemfaultSdkMetric_os_name` and
168
- ` MemfaultSdkMetric_os_version` . These are string metrics that map to the OS
169
- / platform name and version string respectively, and are included in the the
170
- ELF at build time, and processed out-of-band by Memfault for NCS, Zephyr,
171
- and ESP-IDF. They **are not** ever transmitted over the air (no bandwidth
172
- impact). For example, for Zephyr these metric string values would be
173
- ` zephyr` and `3.7.0` for a project on Zephyr v3.7.0. These metrics are
174
- attributes by default and will not be counted towards attribute quotas.
175
-
176
225
- ESP-IDF :
177
226
178
227
- Fix a minor issue where MEMFAULT_LOG_x() macros (MEMFAULT_LOG_ERROR() etc )
0 commit comments