• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 41 subscribers
  • Views 396 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220MOD: Diference between SlNetSock API and Host Driver sockets.

Vadym Mishchuk
Intellectual 305 points
Part Number: CC3220MOD

I am working on providing BSD socket interface for custom HTTP server app. On one hand I have TI implementation from CC3220 SDK (source\ti\net\bsd) on the other hand this repo: https://github.com/bakerstu/cc32xx-bsd-wrapper . I see, that one of them uses socket interface from ti/drivers/net/wifi directory, whereas other uses SlNetSock API from ti/net/. I am wondering what is the difference between those socket API's, because they look quite similar to me. Maybe they have something to do with thread/safety or something? Also I am curios about support of "secure sockets" for those options (because server app should support https security).

  • 0
    Guru 79905 points
    Hi,

    Native interface for CC3220 devices are sl_ API calls in ti/drivers/net/wifi. SlNet API is a wrapper around the sl_ API. Reasons for SlNet API is a code portability between wireless and wired devices (MSP432E4). New TI examples uses SlNet layer. Secured sockets are supported at both layers. In case you are starting new development at CC3220 it may to be better use SlNet layer.

    Jan