@@ -6,6 +6,71 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66and this project adheres to
77[ Semantic Versioning] ( https://semver.org/spec/v2.0.0.html ) .
88
9+ ## [ 1.11.2] - 2024-08-29
10+
11+ ### :chart_with_upwards_trend : Improvements
12+
13+ - nRF-Connect SDK:
14+
15+ - Add support for the following reboot reasons on nRF series SOCs. These
16+ reboot reasons are tracked as ` kMfltRebootReason_DeepSleep ` .
17+
18+ - ` NRF_POWER_RESETREAS_OFF_MASK `
19+ - ` NRF_POWER_RESETREAS_NFC_MASK `
20+ - ` NRF_POWER_RESETREAS_CTRLAP_MASK `
21+
22+ - Zephyr:
23+
24+ - Use ` MEMFAULT_ASSERT_HALT_IF_DEBUGGING_ENABLED ` to control whether coredumps
25+ trigger a halt when a debugger is attached.
26+
27+ - Add a new Kconfig option, ` CONFIG_MEMFAULT_RAM_BACKED_COREDUMP_REGION ` , to
28+ set the RAM region used for storing RAM-backed coredumps.
29+
30+ - Fix a :bug : when trying to communicate via HTTPS with Memfault on the
31+ nRF91x. On the nRF91x, socket operations are offloaded to the nRF modem lib,
32+ which does not currently support the socket option ` TLS_CERT_NO_COPY ` . In
33+ v1.9.4, this socket option was applied when TLS was enabled
34+ (` !g_mflt_http_client_config.disable_tls ` ) and Zephyr version was >=3.0.0
35+ (when support for this socket option was added). Therefore, devices on SDK
36+ versions >=1.9.4 and <1.11.2 trying to communicate with Memfault will run
37+ into a no protocol support error (` ENOPROTOOPT ` ) in the nRF modem lib. Since
38+ this option is only required to use the DER format,
39+ ` CONFIG_MEMFAULT_TLS_CERTS_USE_DER ` now depends on the Zephyr-implemented
40+ socket operations being used (` !NET_SOCKET_OFFLOAD ` ).
41+
42+ - Fix the build when using Zephyr 3.7.0 and leveraging the HTTP client and/or
43+ ESP32 port. The Memfault HTTP client would fail to build due to the wrong
44+ ` crypto.h ` header getting picked up in the build. Additionally, due to the
45+ [ removal of default support for mbedTLS hash algorithms in Zephyr] ( https://docs.zephyrproject.org/latest/releases/migration-guide-3.7.html#mbed-tls ) ,
46+ ` CONFIG_MBEDTLS_SHA1 ` now must be enabled explicitly when using any of
47+ Memfault's CA certificates. When using PEM and leveraging Zephyr's in-tree
48+ mbedTLS and config file
49+ (` CONFIG_MBEDTLS_BUILTIN=y && CONFIG_MBEDTLS_CFG_FILE="config-tls-generic.h" ` ),
50+ ` CONFIG_MBEDTLS_PEM_CERTIFICATE_FORMAT=y ` is required for PEM certificate
51+ support. To simplify certificate format selection, a new choice Kconfig
52+ called ` CONFIG_MEMFAULT_TLS_CERTS_FORMAT ` has been added. Use the configs
53+ ` CONFIG_MEMFAULT_TLS_CERTS_USE_PEM ` and ` CONFIG_MEMFAULT_TLS_CERTS_USE_DER `
54+ to choose the certificate format.` CONFIG_MEMFAULT_TLS_CERTS_USE_DER ` is the
55+ default choice config. Finally, the Kconfig ` CONFIG_SOC_FAMILY_ESP32 ` is now
56+ deprecated. References of this Kconfig now also check the new Kconfig
57+ ` CONFIG_SOC_FAMILY_ESPRESSIF_ESP32 ` . See
58+ [ Zephyr's 3.7 Migration guide] ( https://docs.zephyrproject.org/latest/releases/migration-guide-3.7.html )
59+ for more details.
60+
61+ - Dialog
62+
63+ - Add support to the existing DA145xx port for the DA14535 by adding the
64+ correct memory region for ` memfault_platform_sanitize_address_range() ` .
65+
66+ - Fix several :bug : s in ` memfault_reboot_reason_get() ` and
67+ ` memfault_platform_reboot() ` implementations in the DA146x port. In
68+ ` memfault_reboot_reason_get() ` , the bit masks were incorrectly applied and a
69+ block was missing to reset the reboot reason register if
70+ ` MEMFAULT_REBOOT_REASON_CLEAR ` is set. In ` memfault_platform_reboot() ` , the
71+ mechanism to reboot the system has been updated from
72+ ` hw_cpm_reboot_system() ` to ` SWRESET ` .
73+
974## [ 1.11.1] - 2024-08-12
1075
1176### :chart_with_upwards_trend : Improvements
0 commit comments