Other Parts Discussed in Thread: CC3100, CC3200
We have an application that will occasionally bring the CC3100 out of hibernate mode and attempt to manually connect to an Enterprise network using PEAP0_MSCHAPv2 (i.e. we do not use profiles, and SL_CONNECTION_POLICY is invoked with everything turned off). We have noticed that about 15% of the time, we receive the above asynchronous event after the call to sl_WlanConnect(). In the previous release (1.0.0.10.0), this event was called SL_DEVICE_FATAL_ERROR_EVENT, which results in our application resetting the CC3100 and re-trying the connection. The re-try connects successfully almost 100% of the time. Since status of -102 means SL_GENERAL_ERROR_CON_MGMT_STATUS_UNSPECIFIED, it is difficult to know what could cause this. Is there any way to find out what is happening and what we can do to improve this?
Also FYI, in between the attempts to manually connect to the Enterprise network, we also bring the CC3100 out of hibernate mode to transmit a handful of small packets in transceiver mode. Not sure if that makes a difference or not.
