Is exectuion of nrf_modem_at_cmd "blocking"?

[marsal]

Hi, 

for 9161, I'd like to query periodically the modem using nrf_modem_at_cmd, doing this in a dedicated thread.

My question is: If I launch such AT command query, is the thread which does this (and then also other threads) blocked until the response from modem comes back or the execution of nrf_modem_at_cmd is "non-blocking"?

I am aware of  nrf_modem_at_cmd_async, but I do not need it necessarily.

Thank you!

[Håkon Alseth]

Hi,

 

The nrf_modem API is thread safe, and can safely be used in several threads:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc-legacy/2.0.0/nrfxlib/nrf_modem/doc/at_interface.html#thread-safety

 

My question is: If I launch such AT command query, is the thread which does this (and then also other threads) blocked until the response from modem comes back or the execution of nrf_modem_at_cmd is "non-blocking"?

Given that it is a blocking call, ie. will return once the function has executed, it will effectively block the current thread. However; it will yield when awaiting modem response, thus it will allow equal or higher priority threads to execute. You can read more about the scheduling in the kernel here:

https://docs.zephyrproject.org/latest/kernel/services/scheduling/index.html

 

Kind regards,

Håkon

[marsal]

Thanks a lot, Hakon! The yield explains it.

[Håkon Alseth]

Happy to help! Hope you have a wonderful weekend!

 

Cheers,

Håkon