• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 189 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

BOOSTXL-CC3135: Need of slNet Library

SN
Intellectual 255 points
Part Number: BOOSTXL-CC3135
Other Parts Discussed in Thread: CC3135

Hi,

I am using STM32 interfaced with CC3135 through SPI with FreeRTOS. I intend to use MQTT in our application. Taking the following links as reference, I have ported the MQTT libraries to FreeRTOS and also have replaced the SlNetSock APIs in the libraries with sl_APIs:

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/997613/cc3135mod-mqtt-example-doesn-t-work-with-ported-sdk-to-stm32-with-freertos/3687158#3687158

https://e2e.ti.com/support/wireless-connectivity/wifi/f/wi-fi-forum/858993/boostxl-cc3135-port-of-cc3135-driver-and-middlewares-with-stm32l4-with-hal-drivers-using-freertos?tisearch=e2e-sitesearch&keymatch=port%25252525252520freertos%25252525252520mqtt%25252525252520cc3135#

I want to understand the purpose of the slNet libraries. Do I need them for my project after all these changes? None of the MQTT client source files use these slNet libraries per se but all the examples with Wifi initialize the slNetSock layer using the slNetIf. Does it have to do anything with the network stack?

Plz advise.

Thanks

SN

  • 0
    TI__Guru 63006 points

    slNet is a layer on top of the network stack that enables you to work seamlessly on top of different SimpleLink IP devices (currently it means that you can easily port from the wi-fi to using Ethernet e.g. of MSP432E - or use both interfaces together). 

    It is less important if you are only interested with wi-fi.

    One feature that is relevant for wi-fi only is the slnetconn (which is part of the SlNet component), that simplifies the maintenance of wi-fi level connection including the handling of provisioning (TI and/or external provisioning) - see Connection Manager example for details.

    br,

    Kobi

  • 0 in reply to Kobi Leibovitch
    Intellectual 255 points

    Hi Kobi,

    Thanks for the reply. I am interested only in Wi-fi along with MQTT at the moment so as you said slNet may not be necessary.

    I went through the Connection Manager example. It looks like an alternative way of handling the NWP. I have reasonable amount of experience with using the host driver sl_ APIs for the NWP.

    Do I have to migrate to the slnetconn method or can I continue with the host driver sl APIs itself?

    Are there any advantages of using the slnetconn? I have not seen a connection manager example in any of the previous SDKs, so I am curious to know.

    Please do let me know.

    Thanks

    SN

  • 0 in reply to SN
    TI__Guru 63006 points

    slnetconn is new and in a wi-fi only case it mainly simplifies the integration of provisioning (if you have plans to add an external provisioning - this can be very helpful).

    The use of slnetconn is optional (it is mainly recommended for new designs).

    If you don't use slNet you will need to port the mqtt example to use the sl_ API.