Which API to use, socket or nrf_socket?

[kt1024]

Hi,

I just tried to use the following code on the nrf9160DK with zephyr version 0.3.0:

 errVal =setsockopt(at_socket_fd, NRF_SOL_SOCKET, NRF_SO_RCVTIMEO, (const char*)&sock_timeout, sizeof(sock_timeout));
    if (errVal != 0L)
    {
        printk("Error: %d\n",errVal);
        return -EFAULT;
    }

While setsockopt exists SO_RCVTIMEO doesn't, NRF_SO_RCVTIMEO however does exist but doesn't work with sockets, i.e. errVal is -1.

So the question is does it make sense to use socket, or should I rather use nrf_setsockopt()?

Regards,

KT

[Jared]

Hi,

Sorry for the late response.

They're basically the same. You should use setsockopt(), which is translated over to nrf_setsocketopt in nrf91_sockets.c.

Best regards

Jared 

[kt1024]

I already tried using NRF_SO_RCVTIMEO with setsockopt it appearently doesn't work. I don't have any need for this right now, so I'll not try again.

Regards,

KT