• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 41 subscribers
  • Views 1422 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.

CC3200: Transceiver mode in STA mode

Tobias Schneider1
Prodigy 120 points
Other Parts Discussed in Thread: CC3200

Hi,


we are porting our existing application to the CC3200. The application already contains a TCP/IP stack. The application was working with a wired Ethernet connection before.


Is it possible to let the CC3200 NWP handle the connection to the AP in STA mode, and still let our application use the transceiver mode? This could make it much easier for us to integrate the CC3200 into our application.

Thanks

Tobias

  • 0
    Guru 21435 points
    I cannot confirm, but I suspect you should be able to this. Though I would recommend you seriously look into using the CC3200 TCP/IP stack. If your application/TCP/IP stack was built on standard BSD Sockets, then the work should not be that great to migrate. Migration will ensure performance and allow you simple access to important features like SSL/TLS support. Basically if you are going to use a new platform for your product, then you really should be considering migrating to this new platform fully, especially since the work is unlikely to be that great, and the benefits are significant.

    Glenn.
  • 0 in reply to Glenn Vassallo
    TI__Mastermind 26320 points

    Also, it can help save you previous RAM for application development on M4. 

    Regards,
    Geet

  • 0 in reply to Glenn Vassallo
    Prodigy 120 points
    So, I've just got out a CC3200 LaunchPad and tried it. It does look like being associated to an AP and having a RAW socket is mutually exclusive. I've made the following observations:

    1) You can be in STA mode and create a RAW socket.
    2) You can not associate with an AP if a RAW socket has been created. The call to sl_WlanConnect fails.
    3) You can not create a RAW socket while being associated to an AP. In my case (nonos) the call to sl_Socket just blocks.

    The reasons why we are investigating the option to use our own stack are quite simple: We know its limitations and we can quickly fix bugs if needed.