Memfault RTOS Support

Memfault automatically detects what RTOS your system is running. For uploaded coredumps, it will attempt to extract backtraces for all threads in the system and optionally determine what state each thread is in and the stack usage high water mark.

In order for this to work correctly, the coredump must capture the RTOS' thread state variables, all thread control blocks as well as the stack memory of each thread. The following sections list for each RTOS what needs to be captured. See the documentation on Coredump Collection for details on how to set up additional coredump capturing regions.

FreeRTOS

Required

These variables must be captured in the coredump. On top of this, the memory of all task control blocks (TCB_t) must be captured. Because FreeRTOS TCBs double as linked list nodes, all TCBs must be captured.

uxCurrentNumberOfTasks
pxCurrentTCB
pxReadyTasksLists
xDelayedTaskList1
xDelayedTaskList2
xPendingReadyList
uxTopReadyPriority
xSchedulerRunning

note

There were several releases of FreeRTOS that did not include uxTopUsedPriority, see this GitHub issue:

https://github.com/FreeRTOS/FreeRTOS-Kernel/issues/33#issue-583304006

If the version of FreeRTOS in use doesn't include the fix, add the sample file (for example, this copy) and relevant linker flags.

Optional

xTasksWaitingTermination
xSuspendedTaskList

tip

Set configCHECK_FOR_STACK_OVERFLOW != 0 to ensure Memfault collects a coredump when the FreeRTOS kernel detects a stack overflow. See the FreeRTOS documentation for the possible values of configCHECK_FOR_STACK_OVERFLOW

How to Capture the Required Variables

The memfault_freertos_ram_regions.c file contains details on selectively capturing the required variables.

note

Note that this is only necessary if all of RAM is not captured as part of the coredump (i.e. when coredump storage and bandwidth is limited).

The strategy has 3 parts:

update linker script to enclose the needed variables in a known region
Update memfault_platform_coredump_get_regions() to include that region's data in a coredump region
Use the FreeRTOS traceTASK_CREATE/DELETE() macros to track tasks during runtime

See example implementations below.

Update the linker script (typically a file that ends with the .ld extension) to enclose the necessary .bss symbols with some exported symbols:

.bss (NOLOAD) :
{
    _sbss = . ;
    __bss_start__ = _sbss;
    __memfault_capture_bss_start = .;
    /* Place all objects from the FreeRTOS timers and tasks modules here.
       Note that some build systems will use 'timers.o' as the object
       file name, and some may use variations of 'timers.c.o' or
       'timers.obj' etc. This pattern should capture all of them. */
     *tasks*.o*(.bss COMMON .bss*)
     *timers*.o*(.bss COMMON .bss*)
    __memfault_capture_bss_end = .;

And then update memfault_platform_coredump_get_regions() to include those variables:

const sMfltCoredumpRegion *memfault_platform_coredump_get_regions(
    const sCoredumpCrashInfo *crash_info, size_t *num_regions) {
  int region_idx = 0;

  // any higher priority regions would go here, i.e. active stack

  // collect the FreeRTOS timer and task variables required for RTOS decode
  extern uint32_t __memfault_capture_bss_start;
  extern uint32_t __memfault_capture_bss_end;
  const size_t memfault_region_size = (uint32_t)&__memfault_capture_bss_end -
      (uint32_t)&__memfault_capture_bss_start;

  s_coredump_regions[region_idx] = MEMFAULT_COREDUMP_MEMORY_REGION_INIT(
    &__memfault_capture_bss_start, memfault_region_size);
  region_idx++;

  // remaining regions would go here. typically the
  // 'memfault_freertos_get_task_regions()' helper would be used to capture the
  // task data.
  region_idx += memfault_freertos_get_task_regions(&s_coredump_regions[region_idx],
      MEMFAULT_ARRAY_SIZE(s_coredump_regions) - region_idx);
  // remaining regions

Update the linker script (typically a file with a .icf extension) to include this line:

define block memfault_freertos { section .bss* object *tasks*.o*, section .bss* object *timers*.o* };

And then update memfault_platform_coredump_get_regions() to include that block:

// In the source file where memfault_platform_coredump_get_regions is defined add the following snippet
// Be sure to include additional sMfltCoredumpRegion entries in your regions array for the FreeRTOS regions
// created by the linker script and helper function
const sMfltCoredumpRegion *memfault_platform_coredump_get_regions(
    const sCoredumpCrashInfo *crash_info, size_t *num_regions) {
  int region_idx = 0;

  // any higher priority regions would go here, i.e. active stack

  // collect the block defined in the linker script
  const void *memfault_freertos_region_start = __section_begin("memfault_freertos");
  const size_t memfault_freertos_region_size = __section_size("memfault_freertos");
  s_coredump_regions[region_idx] = MEMFAULT_COREDUMP_MEMORY_REGION_INIT(
     memfault_freertos_region_start, memfault_freertos_region_size);
  region_idx++;

  // remaining regions would go here. typically the
  // 'memfault_freertos_get_task_regions()' helper would be used to capture the
  // task data.
  region_idx += memfault_freertos_get_task_regions(&s_coredump_regions[region_idx],
      MEMFAULT_ARRAY_SIZE(s_coredump_regions) - region_idx);
  // remaining regions

Finally, modify your FreeRTOSConfig.h to include this following snippet:

//! @file FreeRTOSConfig.h
#pragma once

#include "memfault/ports/freertos_trace.h"

Built-in FreeRTOS Metrics

The Memfault SDK has support for some built-in FreeRTOS Metrics:

idle_task_run_time_percent (for both single- and dual-core systems)
timer_task_stack_free_bytes

To enable these metrics, include the definition in the user Heartbeat configuration file:

memfault_metrics_heartbeat_config.def
loading...

View on GitHub

Be sure to add the Memfault FreeRTOS Port files to your project, located here in the SDK: sdk/embedded/ports/freertos/src/

Tracking Thread Stack Usage

The Memfault SDK has built-in support for tracking FreeRTOS thread stack usage, by registering thread names and stack usage metric keys.

By default, the IDLE and Tmr Svc tasks are monitored. To track other tasks, override the list of tracked tasks by adding the following to your project:

//! Set the list of threads to monitor for stack usage. The metric keys must
//! be defined in memfault_metrics_heartbeat_config.def, ex:
//!
//! MEMFAULT_METRICS_KEY_DEFINE_WITH_SCALE_VALUE(
//!   memory_main_pct_max, kMemfaultMetricType_Unsigned,
//!   CONFIG_MEMFAULT_METRICS_THREADS_MEMORY_SCALE_FACTOR
//! )
//! MEMFAULT_METRICS_KEY_DEFINE_WITH_SCALE_VALUE(
//!   memory_shell_uart_pct_max, kMemfaultMetricType_Unsigned,
//!   CONFIG_MEMFAULT_METRICS_THREADS_MEMORY_SCALE_FACTOR
//! )
#include "memfault/ports/zephyr/thread_metrics.h"

MEMFAULT_METRICS_DEFINE_THREAD_METRICS (
  // monitor the main thread stack usage
  {
    .thread_name = "main",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_main_pct_max),
  },
  // monitor the shell_uart thread stack usage
  {
    .thread_name = "shell_uart",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_shell_uart_pct_max),
  },
  // track the Timer thread stack usage. note that this metric doesn't need to
  // be defined by the user- it's built in to the SDK
  {
    .thread_name = "Tmr Svc",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_tmr_svc_pct_max),
  });

