MPU Fault in mesh light sample

RE: MPU Fault in mesh light sample

boris bergman1 — Fri, 22 Sep 2023 14:54:14 GMT

BT Mesh settings workq: STACK: unused 368 usage 1032 / 1400 (73 %); CPU: 0 %
      : Total CPU cycles used: 222
 BT CTLR ECDH        : STACK: unused 704 usage 200 / 904 (22 %); CPU: 0 %
      : Total CPU cycles used: 1
 BT RX               : STACK: unused 920 usage 3080 / 4000 (77 %); CPU: 0 %
      : Total CPU cycles used: 135912
 BT TX               : STACK: unused 896 usage 640 / 1536 (41 %); CPU: 0 %
      : Total CPU cycles used: 1499
 thread_analyzer     : STACK: unused 584 usage 440 / 1024 (42 %); CPU: 0 %
      : Total CPU cycles used: 15439
 sysworkq            : STACK: unused 936 usage 1112 / 2048 (54 %); CPU: 0 %
      : Total CPU cycles used: 28933
 MPSL Work           : STACK: unused 472 usage 552 / 1024 (53 %); CPU: 1 %
      : Total CPU cycles used: 436337
 BT_LW_WQ            : STACK: unused 476 usage 828 / 1304 (63 %); CPU: 0 %
      : Total CPU cycles used: 144
 logging             : STACK: unused 1432 usage 616 / 2048 (30 %); CPU: 2 %
      : Total CPU cycles used: 676852
 idle                : STACK: unused 216 usage 104 / 320 (32 %); CPU: 95 %
      : Total CPU cycles used: 28679255
 ISR0                : STACK: unused 936 usage 1112 / 2048 (54 %)

bt_rx just didn't fit in the stack. Didn't know it had too be that big, issue is resolved now.

RE: MPU Fault in mesh light sample

boris bergman1 — Fri, 22 Sep 2023 14:10:41 GMT

I have the same issue.

Initializing...
[00:00:00.008,483] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.008,514] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:00.008,514] <inf> fs_nvs: data wra: 0, 0
[00:00:00.008,697] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
                                            e0 7e 2e c1 5e 05 85 23  46 15 dc fa 8e 29 7d 70 |.~..^..# F....)}p
                                            10 93 a5 fc                                      |....             
[00:00:00.013,000] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.013,031] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.013,061] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
[00:00:00.013,519] <inf> bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
[00:00:00.426,666] <inf> bt_hci_core: Identity: E1:69:11:7E:78:B6 (random)
[00:00:00.426,696] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x1077, manufacturer 0x0059
[00:00:00.426,727] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x1077
Mesh initialized
[00:00:07.359,436] <wrn> bt_att: Unhandled ATT code 0x1d
[00:00:20.132,965] <inf> bt_mesh_main: Primary Element: 0x0026
[00:00:24.226,898] <wrn> bt_att: Unhandled ATT code 0x1d
[00:00:26.784,393] <err> os: ***** MPU FAULT *****
[00:00:26.784,423] <err> os:   Stacking error (context area might be not valid)
[00:00:26.784,454] <err> os:   Data Access Violation
[00:00:26.784,454] <err> os:   MMFAR Address: 0x20008830
[00:00:26.784,484] <err> os: r0/a1:  0x00000000  r1/a2:  0x2000625c  r2/a3:  0x00000000
[00:00:26.784,515] <err> os: r3/a4:  0xe000ed00 r12/ip:  0x20006984 r14/lr:  0x00000000
[00:00:26.784,515] <err> os:  xpsr:  0x21000000
[00:00:26.784,545] <err> os: Faulting instruction address (r15/pc): 0x0004c73c
[00:00:26.784,576] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:26.784,637] <err> os: Current thread: 0x20002da0 (BT RX)

Same sample, same board, platform v2.4.2. Also I configured CONFIG_BT_RX_STACK_SIZE=3000. Get the error already when I provision with nrf app.

RE: MPU Fault in mesh light sample

Joakim Jakobsen — Thu, 16 Mar 2023 23:10:13 GMT

Glad you figured it out.

Thanks for sharing the solution.

Br,
Joakim

RE: MPU Fault in mesh light sample

Mustafa — Tue, 14 Mar 2023 11:16:49 GMT

Hey Joakim,

Actually, I had to increase CONFIG_BT_RX_STACK_SIZE, then it worked on my side.

RE: MPU Fault in mesh light sample

Joakim Jakobsen — Tue, 14 Mar 2023 11:02:30 GMT

Hi.

Sorry about the delay. I wanted to test the sample before getting back to you. Have you made any progress on the issue, or do you still need assistance?

I couldn't see the same issue testing with a nRF52840-DK.

Br,
Joakim