• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 40 subscribers
  • Views 798 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.

CCS/CC3220SF-LAUNCHXL: cc3220sf: access point, event handler question

Dave Warner26
Intellectual 605 points
Part Number: CC3220SF-LAUNCHXL

Tool/software: Code Composer Studio

I am running the CC3220 in Access Point mode with an external application (android device) sending/receiving data to/from it (the android app is written by a third party I am not 100% of all the functionality behind it).

For the most part, everything runs ok and the data is passed around without any issues.
I sometimes get the following event from the SimpleLinkSockEventHandler:

"[SimpleLinkSockEventHandler ERROR]: Close socket (5) operation failed to transmit all queued packets."

I'm not sure what is causing this issue (on my end, I am not closing any sockets - I believe the android app might be doing that).
After this error occurs, communication with the CC3220 device gets flaky and un-reliable.

Any info on this would be greatly appreciated - thanks!!

  • 0
    TI__Mastermind 30780 points
    Hi Dave,

    It does seem the socket is not being closed cleanly.
    What application for the CC3220 are you using when testing this? And what is the android app?

    Thanks,
    Ben M
  • 0 in reply to Benjamin Moore
    Intellectual 605 points

    Ben:

    I am running a custom build of firmware here - the android app is custom as well.

    We are in conversations with the developers regarding how they are handling sockets - the issue might be on their end, currently trying to get to the bottom of it.

  • 0 in reply to Dave Warner26
    TI__Mastermind 30780 points
    Hi Dave,

    Thanks for the update. Please let us know what feedback you get from the developers of the mobile app.

    Another additional question, when you say "After this error occurs, communication with the CC3220 device gets flaky and un-reliable." do you mean that the CC3220 SW application continues to use the same socket with unreliable communication or is a new connection to the app established and that communication is seen to be unreliable?

    Thanks,
    Ben M
  • 0 in reply to Benjamin Moore
    Intellectual 605 points

    Ben:

    As it turns out, the android application didn't process the last reply the CC3220 sent to it and it flagged the message with an error and tried closing the socket twice (same socket number) - that in turn caused the error to pop up on our end.

    He corrected the issue and everything seems to be ok.

    As of now, this issue has been resolved.

    As for the flaky connection, after the error occurred, I wasn't able to connect to the CC3220 with a different source - I had to re-boot the CC3220.

  • 0 in reply to Dave Warner26
    TI__Mastermind 30780 points
    Hi Dave,

    I'm glad you have it working now. Thank you for confirming that the issue is resolved. Feel free to open up a new thread for any other questions you have.

    Best Regards,
    Ben M