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.

  • TI Thinks Resolved

CC3100MOD: Marcro Clarification VERIFY_NO_ERROR_HANDLING_IN_PROGRESS

Intellectual 980 points

Replies: 1

Views: 23

Part Number: CC3100MOD

Hi Team,

We are working with CC3100MOD and have experienced some problems with the SDK. The SDK has calls from various places that block forever. We need to be able to recover from an error condition and cannot do that when the calls don't return to give an error code. There is also the _SlNonOsMainLoopTask() function that apparently needs to be called in order for the SDK to process callbacks etc. When does this need to be called?

We have seen a variable g_bDeviceRestartIsRequired being set to TRUE sometimes although it is hard to see in the debugger since it is buried within a macro VERIFY_NO_ERROR_HANDLING_IN_PROGRESS. How do we check whether this is set, is there a function that will tell me if this is set? I assume the chip needs a reset at this point? Thanks for your help with this!

Regards,


Garret

  • Hi,

    The SimpleLink a-sync error event handler (SimpleLinkGeneralEventHandler) will be invoked when the g_bDeviceRestartIsRequired gets set.

    Which calls are blocked forever?

    Are you using a non-RTOS solution? only in this case you will need to call _SlNonOsMainLoopTask() from the main loop.

    This call will be used as a context for the simplelink driver event processing. The simplelink requires such an execution context and will definitely get blocked if this function will not be called.

    In the RTOS implementation, the simplelink context is obtained through a dedicated thread (initiated with the VStartSimpleLinkSpawnTask call).

    Br,

    Kobi

     

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.