• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 64 subscribers
  • Views 729 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 247644
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Workaround for nrf_send known issue in nRF Connect SDK 1.2.0

Cody

Hello,

I noticed in the release notes for nRF Connect SDK v1.2.0 there is a known issue with the nrf_send function as it relates to blocking for several minutes, see below for the snippet as seen in the release notes:

* The :cpp:func:`nrf_send` function in the :ref:`nrfxlib:bsdlib` might be blocking for several minutes, even if the socket is configured for non-blocking operation.
The behavior depends on the cellular network connection.

I was curious if Nordic can recommend/provide a workaround for this issue. I am seeing instances where this function is blocking for 10+ minutes.

Thanks,
Cody

Parents
  • 0

    Hi Cody,

    We are aware of this and there should come a new patch in "nrfxlib" in the near future in the NCS that will handle this.


    There will be introduced timeout support in the send() function and support for the flag NRF_MSG_DONTWAIT on the send() function. In your case here it would return the error code "EAGAIN" if you would use this flag.

    The only thing you would need to do is to update your code to understand/handle the return of the error codes "EAGAIN", "EWOULDBLOCK" or "ETIMEOUT" in the case you are using the timeout support.


    Best regards,

    Martin L.

  • 0 in reply to Martin Lesund

    Hi Martin,

    Thank you for the response, do you know if there is a timeline for when this will be released and when it does will it be a patch/backport to 1.2.0 or is it going to be in the next quarterly release (ie v1.3.0)?

    Thanks,
    Cody

Reply Children
Related