Bluetooth Mesh MPU fault with Logging V2

Hi,

Currently, I am building an application with Bluetooth mesh and I tried to use Zephyr's logging v2 modules. However, when I build it I get MPU-fault errors at boot. For verification, I tried it also with a BT mesh sample project. For the test, I used the light fixture example and added the following configs. Each config gave the same result.

CONFIG_LOG_MODE_MINIMAL=n
CONFIG_LOG2_MODE_DEFERRED=y
CONFIG_LOG_BACKEND_UART=y
CONFIG_LOG_MODE_MINIMAL=n
CONFIG_LOG2_MODE_IMMEDIATE=y
CONFIG_LOG_BACKEND_UART=y

I also tried this with RTT backend instead of UART, but also same result.

CONFIG_LOG_BACKEND_RTT=n
CONFIG_LOG_BACKEND_UART=y

Log ouput:

▒*** Booting Zephyr OS build v2.7.99-ncs1-1  ***system
Initializing...
[00:00:00.012,298] <err> os: ***** HARD FAULT *****
[00:00:00.012,329] <err> os:   Fault escalation (see below)
[00:00:00.012,329] <err> os: ***** MPU FAULT *****
[00:00:00.012,329] <err> os:   Data Access Violation
[00:00:00.012,359] <err> os:   MMFAR Address: 0x20006eac
[00:00:00.012,359] <err> os: r0/a1:  0x00000008  r1/a2:  0x00000195  r2/a3:  0x00000000
[00:00:00.012,390] <err> os: r3/a4:  0x00000004 r12/ip:  0x0000019d r14/lr:  0x00000000
[00:00:00.012,390] <err> os:  xpsr:  0x61000000
[00:00:00.012,390] <err> os: Faulting instruction address (r15/pc): 0x0000128c
[00:00:00.012,451] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:00.012,481] <err> os: Current thread: 0x20003708 (main)

Using log minimal or logging v1 does work. Does anyone know how I can get this to work with logging v2?

Setup:

  • nRF52833DK
  • nRF Connect SDK v1.9.1
  • Example: Bluetooth mesh Light fixture

Related