Hello,
is there a way to check for NRF_ERROR_BUSY
before issuing a new command?
The idea would be to create a timer to retry issuing a/the command if the NRF is not busy any more.
(I am currently on SDK 9, S130)
Thanks!
Hello,
is there a way to check for NRF_ERROR_BUSY
before issuing a new command?
The idea would be to create a timer to retry issuing a/the command if the NRF is not busy any more.
(I am currently on SDK 9, S130)
Thanks!
Hello Daniel, it is complicated. The app has both GATTC and GATTS. Many things can happen asynchronously/concurrently. I was thinking of an architecture to deal with this, so I was looking at my (API) options. :)
Hello Daniel, it is complicated. The app has both GATTC and GATTS. Many things can happen asynchronously/concurrently. I was thinking of an architecture to deal with this, so I was looking at my (API) options. :)