Shifting to v2.5.1 from v2.3.0 I start getting MPU FAULTS, on my own project (when establishing BLE connection).
So I tried the peripheral_lbs sample project. The MPU FAULT is still there:
*** Booting nRF Connect SDK v2.5.1 ***
Starting Bluetooth Peripheral LBS example
I: 6 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: SoftDevice Controller build revision:
I: c5 93 ba a9 14 4d 8d 05 |.....M..
I: 30 4e 9b 92 d7 71 1e e8 |0N...q..
I: aa 02 50 3c |..P<
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: C5:E8:50:B6:06:33 (random)
I: HCI: version 5.4 (0x0d) revision 0x1102, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x1102
E: ***** HARD FAULT *****
E: Fault escalation (see below)
E: ***** MPU FAULT *****
E: Stacking error (context area might be not valid)
E: Data Access Violation
E: MMFAR Address: 0x20005a30
E: r0/a1: 0xd598c43c r1/a2: 0x91528dac r2/a3: 0xe6a3d79b
E: r3/a4: 0x0a467350 r12/ip: 0x7eb7952e r14/lr: 0xcda3adb1
E: xpsr: 0x61000000
E: Faulting instruction address (r15/pc): 0x0000b924
E: >>> ZEPHYR FATAL ERROR 19: Unknown error on CPU 0
E: Current thread: 0x20002650 (main)
E: Resetting system