note

On some platforms, such as ESP-IDF, it's necessary to set the following to disable the default task list:

memfault_platform_config.h
#define MEMFAULT_METRICS_THREADS_DEFAULTS_INDEX 0

Optionally, instead of using a thread name to tag threads, a callback can be used that returns the thread handle. Example:

#include "memfault/ports/zephyr/thread_metrics.h"

static TaskHandle_t prv_get_shell_uart_task_handle(void) {
  // task handle for shell_uart task
  extern TaskHandle_t shell_uart_task_handle;
  return shell_uart_task_handle;
}

MEMFAULT_METRICS_DEFINE_THREAD_METRICS (
  // monitor the main thread stack usage
  {
    .thread_name = "main",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_main_pct_max),
  },
  // monitor the shell_uart thread stack usage, using the task handle callback
  // to provide the task handle instead of the thread name string
  {
    .get_task_handle = prv_get_shell_uart_task_handle,
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_shell_uart_pct_max),
  });

Coredump Stack High Watermark

Memfault will automatically compute stack high watermarks (represented as High Water Mark: x Bytes Free) for each task captured in a coredump.

Memfault has two ways of computing the high watermarks:

If a task's entire stack region is captured in the coredump, the watermark is computed when the coredump is processed. This requires setting #define configRECORD_STACK_HIGH_ADDRESS 1 in FreeRTOSConfig.h.
If #define MEMFAULT_COREDUMP_COMPUTE_THREAD_STACK_USAGE 1 is set in memfault_platform_config.h, the high watermark is computed when the coredump is captured. The full task stack does not need to be present in the coredump for Memfault to show the watermark. This also requires setting #define INCLUDE_uxTaskGetStackHighWaterMark 1 in FreeRTOSConfig.h.

Zephyr

Required

These variables must be captured in the coredump:

_kernel
_kernel_openocd_offsets
_kernel_openocd_size_t_size

Tracking Thread Stack Usage

The Memfault SDK has built-in support for tracking thread stack usage using Memfault Metrics. This is controlled with the Kconfig option CONFIG_MEMFAULT_METRICS_THREADS, and is enabled by default.

//! Set the list of threads to monitor for stack usage. The metric keys must
//! be defined in memfault_metrics_heartbeat_config.def, ex:
//!
//! MEMFAULT_METRICS_KEY_DEFINE_WITH_SCALE_VALUE(
//!   memory_main_pct_max, kMemfaultMetricType_Unsigned,
//!   CONFIG_MEMFAULT_METRICS_THREADS_MEMORY_SCALE_FACTOR
//! )
//! MEMFAULT_METRICS_KEY_DEFINE_WITH_SCALE_VALUE(
//!   memory_shell_uart_pct_max, kMemfaultMetricType_Unsigned,
//!   CONFIG_MEMFAULT_METRICS_THREADS_MEMORY_SCALE_FACTOR
//! )
#include "memfault/ports/zephyr/thread_metrics.h"

