CC3200 what does SimpleLinkAppGeneralEventHandler ?

Hi Rafael,

The General events are generally used by NWP to notify the state of the system and most of the events are not Fatal.
The application shouldn't loop forever in the event handler.

Regards,
Ankur

Hi,

thank your for fast responde,

but my application it is loop forever when this routine called.

This is routine provided by TI and I have not changed anything.

//*****************************************************************************
//
//! \brief This function handles General Events
//!
//! \param[in]     pDevEvent - Pointer to General Event Info
//!
//! \return None
//!
//*****************************************************************************
void SimpleLinkAppGeneralEventHandler(SlDeviceEvent_t *pDevEvent)
{
    if(!pDevEvent)
    {
        return;
    }
    switch(pDevEvent->Event)
    {
        case SL_DEVICE_ABORT_ERROR_EVENT:
        {
          //
          // Most of the general errors are not FATAL are are to be handled
          // appropriately by the application
          //
          UART_PRINT("[GENERAL EVENT] - ID=[%d] Sender=[%d]\n\r",
                     pDevEvent->EventData.deviceEvent.status,
                     pDevEvent->EventData.deviceEvent.sender);

          PRCMSOCReset();
        }
        break;

        case SL_DEVICE_FATAL_ERROR_EVENT:
        {
          //
          // Most of the general errors are not FATAL are are to be handled
          // appropriately by the application
          //
          UART_PRINT("[GENERAL EVENT] - ID=[%d] Sender=[%d]\n\r",
                     pDevEvent->EventData.deviceEvent.status,
                     pDevEvent->EventData.deviceEvent.sender);
        }
        break;
    }
}

Eternally "SL_DEVICE_ABORT_ERROR_EVENT" event is generated.

Hi Rafael,

Which application you are referring to here?

Regards,
Ankur

Hi Ankur,

my application is basead in "Provisioning Smart Config".

The routine provided by TI ( SimpleLinkAppGeneralEventHandler ) not handle the event, only reports.

How handle this event? Especially the event "SL_DEVICE_ABORT_ERROR_EVENT" ?

thanks

Hi Ankur,

I would like to revive this discussion. You state that "most of the events are not Fatal" but if we look at the naming of the events being SL_DEVICE_FATAL_ERROR_EVENT and SL_DEVICE_ABORT_ERROR_EVENT the words "FATAL" and "ABORT" makes the state of affairs very clear.

I also get these events on an irregular basis with both r3.2 and r4.1 LaunchPads, running essentially the same application. I have tried to trace the cause back into driver.c but there it comes to a halt.

No information is provided on the possible causes behind these events and in the 1 case the sample code simply does a SOC reset.

Can we please have some clear and specific information with respect to the causes, seriousness and recommended actions to recover.

Thanks

Andre

Hi Andre,

remembering that "PRCMSOCReset ()" instruction was implemented by me, because for in the original Texas code there is no treatment for this ERROR.

That was the only way I managed to solve this error.

Thanks

Rafael