If the softdevice is enabled, can I call the function of "nrf_mtx.h"? If I could, would something bad happen?

RE: If the softdevice is enabled, can I call the function of "nrf_mtx.h"? If I could, would something bad happen?

Gray — Fri, 05 Jun 2020 08:54:27 GMT

Ok, I understand. Thanks again for your answers.

RE: If the softdevice is enabled, can I call the function of "nrf_mtx.h"? If I could, would something bad happen?

Simonr — Fri, 05 Jun 2020 05:47:05 GMT

Yes, if you're using the nrf_mtx library in an application also sporting the SoftDevice the nrf_mtx functions will be prone to interrupts by the SoftDevice. The sd_mutex functions will be handled by the SoftDevice itself, so the SoftDevice will make sure that it won't be interrupted.

Best regards,

Simon

RE: If the softdevice is enabled, can I call the function of "nrf_mtx.h"? If I could, would something bad happen?

Gray — Thu, 04 Jun 2020 13:04:05 GMT

Hi,Simon.

Thanks for your answers.

And can I understand that when using the SoftDevice,I can call the nrf_mtx_trylock() function?But the calling process can be interrupted?And the sd_mutex function will not be interrupted.

RE: If the softdevice is enabled, can I call the function of "nrf_mtx.h"? If I could, would something bad happen?

Simonr — Thu, 04 Jun 2020 10:52:33 GMT

When using the SoftDevice, I would suggest using the sd_mutex functions which are an implementation of mutex that can be used by the application. The mutex functionality itself is handled by the SoftDevice, and due to the characteristics of SVC calls in the ARM architecture, it's atomic. When the SoftDevice is running, you can never interrupt the "lower stack" interrupts. Here, the mutex is atomic, in the sense that grabbing/releasing it is a process that can't be interrupted as it will run through the SoftDevice supervisor call.

Best regards,

Simon