nRF5340 control radio peripheral with Bluetooth enabled

RE: nRF5340 control radio peripheral with Bluetooth enabled

rynze — Fri, 02 Feb 2024 08:25:30 GMT

Thank you very much Jared!

RE: nRF5340 control radio peripheral with Bluetooth enabled

Jared — Thu, 01 Feb 2024 14:39:53 GMT

Hi,

No that is not possible.

The assert that you're getting is because you get a radio interrupt outside a timeslot. In short, if you want to use the radio with Softdevice controller enabled, then you have to use MPSL and timeslots,

regards

Jared

EDIT: I think bt_disable() will do the job to disable the softdevice but I still think you should use timeslots.

RE: nRF5340 control radio peripheral with Bluetooth enabled

rynze — Thu, 01 Feb 2024 07:26:05 GMT

I see! Is it possible to disable SoftDevice manually during initialization, in the code?

Yes, those lines that I mentioned before are my own lines for my radio driver. I am using NCS v2.1.2

RE: nRF5340 control radio peripheral with Bluetooth enabled

Jared — Tue, 30 Jan 2024 12:34:44 GMT

[quote user="rynze"]I am aware of TimeSlots on nRF52 and 51. There I can choose not to start the SoftDevice and use radio without Timeslot API and at the same time be able to call ECB via SVCALL. Is it different for nrf53?[/quote]

Yes, the nRF5340 use Zephyr RTOS which will immediately initialize the Softdevice or Zephyr controller once CONFIG_BT=y is set in the project config. It's not like in the nRF5SDK where you could choose to enable the Softdevice first when it's used. You therefore have to use Timeslot through MPSL if you want access to the Radio peripheral when the CONFIG_BT=y.

[quote user="rynze"]

It seems like it crashes on these lines:

[/quote]

I assume that this are the added lines in your custom radio driver?

Can you specify the NCS version that you're using, and I'll try to track down the root cause of the MPSL assert.

regards

Jared

RE: nRF5340 control radio peripheral with Bluetooth enabled

rynze — Mon, 29 Jan 2024 15:03:10 GMT

Hello,
This is on a development kit.

Tomass

RE: nRF5340 control radio peripheral with Bluetooth enabled

Jared — Mon, 29 Jan 2024 15:02:01 GMT

Hi,

Is this on a custom board or a development kit? If it's on a custom board, can you specify the internal capacitance of the HFXO crystal and the size of the parallel load capacitors?

regards

Jared

RE: nRF5340 control radio peripheral with Bluetooth enabled

rynze — Fri, 26 Jan 2024 14:06:41 GMT

Yes, I am setting CONFIG_BT=y, since it is needed to activate softdevice controller.

Below is debug log from when it crashes:

*** Booting Zephyr OS build cbe3b8fe8b05  ***g system
Main nrf5340dk_nrf5340_cpunet
Initializing radio hardware
[00:00:00.010,101] <err> mpsl_init: MPSL ASSERT: 112, 2183
[00:00:00.010,101] <err> os: ***** HARD FAULT *****
[00:00:00.010,131] <err> os:   Fault escalation (see below)
[00:00:00.010,131] <err> os: ARCH_EXCEPT with reason 3

[00:00:00.010,162] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000001  r2/a3:  0x00000000
[00:00:00.010,162] <err> os: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x010192ef
[00:00:00.010,192] <err> os:  xpsr:  0x69000018
[00:00:00.010,192] <err> os: Faulting instruction address (r15/pc): 0x01016458
[00:00:00.010,223] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:00.010,223] <err> os: Fault during interrupt handling

[00:00:00.010,253] <err> os: Current thread: 0x21002038 (unknown)
*** Booting Zephyr OS build cbe3b8fe8b05  ***ng system
Main nrf5340dk_nrf5340_cpunet
Initializing radio hardware

RE: nRF5340 control radio peripheral with Bluetooth enabled

Jared — Fri, 26 Jan 2024 13:51:54 GMT

[quote user="rynze"]I am assuming that it should be OK to run radio without timeslot API if nor BT nor softdevice are initiated, or am I wrong?[/quote]

No you're correct. But you are setting CONFIG_BT=y in the project config right?

[quote user="rynze"]No, it crashes silently and restarts the core.[/quote]

Can you try to build your application with debug optimizations and see if the log is outputting any error log?

regards
Jared

RE: nRF5340 control radio peripheral with Bluetooth enabled

rynze — Fri, 26 Jan 2024 13:33:31 GMT

Hello again,

No, it crashes silently and restarts the core.
I am assuming that it should be OK to run radio without timeslot API if nor BT nor softdevice are initiated, or am I wrong?

RE: nRF5340 control radio peripheral with Bluetooth enabled

Jared — Fri, 26 Jan 2024 13:21:45 GMT

Hi,

Is any log printed out when it crashes? Any specific error reported on the log?

regards

Jared

RE: nRF5340 control radio peripheral with Bluetooth enabled

rynze — Fri, 26 Jan 2024 10:01:28 GMT

It seems like it crashes on these lines:

NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
NRF_CLOCK->TASKS_HFCLKSTART    = 1;

I am aware of TimeSlots on nRF52 and 51. There I can choose not to start the SoftDevice and use radio without Timeslot API and at the same time be able to call ECB via SVCALL. Is it different for nrf53?

RE: nRF5340 control radio peripheral with Bluetooth enabled

Jared — Fri, 26 Jan 2024 09:55:34 GMT

Hi,

[quote user=""] As soon as I enable bluetooth with CONFIG_BT=y it suddenly starts crashing when I try to initialize my custom radio driver.[/quote]

Can you share the code where you try to initialize your custom driver, what exactly is it doing?

When the Softdevice controller has been enabled, then the Radio and some other peripherals will be restricted and only accessible for the application through Timeslot and the MPSL interface,

regards

Jared