nrf9160 blocking sendto() call for UDP

RE: nrf9160 blocking sendto() call for UDP

miked531 — Fri, 01 Nov 2019 01:42:06 GMT

The newer version of nrfxlib has indeed fixed it. I used nrf v1.1.0-rc1 (followed by west update). Thanks for your help!

RE: nrf9160 blocking sendto() call for UDP

Håkon Alseth — Thu, 31 Oct 2019 14:10:54 GMT

Hi,

[quote user="miked531"]I'm using nrf tag v1.0.0[/quote]

When testing with this tag, I see the same behavior. This is due to a bug in the send/sendto() functions in bsdlib, which was fixed in v0.4.1:

https://github.com/NordicPlayground/nrfxlib/blob/master/bsdlib/CHANGELOG.rst#bsdlib-041

Could you try this version (or newer) to see if this improves the scenario?

Kind regards,

Håkon

RE: nrf9160 blocking sendto() call for UDP

miked531 — Thu, 31 Oct 2019 13:49:55 GMT

I'm using nrf tag v1.0.0 along with whatever 'west update' checked out of the other repos. It's the ibasis SIM, and modem firmware v1.0.1 on the nrf9160 DK.

In my test I am using the IP+port of my server in Amazon, but I changed the values before posting. I am specifically trying to dump a bunch of datagrams that won't get received by anyone. It's UDP, so it really shouldn't matter if there is a server there to receive it or not.

If it helps, I consistently get the ENOMEM after about 16 cycles.

RE: nrf9160 blocking sendto() call for UDP

Håkon Alseth — Thu, 31 Oct 2019 09:21:30 GMT

Hi,

I tried your sample, and wasn't able to verify the behavior that you are seeing. What commit/tag of "nrf" are you using?

[quote user=""]In my test I didn't have a server running to receive the datagrams, if it matters. [/quote]

Have you tried this with sending to a specific server? NTP is udp-based, so you can connect to any ntp-server (default port 123) and see if you get the same behavior there.

Kind regards,

Håkon