• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 42 subscribers
  • Views 271 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.

CC3100: Error (-6) when performing an sl_Stop()

Alan Hamilton
Prodigy 130 points
Part Number: CC3100
Sometimes our devices are receiving error (-6) when performing an sl_Stop(). This only happens a small percentage of the time.
1)  What is the meaning of error (-6) in response to sl_Stop()?
2)  What are the proper recovery actions after receiving the error?
3)  Is there are list or table of these error codes?
Thanks,
Alan
  • 0
    Guru 78485 points

    Hi Alan,

    This error code you find at \simplelink\include\simplelink.h:

    #define SL_RET_CODE_ABORT                  (-6)

    Additional information about error code SL_RET_CODE_ABORT you find at e2e forum.

    As I know recovery procedure should look like:

    1. Call stop again:
      1. wait a moment
      2. call sl_Stop(0)
      3. call sl_Start() again and continue at WiFi operations
    2. If step 1 does not fix a issue preform restart of your host MCU

    BTW ... do you use latest SDK and ServicePack?

    Jan

  • 0 in reply to Jan D
    Prodigy 130 points

    Hi Jan,

    Retrying the sl_Stop() call hangs (never returns).
    The symbol ??? does not exist in our version of the SDK so your information was a big clue. 
    Thanks for that - it confirms that our workaround strategy will likely work.
    Here is the version information. We will need to be extremely careful about updating the SDK in
    production because if it causes an unexpected side effect, a scenario can be created where customer
    units cannot download a fix over-the-air which is bad for obvious reasons.
    /*****************************************************************************/
    /* Macro declarations for Host Driver version                                */
    /*****************************************************************************/
    #define SL_DRIVER_VERSION   "1.0.0.10"
    #define SL_MAJOR_VERSION_NUM    1L
    #define SL_MINOR_VERSION_NUM    0L
    #define SL_VERSION_NUM          0L
    #define SL_SUB_VERSION_NUM      10L
    =========================================
    Regards,
    Alan
  • 0 in reply to Alan Hamilton
    Guru 39650 points

    Hi Alan,

    It seems that you are using SDK version 1.1.0 which is pretty old (10 Mar 2015). If you don't want to use latest SDK version you should to use latest Service Pack version at least. From message above is not clear what version of ServicePack do you use. Service Packs are backward compatible with SDK, even though cross versions testing between SDK and Service Packs version is not made by TI.

    But I agree that all changes (including updating ServicePack) need to be carefully tested at your side. If Host MCU restart is not a issue for you you can use this workaround.

    (I will not be answering at this forum for 14 days due to vacations)

    Jan

  • 0 in reply to Hnz
    Prodigy 130 points

    Hi,

    Thank you for the helpful information. We have developed something that will work until the SDK can be updated.

    Regards,

    Alan