sd_rpc_open hangs for ever if sd_rpc_close was not called

RE: sd_rpc_open hangs for ever if sd_rpc_close was not called

jon — Mon, 07 Dec 2015 02:24:14 GMT

This doesn't work for me very well. I am calling sd_rpc_close() before my program exits (and getting NRF_SUCCESS return value), but I still can't connect the next time I run my program. The behavior I am seeing is this:

First time running program, works fine. Calls nrfjprog --pinreset and beginning and calls sd_rpc_close() at end.
Second time, calls nrfjprog --pinreset (also tried nrfjprog --reset), hangs at sd_rpc_open(). Have to manually close program.
Third time, runs flawlessly as in step 1.

What is going on?

RE: sd_rpc_open hangs for ever if sd_rpc_close was not called

jpo38 — Fri, 27 Nov 2015 12:52:25 GMT

I can't run those commands because nrfproj and JLinkExe are not deployed on the machine running my program. But as far as there's a plan to have it fixed, that's fine for me.

RE: sd_rpc_open hangs for ever if sd_rpc_close was not called

Vidar Berg — Fri, 27 Nov 2015 12:49:29 GMT

Hi, the problem is that the transport layer looses sync with the host when not closed beforehand. The development team is aware of this. A workaround is to reset the device before you start your script. You can make a script to do the reset it via the Segger programmer.

E.g., using nrfjprog:

nrfjprog --reset

Or Jlink commander:

>JLinkExe

>device nrf51

>r //reset and halt

>g // "go" start execution

>q // exit Jlink commander