Memfault

The Memfault module provides an integration of Memfault SDK into nRF Connect SDK and expands the functionality of the SDK with some options that are specific to nRF Connect SDK. To get started with Memfault integration in nRF Connect SDK, see Memfault integration.

Memfault SDK is an SDK for embedded devices to make use of services that Memfault offers on their platform. For official documentation for Memfault SDK and the Memfault platform in general, see Memfault Docs.

Note

When building applications with Trusted Firmware-M (TF-M), the faults resulting from memory access in secure regions are not caught by Memfault’s fault handler. Instead, they are handled by TF-M. This means that those faults are not reported to the Memfault platform.

Configuration

In general, configuration of Memfault SDK in nRF Connect SDK is done using Kconfig options. Kconfig options are defined both in Memfault SDK and in the integration layer, which integrates the SDK into nRF Connect SDK. Kconfig options of the integration layer are located in modules/memfault/Kconfig. These Kconfig options are differentiated by two distinct prefixes:

• CONFIG_MEMFAULT_ - Prefix for options defined in Memfault SDK

• CONFIG_MEMFAULT_NCS_ - Prefix for options defined in nRF Connect SDK

Additionally, nRF Connect SDK has an implementation of the Memfault Diagnostic Service (MDS). Use the CONFIG_BT_MDS option to enable it. The MDS cannot be used concurrently with HTTP transport.

Configuration files

If you just want to do a quick test with a sample, disable the CONFIG_MEMFAULT_USER_CONFIG_ENABLE option in the prj.conf file to avoid adding the user configuration files. Otherwise, follow the instructions below.

Memfault SDK requires three files in the include path during the build process. Add a new folder called config into your project and add the following three files:

• memfault_platform_config.h - Sets Memfault SDK configurations that are not covered by Kconfig options.

• memfault_metrics_heartbeat_config.def - Defines application-specific metrics.

• memfault_trace_reason_user_config.def - Defines application-specific trace reasons.

For more information, see the Memfault nRF Connect SDK integration guide. You can use the files in the Memfault sample as a reference. To have these configuration files in the include path, add the following to the CMakeLists.txt file:

zephyr_include_directories(config)

Configuration options in Memfault SDK

Following are some of the configuration options that Memfault SDK defines:

• CONFIG_MEMFAULT_SHELL

• CONFIG_MEMFAULT_RAM_BACKED_COREDUMP

• CONFIG_MEMFAULT_RAM_BACKED_COREDUMP_SIZE

• CONFIG_MEMFAULT_COREDUMP_COLLECT_DATA_REGIONS

• CONFIG_MEMFAULT_COREDUMP_COLLECT_BSS_REGIONS

• CONFIG_MEMFAULT_HTTP_ENABLE

• CONFIG_MEMFAULT_HTTP_PERIODIC_UPLOAD_INTERVAL_SECS

• CONFIG_MEMFAULT_HTTP_PERIODIC_UPLOAD_USE_DEDICATED_WORKQUEUE

• CONFIG_MEMFAULT_EVENT_STORAGE_SIZE

• CONFIG_MEMFAULT_CLEAR_RESET_REG

• CONFIG_MEMFAULT_METRICS

• CONFIG_MEMFAULT_METRICS_DEFAULT_SET_ENABLE

• CONFIG_MEMFAULT_HTTP_PERIODIC_UPLOAD

• CONFIG_MEMFAULT_ROOT_CERT_STORAGE_NRF9160_MODEM

For more details on each option, use menuconfig or guiconfig, and see the Kconfig sources in modules/lib/memfault-firmware-sdk/ports/zephyr/Kconfig.

Note

The Memfault shell is enabled by default, using the UART interface. If AT Host library and the Memfault module are enabled simultaneously, both will not behave as expected, as they both require the same UART interface. Therefore, it is recommended to enable only one of these at a time. To disable the Memfault shell, you need to disable the Kconfig options CONFIG_MEMFAULT_SHELL and CONFIG_MEMFAULT_NRF_SHELL.

Configuration options in nRF Connect SDK

The Kconfig options for Memfault that are defined in nRF Connect SDK provide some additional features compared to the options that are already implemented in Memfault SDK:

• CONFIG_MEMFAULT_NCS_PROJECT_KEY

• CONFIG_MEMFAULT_NCS_PROVISION_CERTIFICATES

• CONFIG_MEMFAULT_NCS_INTERNAL_FLASH_BACKED_COREDUMP

• CONFIG_MEMFAULT_NCS_LTE_METRICS

• CONFIG_MEMFAULT_NCS_STACK_METRICS

• CONFIG_MEMFAULT_NCS_BT_METRICS

The nRF Connect SDK integration of Memfault SDK provides default values for some metadata that is required to identify the firmware when it is sent to Memfault cloud. You can control the defaults by using the configuration options below:

• CONFIG_MEMFAULT_NCS_DEVICE_ID

• CONFIG_MEMFAULT_NCS_HW_VERSION

• CONFIG_MEMFAULT_NCS_FW_TYPE

• CONFIG_MEMFAULT_NCS_FW_VERSION_STATIC

• CONFIG_MEMFAULT_NCS_FW_VERSION_PREFIX

The Kconfig options for CONFIG_BT_MDS are the following:

• CONFIG_BT_MDS_MAX_URI_LENGTH

• CONFIG_BT_MDS_PERM_RW

• CONFIG_BT_MDS_PERM_RW_ENCRYPT

• CONFIG_BT_MDS_PIPELINE_COUNT

• CONFIG_BT_MDS_DATA_POLL_INTERVAL

API documentation

Header file: include/memfault_ncs.h

Source files: modules/memfault/

group memfault_ncs

Convenience functions for using Memfault firmware SDK with nRF Connect SDK.

Functions

int memfault_ncs_device_id_set(const char *device_id, size_t len)

Set the Memfault device ID.

Note

In order to use this API successfully, CONFIG_MEMFAULT_NCS_DEVICE_ID_RUNTIME must be enabled.

Parameters:

• device_id – Pointer to device ID buffer

• len – Length of device ID. Cannot exceed CONFIG_MEMFAULT_NCS_DEVICE_ID_MAX_LEN.

Returns:

0 on success, otherwise a negative error code

void memfault_ncs_metrics_collect_data(void)

Trigger NCS metrics collection. Called by default from NCS memfault_metrics_heartbeat_collect_data(), but can instead be called from user’s implementation of memfault_metrics_heartbeat_collect_data(), see CONFIG_MEMFAULT_NCS_IMPLEMENT_METRICS_COLLECTION Kconfig option.