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

CCS/CC3220SF-LAUNCHXL: Wi-Fi OTA training academy lab: ERROR socket connect, status -708

Benjamin Simpson31
Prodigy 150 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

Tool/software: Code Composer Studio

I'm trying to complete the last part of the Wi-Fi OTA training academy lab and keep getting the above error. I am able to get a -456 too but I think that one is from not having the correct CA file in flash memory before trying to interface with the repository. -708 error code states  <SL_ERROR_BSD_ESEC_SOCKET_ERROR_E (-708L)  /* error state on socket    */> but I'm not positive what this means. I'm attempting to get my dev kit to communicate with a repository on Dropbox as stated in the training academy lab but this error comes up :

The previous tasks have you flash firmware using OTA protocol on a Github server which works fine so I know this procedure works I just can't seem to get the last part to work.

If anyone has any suggestions as to what might be happening please let me know.

Thanks,

-Ben  

  • 0
    TI__Expert 8255 points
    Hi Benjamin,

    Thanks for your question. Please allow some time for us to take a look into this.
  • 0
    Prodigy 150 points

    Having moved on to the 'Wi-Fi Secure Sockets' exercise in the training academy I have elicited the same error code. I've connected two CC3220SF MCU Launchpad platforms together as instructed in the lab setting; one as a server and the other as a client. After issuing the send command for Task 2 I am presented with the below error:

    This lab points you to the CC320 SimpleLink Wi-Fi & IoT Programmers Guide found here to troubleshoot any potential socket errors. Under chapter 7 I found this:
    So at least I'm getting the 'what' part figured out but am still unsure 'why' this is the case. In this example the two MCU's are not connected to the outside inter-webs so the issue has to be some configuration within the code or device itself, I think. 

  • 0 in reply to Benjamin Simpson31
    TI__Expert 8255 points
    Hi Benjamin,

    Can you confirm whether you are using non-blocking sockets? Also which SDK version is being used?