periodic_sync HardFault with ASSERT: 50, 5233

Question

Hi,

I'm trying to use the periodic sync sample app using 2 nrf52833DK (one for advertising and one for receiving sync) and been getting this assert message every time a sync advertisement arrives:

▒*** Booting nRF Connect SDK v3.5.99-ncs1-1 *** system
Starting Periodic Advertising Synchronization Demo
Checking LED device...done.
Configuring GPIO pin...done.
[00:00:00.000,671] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision:
                                            36 f0 e5 0e 87 68 48 fb  02 fd 9f 82 cc 32 e5 7b |6....hH. .....2.{
                                            91 b1 5c ed                                      |..\.
[00:00:00.002,441] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.002,471] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.002,502] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
[00:00:00.003,234] <inf> bt_hci_core: Identity: C3:99:2C:E5:16:57 (random)
[00:00:00.003,295] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x118f, manufacturer 0x0059
[00:00:00.003,326] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x118f
Scan callbacks register...success.
Periodic Advertising callbacks register...Success.
Start scanning...success.
Start blinking LED...
Waiting for periodic advertising...
[00:00:02.015,563] <err> bt_sdc_hci_driver: SoftDevice Controller ASSERT: 50, 5233
[00:00:02.015,563] <err> os: ***** HARD FAULT *****
[00:00:02.015,563] <err> os:   Fault escalation (see below)
[00:00:02.015,594] <err> os: ARCH_EXCEPT with reason 3

[00:00:02.015,594] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00004002
[00:00:02.015,625] <err> os: r3/a4:  0x00000000 r12/ip:  0x200018d8 r14/lr:  0x00000000
[00:00:02.015,625] <err> os:  xpsr:  0x41000011
[00:00:02.015,625] <err> os: Faulting instruction address (r15/pc): 0x00016c44
[00:00:02.015,686] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:02.015,686] <err> os: Fault during interrupt handling

[00:00:02.015,716] <err> os: Current thread: 0x200027b0 (unknown)

I've seen this thread describing something very similar, but it is from a year ago and the recommendation to use later release does not apply since I am using a release later than the one described in the thread.

What might be the cause for this assert?

Is there any tool that can help me understand such messages?

Thanks,

Guy.