nRF52833 custom board Hard Fault when using Bluetooth

[Kesims]

Hello,

I am trying to get into Zephyr development and for my project I have created a custom board based on nRF52833 QDAA (40 pin). I have been successfully able to verify the board functionality using the nRF5 SDK by using some of the examples provided by Nordic.

Unfortunately I am running into issues when trying to use nRF Connect SDK (version 2.5.0).

The board seems to work pretty well, but when I enable Bluetooth (for example just a simple advertising), the board successfully starts up, sends out one advertisement packet and then crashes.

Fullscreen

1

2

3

4

5

6

7

8

9

10

11

12

13

14

[00:00:00.017,547] <err> mpsl_init: MPSL ASSERT: 112, 2185

[00:00:00.017,578] <err> os: ***** HARD FAULT *****

[00:00:00.017,578] <err> os: Fault escalation (see below)

[00:00:00.017,608] <err> os: ARCH_EXCEPT with reason 3

[00:00:00.017,608] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x00000009

[00:00:00.017,639] <err> os: r3/a4: 0x20001090 r12/ip: 0x20000970 r14/lr: 0x0000bbe5

[00:00:00.017,639] <err> os: xpsr: 0x41000018

[00:00:00.017,669] <err> os: Faulting instruction address (r15/pc): 0x000108b8

[00:00:00.017,700] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0

[00:00:00.017,730] <err> os: Fault during interrupt handling

[00:00:00.017,761] <err> os: Current thread: 0x20001090 (logging)

[00:00:00.478,393] <err> os: Halting system

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

[00:00:00.017,547] <err> mpsl_init: MPSL ASSERT: 112, 2185
[00:00:00.017,578] <err> os: ***** HARD FAULT *****
[00:00:00.017,578] <err> os:   Fault escalation (see below)
[00:00:00.017,608] <err> os: ARCH_EXCEPT with reason 3

[00:00:00.017,608] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000009
[00:00:00.017,639] <err> os: r3/a4:  0x20001090 r12/ip:  0x20000970 r14/lr:  0x0000bbe5
[00:00:00.017,639] <err> os:  xpsr:  0x41000018
[00:00:00.017,669] <err> os: Faulting instruction address (r15/pc): 0x000108b8
[00:00:00.017,700] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:00.017,730] <err> os: Fault during interrupt handling

[00:00:00.017,761] <err> os: Current thread: 0x20001090 (logging)
[00:00:00.478,393] <err> os: Halting system

From the zephyr.map I have found out that the faulting instruction is part of zephyr/arch/arch/arm/core/aarch32/libarch__arm__core__aarch32.a(irq_manage.c.obj).

I am stuck at this issue as I have no idea what could be the cause or how to resolve it, when I build the firmware for nRF52833DK and flash it on the DK, it seems to be running fine.

My prj.conf:

Fullscreen

1

2

3

4

5

6

# Bluetooth configuration

CONFIG_BT=y

CONFIG_BT_DEVICE_NAME="BugPack"

# Logging configuration

CONFIG_LOG=y

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

# Bluetooth configuration
CONFIG_BT=y
CONFIG_BT_DEVICE_NAME="BugPack"

# Logging configuration
CONFIG_LOG=y

To be honest, I have no idea what to do about this, how to debug the issue, as I have just started working with Zephyr. Any help with the issue would be very appreciated.

I will also attach the board schematic and Zephyr board files.

Thank you very much in advance!

Matej


bugpack.zipSchematic_BugPack_v2.pdf