Memfault Firmware SDK 1.30.3 (Build 15552)

Author: Memfault Inc

CHANGELOG.md

@@ -6,6 +6,58 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.30.3] - 2025-10-23
+
+This is a patch release, fixing build errors and one bug.
+
+### 🛠️ Changed
+
+- Zephyr:
+
+  - Update the RRAM coredump storage backend implementation to support the
+    Nordic nRF54LM20 (and other Nordic nRF54L series chips) when not using
+    partition manager to assign flash regions (i.e. using device tree fixed
+    partitions). See
+    [`ports/zephyr/common/memfault_rram_backed_coredump.c`](ports/zephyr/common/memfault_rram_backed_coredump.c)
+    for details, and how to enable the coredump storage backend.
+
+  - Fix a compilation error when `CONFIG_MEMFAULT_METRICS_THREADS_DEFAULTS=n`.
+
+  - Remove an error log statement from
+    [`memfault_platform_thread_metrics.c`](ports/zephyr/common/memfault_platform_thread_metrics.c).
+    Previously this would log as
+    `<err> mflt: No thread name registered for 0x2000eae8`, for example, but was
+    not useful in many cases, and is not an error in any case.
+
+### 🐛 Fixed
+
+- ESP-IDF:
+
+  - Fix a compilation issue when building the [ESP32 sample app](examples/esp32)
+    for an ESP32-C6 with `MEMFAULT_DISABLE=` set (i.e.
+    `MEMFAULT_DISABLE=1 idf.py set-target esp32c6 build`). This only impacts the
+    sample application.
+
+- Zephyr:
+
+  - Disable invoking `LOG_PANIC()` during fault handling by default. When
+    deferred logging is used (`CONFIG_LOG_MODE_DEFERRED=y`), triggering a panic
+    flush from fault context may result in some log backends
+    (`CONFIG_SHELL_LOG_BACKEND` for example) to double-fault, which results in
+    failed coredump captures. This specifically can happen when running a
+    non-secure application with TF-M, and passing back from a secure fault
+    handler using `CONFIG_TFM_ALLOW_NON_SECURE_FAULT_HANDLING=y`. Users who are
+    comfortable enabling this can re-enable `LOG_PANIC()` with
+    `CONFIG_MEMFAULT_FAULT_HANDLER_LOG_PANIC=y`.
+
+  - Remove an unnecessary `depends on PARTITION_MANAGER_ENABLED` in the
+    `MEMFAULT_COREDUMP_STORAGE_RRAM` Kconfig setting. This feature only requires
+    a partition labeled `memfault_coredump_partition`, but does not require
+    partition manager specifically (which is a Nordic nRF-Connect SDK feature,
+    not a Zephyr feature). Thanks to
+    [@JordanYates](https://github.com/JordanYates) for reporting this issue in
+    [#96](https://github.com/memfault/memfault-firmware-sdk/issues/96)!
+
 ## [1.30.2] - 2025-10-10
 
 This is a patch release, including only a change to boolean Kconfig prompts so
@@ -40,7 +92,7 @@ This is a minor release. Highlights:
 
 ### 📈 Added
 
-- Zephyr
+- Zephyr:
 
   - Add Kconfig option
     `CONFIG_MEMFAULT_COREDUMP_ACTIVE_TASK_STACK_SIZE_TO_COLLECT` to control how
@@ -56,7 +108,7 @@ This is a minor release. Highlights:
 
 ### 🛠️ Changed
 
-- Zephyr
+- Zephyr:
 
   - Replace use of deprecated API `bt_hci_cmd_create()` with
     `bt_hci_cmd_alloc()` for Zephyr 4.2+.

VERSION

@@ -1,3 +1,3 @@
-BUILD ID: 15462
-GIT COMMIT: b238b31908
-VERSION: 1.30.2
+BUILD ID: 15552
+GIT COMMIT: b8b409dcbf
+VERSION: 1.30.3

components/include/memfault/version.h

@@ -20,8 +20,8 @@ typedef struct {
 } sMfltSdkVersion;
 
 #define MEMFAULT_SDK_VERSION \
-  { .major = 1, .minor = 30, .patch = 2 }
-#define MEMFAULT_SDK_VERSION_STR "1.30.2"
+  { .major = 1, .minor = 30, .patch = 3 }
+#define MEMFAULT_SDK_VERSION_STR "1.30.3"
 
 #ifdef __cplusplus
 }

examples/esp32/apps/memfault_demo_app/main/led.c

@@ -102,7 +102,9 @@ static void led_config(void) {
 }
   #endif  // ESP_IDF_VERSION >= ESP_IDF_VERSION_VAL(5, 0, 0)
 
-static void prv_heartbeat_led_callback(MEMFAULT_UNUSED TimerHandle_t handle) {
+static void prv_heartbeat_led_callback(TimerHandle_t handle) {
+  (void)handle;
+
   static bool s_led_state = true;
 
   /* If the addressable LED is enabled */

examples/esp32/apps/memfault_demo_app/main/main.c

@@ -361,7 +361,7 @@ void esp_heap_trace_alloc_hook(void *ptr, size_t size, uint32_t caps) {
 }
 #endif
 
-#if !defined(CONFIG_MEMFAULT_LOG_USE_VPRINTF_HOOK)
+#if defined(CONFIG_MEMFAULT) && !defined(CONFIG_MEMFAULT_LOG_USE_VPRINTF_HOOK)
 // Demonstrate a custom vprintf hook that prefixes all log messages with
 // "[IDF]", before invoking the Memfault log hook, and then printing to stdout.
 static int prv_vprintf_hook(const char *fmt, va_list args) {

examples/nrf-connect-sdk/nrf5/memfault_demo_app/boards/nrf54lm20pdk_nrf54lm20a_cpuapp.conf

@@ -0,0 +1,7 @@
+# Use RRAM internal storage implementation instead of flash-based
+CONFIG_MEMFAULT_NCS_INTERNAL_FLASH_BACKED_COREDUMP=n
+CONFIG_MEMFAULT_COREDUMP_STORAGE_RRAM=y
+
+# Place the noinit objects into a custom section.
+CONFIG_MEMFAULT_REBOOT_TRACKING_REGION="memfault_noinit.memfault_reboot_info"
+CONFIG_MEMFAULT_RAM_BACKED_COREDUMP_REGION="memfault_noinit.memfault_coredump"

examples/nrf-connect-sdk/nrf5/memfault_demo_app/boards/nrf54lm20pdk_nrf54lm20a_cpuapp.overlay.example

@@ -0,0 +1,19 @@
+/*
+ Example device tree overlay for the nrf54lm20dk, showing how to set a
+ fixed-partition region for RRAM-backed coredump storage. Pass it with
+ '-DDTC_OVERLAY_FILE=boards/nrf54lm20pdk_nrf54lm20a_cpuapp.overlay.example'
+ when building.
+*/
+
+&cpuapp_rram {
+	partitions {
+		storage_partition: partition@1d1000 {
+			label = "storage";
+			reg = < 0x1d1000 0x4000 >;
+		};
+		memfault_coredump_partition: partition@1d5000 {
+			label = "memfault_coredump_partition";
+			reg = <0x1d5000 0x5000>;
+		};
+	};
+};

examples/nrf-connect-sdk/nrf5/memfault_demo_app/pm_static_nrf54lm20pdk_nrf54lm20a_cpuapp.yml

@@ -0,0 +1,80 @@
+EMPTY_0:
+  address: 0xd800
+  end_address: 0xe000
+  placement:
+    after:
+    - mcuboot
+  region: flash_primary
+  size: 0x800
+memfault_coredump_partition:
+  address: 0x1fc000
+  end_address: 0x1fd000
+  placement:
+    after:
+    - mcuboot_secondary
+  region: flash_primary
+  size: 0x1000
+app:
+  address: 0xe800
+  end_address: 0x105000
+  region: flash_primary
+  size: 0xf6800
+bootconf:
+  address: 0xffd080
+  end_address: 0xffd084
+  region: bootconf
+  size: 0x4
+mcuboot:
+  address: 0x0
+  end_address: 0xd800
+  placement:
+    align:
+      end: 0x1000
+    before:
+    - mcuboot_primary
+  region: flash_primary
+  size: 0xd800
+mcuboot_pad:
+  address: 0xe000
+  end_address: 0xe800
+  placement:
+    before:
+    - mcuboot_primary_app
+  region: flash_primary
+  size: 0x800
+mcuboot_primary:
+  address: 0xe000
+  end_address: 0x105000
+  orig_span: &id001
+  - app
+  - mcuboot_pad
+  region: flash_primary
+  sharers: 0x1
+  size: 0xf7000
+  span: *id001
+mcuboot_primary_app:
+  address: 0xe800
+  end_address: 0x105000
+  orig_span: &id002
+  - app
+  region: flash_primary
+  size: 0xf6800
+  span: *id002
+mcuboot_secondary:
+  address: 0x105000
+  end_address: 0x1fc000
+  placement:
+    after:
+    - mcuboot_primary
+    align:
+      start: 0x1000
+    align_next: 0x1000
+  region: flash_primary
+  share_size:
+  - mcuboot_primary
+  size: 0xf7000
+sram_primary:
+  address: 0x20000000
+  end_address: 0x2007fc00
+  region: sram_primary
+  size: 0x7fc00

ports/zephyr/Kconfig

@@ -83,7 +83,6 @@ config MEMFAULT_RAM_BACKED_COREDUMP
 config MEMFAULT_COREDUMP_STORAGE_RRAM
         bool "RRAM backed coredump storage"
         depends on NRFX_RRAMC
-        depends on PARTITION_MANAGER_ENABLED
         help
           Use an internal RRAM-backed coredump storage implementation. Requires
           a partition labeled `memfault_coredump_partition`.
@@ -872,6 +871,15 @@ config MEMFAULT_FAULT_HANDLER_RETURN
         instead of rebooting the system. Useful if the system needs to hook into
         `k_sys_fatal_error_handler` at the end of system fault handling.
 
+config MEMFAULT_FAULT_HANDLER_LOG_PANIC
+        bool "Trigger LOG_PANIC() on fault handling"
+        default n
+        help
+         When enabled, the Memfault fault handler will call `LOG_PANIC()` to
+         flush logs during fault handling. Note that this can cause unexpected
+         behavior in some log backends that are not safe to call from fault
+         context.
+
 choice MEMFAULT_SYSTEM_TIME_SOURCE
         prompt "Memfault system time source"
         default MEMFAULT_SYSTEM_TIME_SOURCE_DATETIME if DATE_TIME

ports/zephyr/common/memfault_mram_backed_coredump.c

@@ -2,6 +2,35 @@
 //!
 //! Copyright (c) Memfault, Inc.
 //! See LICENSE for details
+//!
+//! MRAM backed coredump storage implementation. To make use of this, be sure to
+//! add a fixed partition named "memfault_coredump_partition" to your device
+//! tree or use partition manager to define one.
+//!
+//! For example, if using partition manager, you might add an entry like this to
+//! the application's pm_static.yml file:
+//!
+//!  memfault_coredump_partition:
+//!    address: 0x155000
+//!    end_address: 0x165000
+//!    placement:
+//!      align:
+//!        start: 0x1000
+//!      before:
+//!      - end
+//!    region: flash_primary
+//!    size: 0x10000
+//!
+//! If using device tree specified partitions, you might add something like this
+//! to your board's dts file/overlay:
+//!
+//!  &mram1x {
+//!    partitions {
+//!      memfault_coredump_partition: partition@1a9000 {
+//!        reg = <0x1a9000 DT_SIZE_K(20)>;
+//!      };
+//!    };
+//!  };
 
 #include <memfault/components.h>
 #include <zephyr/drivers/flash.h>