Hard Fault Zephyr during scan with shell BLE command

[Piwy]

HI,

I have an error that occured during scan with shell command :

[00:02:04.392,181] <err> sdc_hci_driver: SoftDevice Controller ASSERT: 50, 5399
[00:02:04.392,211] <err> os: ***** HARD FAULT *****
[00:02:04.392,211] <err> os:   Fault escalation (see below)
[00:02:04.392,242] <err> os: ARCH_EXCEPT with reason 3

[00:02:04.392,242] <err> os: r0/a1:  0x00000003  r1/a2:  0x01884dce  r2/a3:  0x01887c35
[00:02:04.392,272] <err> os: r3/a4:  0x00000001 r12/ip:  0xffffffff r14/lr:  0x0004d94f
[00:02:04.392,272] <err> os:  xpsr:  0x61000011
[00:02:04.392,272] <err> os: Faulting instruction address (r15/pc): 0x0004a106
[00:02:04.392,303] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:02:04.392,303] <err> os: Fault during interrupt handling

[00:02:04.392,333] <err> os: Current thread: 0x20003e78 (idle)
[00:02:04.523,834] <err> fatal_error: Resetting system

The first line change sometimes it's : <err> mpsl_init: MPSL ASSERT: 112, 2846

or also :

<err> sdc_hci_driver: SoftDevice Controller ASSERT: 53, 2663

There isn't error when i connect or use gatt command but juste error with the scan.

And i have another question on another topic, it's about the name of a peripheral device, the name appear when the peripheral is in 1M PHY but he don't apprear when the device is in Coded PHY, do you know why ?

regards,

Py

[Jared]

Hi there,

Which NCS version are you using, master branch? 

The assert indicates that something is not correct with your configs, can you share your project config file?

And i have another question on another topic, it's about the name of a peripheral device, the name appear when the peripheral is in 1M PHY but he don't apprear when the device is in Coded PHY, do you know why ?

Can you make a new ticket for this problem?

regards

Jared 

[Piwy]

Thanks you for your reply.

But the radio_test sample can change output_power, is it the same as tx_power ?

regards,

Pierre-Yves

[Hung Bui]

Hi Pierre-Yves, 
Yes they are basically the same. 
However, when you do BLE you would need to request the tx_power/output_power change to the BLE controller, you can't access the radio directly. 

Please follow the code on how to change tx_power using HCI command in the case I pointed to.