You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce necessary changes to support timing out waiting
for a command response:
1. Handle nrf_rpc_os_msg_get() returning null data pointer,
indicating that the response has not arrived within
the required maximum time.
2. Introduce context mutex to protect all context members.
This is necessary because now the response may arrive
after the initiating thread has already released the
context.
Note that 2 may not sufficient solution to address another
scenario where the context is freed by the initiator but
is then reused before a delayed response arrives - to solve
this, we likely need to introduce the concept of session
ID or conversation ID to detect outdated packets.
Signed-off-by: Damian Krolik <[email protected]>
Copy file name to clipboardExpand all lines: nrf_rpc/CHANGELOG.rst
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,18 @@ Changelog
9
9
10
10
All the notable changes to this project are documented on this page.
11
11
12
+
nRF Connect SDK v3.0.99
13
+
***********************
14
+
15
+
Added
16
+
=====
17
+
18
+
* Added a timeout feature for awaiting command responses.
19
+
This change required making the following changes to the nRF RPC OS abstraction layer:
20
+
21
+
* Introduced the :c:struct:`nrf_rpc_os_mutex` structure to protect the nRF RPC thread-local context.
22
+
* Updated the :c:func:`nrf_rpc_os_msg_get` function to unlock the thread-local context mutex and to allow returning no data from the function if a timeout occurs.
0 commit comments