|
| 1 | +### Changes between Memfault SDK 0.32.0 and SDK 0.31.5 - Aug 7, 2022 |
| 2 | + |
| 3 | +#### :chart_with_upwards_trend: Improvements |
| 4 | + |
| 5 | +- [ModusToolbox:tm: Software](https://www.infineon.com/cms/en/design-support/tools/sdk/modustoolbox-software/) |
| 6 | + port updates |
| 7 | + - Added heartbeat metrics for heap and Wi-Fi performance tracking when using |
| 8 | + the default port for |
| 9 | + [CAT1A (PSoC:tm: 6)](https://github.com/Infineon/mtb-pdl-cat1). See |
| 10 | + [ports/cypress/psoc6/memfault_platform_core.c](ports/cypress/psoc6/memfault_platform_core.c) |
| 11 | + for more details |
| 12 | + - Fixed reboot reason reported when PSoC 6 is fully reset to report "Power On |
| 13 | + Reset" instead of "Unknown" |
| 14 | +- Zephyr port updates |
| 15 | + - Memfault logs (eg `MEMFAULT_LOG_DEBUG()` etc) are now routed to the Zephyr |
| 16 | + logging infrastructure. The typical set of Kconfig options for Memfault logs |
| 17 | + are available (`CONFIG_MEMFAULT_LOG_LEVEL_WRN` etc). See details in |
| 18 | + "Breaking Changes" below for enabling logs in your project. |
| 19 | + - Added a new Kconfig option, `MEMFAULT_ZEPHYR_FATAL_HANDLER`, which can be |
| 20 | + used to disable the Zephyr fault handler print facilities. |
| 21 | + |
| 22 | +#### :boom: Breaking Changes |
| 23 | + |
| 24 | +- Users will no longer see internal Memfault log output by default, but will |
| 25 | + have to enable it explicitly to see the output: |
| 26 | + |
| 27 | + ```ini |
| 28 | + # enable LOG |
| 29 | + CONFIG_LOG=y |
| 30 | + # not required- enabling the Memfault logging component enables including the |
| 31 | + # log buffer in coredumps |
| 32 | + CONFIG_MEMFAULT_LOGGING_ENABLE=y |
| 33 | + |
| 34 | + # if on pre-v3.1.0 zephyr, you can choose either the default LOG v1 |
| 35 | + # implementation, or select a LOG2 mode to enable LOG2. on zephyr 3.1.0+, LOG |
| 36 | + # v1 is removed and LOG v2 is now the only log implementation |
| 37 | + # CONFIG_LOG2_MODE_DEFERRED=y |
| 38 | + |
| 39 | + # make sure to select a log backend to see the output |
| 40 | + CONFIG_LOG_BACKEND_UART=y |
| 41 | + ``` |
| 42 | + |
| 43 | + The log statements affected by this change are likely only the internal |
| 44 | + Memfault SDK logs (`MEMFAULT_LOG_DEBUG()` etc), unless those macros are used |
| 45 | + in the user application. |
| 46 | + |
| 47 | +- Removed support for Zephyr LTS release 1.14 as it was superseded by |
| 48 | + [LTS V2 almost a year ago now](https://www.zephyrproject.org/zephyr-lts-v2-release/). |
| 49 | + A project using this release of Zephyr must target a memfault-firmware-sdk |
| 50 | + release less than 0.32.0. |
| 51 | + |
| 52 | +#### :house: Internal |
| 53 | + |
| 54 | +- More logically grouped Kconfig settings in Zephyr example app's |
| 55 | + [prj.conf](examples/zephyr/apps/memfault_demo_app/prj.conf) |
| 56 | +- Fixed a few typos in particle port documentation |
| 57 | +- Simplified compilation steps for the |
| 58 | + [nRF91 sample test app](examples/nrf-connect-sdk/nrf9160/memfault_demo_app) |
| 59 | + when compiling with older releases of the nRF Connect SDK and refreshed the |
| 60 | + example to target the v2.0.2 release by default |
| 61 | +- Updated default demo CLI commands to better align with |
| 62 | + [our suggested integration test commands](https://mflt.io/mcu-test-commands). |
| 63 | + The default set now looks like this: |
| 64 | + |
| 65 | + ```bash |
| 66 | + mflt> help |
| 67 | + clear_core: Clear an existing coredump |
| 68 | + drain_chunks: Flushes queued Memfault data. To upload data see https://mflt.io/posting-chunks-with-gdb |
| 69 | + export: Export base64-encoded chunks. To upload data see https://mflt.io/chunk-data-export |
| 70 | + get_core: Get coredump info |
| 71 | + get_device_info: Get device info |
| 72 | + test_assert: Trigger memfault assert |
| 73 | + test_busfault: Trigger a busfault |
| 74 | + test_hardfault: Trigger a hardfault |
| 75 | + test_memmanage: Trigger a memory management fault |
| 76 | + test_usagefault: Trigger a usage fault |
| 77 | + test_log: Writes test logs to log buffer |
| 78 | + test_log_capture: Trigger capture of current log buffer contents |
| 79 | + test_reboot: Force system reset and track it with a trace event |
| 80 | + test_trace: Capture an example trace event |
| 81 | + help: Lists all commands |
| 82 | + ``` |
| 83 | + |
1 | 84 | ### Changes between Memfault SDK 0.31.5 and SDK 0.31.4 - July 22, 2022
|
2 | 85 |
|
3 | 86 | #### :chart_with_upwards_trend: Improvements
|
|
0 commit comments