MEMFAULT_METRICS_DEFINE_THREAD_METRICS (
  // monitor the main thread stack usage
  {
    .thread_name = "main",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_main_pct_max),
  },
  // monitor the shell_uart thread stack usage
  {
    .thread_name = "shell_uart",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_shell_uart_pct_max),
  },
  // most configurations will have idle and system work queue threads, include
  // them in the tracked list. note that these metrics don't need to be defined
  // by the user- they're built in to the SDK
  {
    .thread_name = "idle",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_idle_pct_max),
  },
  {
    .thread_name = "sysworkq",
    .stack_usage_metric_key = MEMFAULT_METRICS_KEY(memory_sysworkq_pct_max),
  });

Threads are identified by the thread name string. This requires threads to have valid (and unique) names.

threads are statically created with K_THREAD_DEFINE() always have a valid string name set
threads created using k_thread_create() will need to have a name applied with k_thread_name_set()

Eclipse ThreadX RTOS

Required

These variables must be captured in the coredump:

_tx_thread_current_ptr
_tx_thread_created_ptr
_tx_thread_created_count
_tx_thread_system_state

Capturing Threads

note

Memfault currently does not have a built-in integration for tracking ThreadX threads on creation. Please contact us if you're interesting in support for this feature!

Capturing all of target RAM (.data and .bss) will capture any thread state, as well as the above ThreadX kernel variables, and will enable thread-aware coredumps.

If capturing all of target RAM is not possible, you can selectively capture the ThreadX kernel variables, thread control blocks, and thread stack regions.

This is done as follows:

Modify the linker script to place the required kernel variables in a specific region of .bss:

 .bss (NOLOAD) :
 {
     _sbss = . ;
     __bss_start__ = _sbss;
     __memfault_capture_bss_start = .;
     /* Place ThreadX global thread state variables in a single span */
     *tx_thread_initialize.o*(.bss COMMON .bss*)
     __memfault_capture_bss_end = .;
 }

Implement the memfault_platform_coredump_get_regions() function to include the ThreadX kernel variables:

 const sMfltCoredumpRegion *memfault_platform_coredump_get_regions(
     const sCoredumpCrashInfo *crash_info, size_t *num_regions) {
   int region_idx = 0;
   static sMfltCoredumpRegion s_coredump_regions[
     // active stack
     1
     // ThreadX kernel data structure
     + 1
     // ThreadX thread data structures (TCB + stack region)
     + MEMFAULT_PLATFORM_MAX_TASK_REGIONS * 2
   ];

   const size_t stack_size = memfault_platform_sanitize_address_range(
     crash_info->stack_address, MEMFAULT_PLATFORM_ACTIVE_STACK_SIZE_TO_COLLECT);

   s_coredump_regions[0] =
     MEMFAULT_COREDUMP_MEMORY_REGION_INIT(crash_info->stack_address, stack_size);

   // any higher priority regions would go here, i.e. active stack

   // collect the ThreadX kernel variables required for RTOS decode
   extern uint32_t __memfault_capture_bss_start;
   extern uint32_t __memfault_capture_bss_end;
   const size_t memfault_region_size = (uint32_t)&__memfault_capture_bss_end -
       (uint32_t)&__memfault_capture_bss_start;

   s_coredump_regions[region_idx] = MEMFAULT_COREDUMP_MEMORY_REGION_INIT(
     &__memfault_capture_bss_start, memfault_region_size);
   region_idx++;

   // See this example here for a strategy to capture ThreadX thread information:
   // https://github.com/memfault/memfault-firmware-sdk/compare/noahp/threadx-thread-capture
   region_idx += memfault_threadx_get_thread_regions(&s_coredump_regions[region_idx],
       MEMFAULT_ARRAY_SIZE(s_coredump_regions) - region_idx);

   *num_regions = region_idx;

   return s_coredump_regions;
 }

Other RTOSs

Memfault also supports these other RTOSs: Argon, ChibiOS, Mynewt, NuttX, Quantum Platform, and Keil RTX5 / ARM mbedOS.

FreeRTOS​

Required​

Optional​

How to Capture the Required Variables​

Built-in FreeRTOS Metrics​

Tracking Thread Stack Usage​

Coredump Stack High Watermark​

Zephyr​

Required​

Tracking Thread Stack Usage​

Eclipse ThreadX RTOS​

Required​

Capturing Threads​

Other RTOSs​

FreeRTOS

Required

Optional

How to Capture the Required Variables

Built-in FreeRTOS Metrics

Tracking Thread Stack Usage

Coredump Stack High Watermark

Zephyr

Required

Tracking Thread Stack Usage

Eclipse ThreadX RTOS

Required

Capturing Threads

Other RTOSs