Memfault Firmware SDK 0.33.0 (Build 497178)

Author: Memfault Inc

CHANGES.md

@@ -1,3 +1,29 @@
+### Changes between Memfault SDK 0.33.0 and SDK 0.32.2 - Aug 18, 2022
+
+#### :chart_with_upwards_trend: Improvements
+
+- Extend [memfault demo shell](components/demo/src/memfault_demo_shell.c) to
+  support terminals that only emit CR for line endings
+- nRF5 SDK Updates:
+  - Added a [software watchdog](https://mflt.io/root-cause-watchdogs) reference
+    port for nRF5 SDK which makes use of the RTC Peripheral. See
+    [ports/nrf5_sdk/software_watchdog.c](ports/nrf5_sdk/software_watchdog.c) for
+    more details.
+  - Updated [nRF5 example app](examples/nrf5/apps/memfault_demo_app/) to make
+    use of hardware and new software watchdog port.
+- Zephyr Port Updates:
+  - Added Kconfig option to fallback to using `printk` by default when no
+    logging is enabled. This can be disabled by setting
+    `CONFIG_MEMFAULT_PLATFORM_LOG_FALLBACK_TO_PRINTK=n`.
+- nRF Connect SDK Updates:
+  - Fixed a :bug: which could result in download errors when using
+    [Memfault nRF Connect SDK FOTA client](ports/nrf-connect-sdk/zephyr/include/memfault/nrfconnect_port/fota.h)
+    and enabled client in example application by default.
+  - Added new example application for trying Memfault with nRF53 & nRF52 based
+    development kits. See
+    [examples/nrf-connect-sdk/nrf5](examples/nrf-connect-sdk/nrf5) for more
+    details.
+
 ### Changes between Memfault SDK 0.32.2 and SDK 0.32.1 - Aug 16, 2022
 
 #### :chart_with_upwards_trend: Improvements

VERSION

@@ -1,2 +1,2 @@
-BUILD ID: 494632
-GIT COMMIT: b2b683510
+BUILD ID: 497178
+GIT COMMIT: 3f51dc76a

components/demo/src/memfault_demo_shell.c

@@ -28,6 +28,8 @@
 static struct MemfaultShellContext {
   int (*send_char)(char c);
   size_t rx_size;
+  // the char we will ignore when received end-of-line sequences
+  char eol_ignore_char;
   char rx_buffer[MEMFAULT_DEMO_SHELL_RX_BUFFER_SIZE];
 } s_mflt_shell;
 
@@ -43,7 +45,7 @@ static void prv_send_char(char c) {
 }
 
 static void prv_echo(char c) {
-  if ('\n' == c) {
+  if (c == '\n') {
     prv_send_char('\r');
     prv_send_char('\n');
   } else if ('\b' == c) {
@@ -129,13 +131,34 @@ static void prv_process(void) {
 }
 
 void memfault_demo_shell_boot(const sMemfaultShellImpl *impl) {
+  s_mflt_shell.eol_ignore_char = 0;
   s_mflt_shell.send_char = impl->send_char;
   prv_reset_rx_buffer();
   prv_echo_str("\n" MEMFAULT_SHELL_PROMPT);
 }
 
+//! Logic to deal with CR, LF, CRLF, or LFCR end-of-line (EOL) sequences
+//! @return true if the character should be ignored, false otherwise
+static bool prv_should_ignore_eol_char(char c) {
+  if (s_mflt_shell.eol_ignore_char != 0) {
+    return (c == s_mflt_shell.eol_ignore_char);
+  }
+
+  //
+  // First end of line character detected. We will use this character as our EOL delimiter and
+  // ignore the opposite character when we see it in the future.
+  //
+
+  if (c == '\r') {
+    s_mflt_shell.eol_ignore_char = '\n';
+  } else if (c == '\n') {
+    s_mflt_shell.eol_ignore_char = '\r';
+  }
+  return false;
+}
+
 void memfault_demo_shell_receive_char(char c) {
-  if (c == '\r' || prv_is_rx_buffer_full() || !prv_booted()) {
+  if (prv_should_ignore_eol_char(c) || prv_is_rx_buffer_full() || !prv_booted()) {
     return;
   }
 
@@ -144,6 +167,11 @@ void memfault_demo_shell_receive_char(char c) {
     return; // nothing left to delete so don't echo the backspace
   }
 
+  // CR are our EOL delimiter. Remap as a LF here since that's what internal handling logic expects
+  if (c == '\r') {
+    c = '\n';
+  }
+
   prv_echo(c);
 
   if (is_backspace) {

components/include/memfault/version.h

@@ -19,7 +19,7 @@ typedef struct {
   uint8_t patch;
 } sMfltSdkVersion;
 
-#define MEMFAULT_SDK_VERSION   { .major = 0, .minor = 32, .patch = 2 }
+#define MEMFAULT_SDK_VERSION   { .major = 0, .minor = 33, .patch = 0 }
 
 #ifdef __cplusplus
 }

examples/nrf-connect-sdk/nrf5/.gitignore

@@ -0,0 +1,11 @@
+/bootloader
+/build
+/mbedtls
+/modules
+/nrf
+/nrfxlib
+/sparc
+/test
+/tools
+/.west
+/zephyr

examples/nrf-connect-sdk/nrf5/README.md

@@ -0,0 +1,69 @@
+# nRF-Connect Memfault Example
+
+This is a small example application showing a Memfault integration running on an
+nrf52840 development board, using the nRF Connect SDK. Any nRF board should also
+work. The example has been tested on:
+
+- nRF52840-DK
+- nRF5340-DK
+
+## Usage
+
+Make sure you have the Zephyr / nRF-Connect tools installed first:
+
+<https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.2/nrf/gs_installing.html>
+
+To build and flash this example to an nRF52840-DK (PCA10056), run the following
+commands:
+
+```bash
+❯ west init --local memfault_demo_app
+❯ west update
+❯ west build --board nrf52840dk_nrf52840 memfault_demo_app
+❯ west flash
+```
+
+Open a serial terminal to access the console:
+
+```bash
+# for example, pypserial-miniterm
+❯ pyserial-miniterm --raw /dev/ttyACM0 115200
+```
+
+The console has several Memfault test commands available:
+
+```bash
+uart:~$ mflt help
+mflt - Memfault Test Commands
+Subcommands:
+  reboot              :trigger a reboot and record it using memfault
+  get_core            :gets the core
+  clear_core          :clear the core
+  crash               :trigger a crash
+  test_log            :Writes test logs to log buffer
+  trigger_logs        :Trigger capture of current log buffer contents
+  hang                :trigger a hang to test watchdog functionality
+  export              :dump chunks collected by Memfault SDK using
+                       https://mflt.io/chunk-data-export
+  trace               :Capture an example trace event
+  get_device_info     :display device information
+  post_chunks         :Post Memfault data to cloud
+  trigger_heartbeat   :Trigger an immediate capture of all heartbeat metrics
+  get_latest_release  :checks to see if new ota payload is available
+```
+
+For example, to test the coredump functionality:
+
+1. run `mflt crash` and wait for the board to reset
+2. run `mflt get_core` to confirm the coredump was saved
+3. run `mflt export` to print out the base-64 chunks:
+
+   ```plaintext
+   uart:~$ mflt export
+   <inf> <mflt>: MC:SE4DpwIEAwEKbW5yZjUyX2V4YW1wbGUJZTAuMC4xBmFhC0Z5RE1gF8EEhgFpSW5mbyBsb2chAmxXYXJuaW5nIGxvZyEDakVycm9yIGxvZyE=:
+   <inf> <mflt>: MC:gE6A/A==:
+   ```
+
+4. upload the chunks to Memfault. see here for details:
+
+   <https://mflt.io/chunks-debug>

examples/nrf-connect-sdk/nrf5/memfault_demo_app/CMakeLists.txt

@@ -0,0 +1,28 @@
+# SPDX-License-Identifier: Apache-2.0
+
+cmake_minimum_required(VERSION 3.20.0)
+
+find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
+project(fs_shell)
+
+FILE(GLOB app_sources src/*.c)
+target_sources(app PRIVATE ${app_sources})
+
+zephyr_include_directories(config)
+
+# Normalize dbug + __FILE__ paths to relative locations:
+# 1. west workspace
+# 2. toolchain install location (applies to paths in cross tool library files)
+#
+# If debugging from location 1., the west-manifest files should already have the
+# correct relative path for GDB to locate them, otherwise the GDB "directory"
+# command can be used to tell GDB where to find the source files (also required
+# if the cross tool libraries/headers need to be located by GDB)
+get_filename_component(WEST_PROJECT_ROOT_PATH
+                       "${CMAKE_CURRENT_LIST_DIR}/.."
+                       ABSOLUTE)
+zephyr_compile_options(
+    -ffile-prefix-map=${WEST_PROJECT_ROOT_PATH}=.
+    -ffile-prefix-map=${TOOLCHAIN_HOME}=.
+    -Wa,--debug-prefix-map=${WEST_PROJECT_ROOT_PATH}=.
+)

examples/nrf-connect-sdk/nrf5/memfault_demo_app/config/memfault_metrics_heartbeat_config.def

@@ -0,0 +1,9 @@
+#pragma once
+
+//! @file
+//!
+//! Copyright (c) Memfault, Inc.
+//! See License.txt for details
+//!
+//! Platform overrides for the default configuration settings in the memfault-firmware-sdk.
+//! Default configuration settings can be found in "memfault/config.h"

examples/nrf-connect-sdk/nrf5/memfault_demo_app/config/memfault_platform_config.h

@@ -0,0 +1,5 @@
+// This is where project specific trace reasons should be defined
+// using the MEMFAULT_TRACE_REASON_DEFINE macro
+//
+// For example:
+// MEMFAULT_TRACE_REASON_DEFINE(your_custom_error_reason)