Could you please provide us the testing log (with timestamp) and steps to reproduce this issue ?
What are the modification you have done in your application?
If transmission fails, power status change can occur. Nothing wrong in it.
I had originally thought the module change to sniff power mode was the cause of the transmission halt. Now I believe the mode change is a symptom of failed transmissions, as you mentioned. Are there Bluetooth statistics or diagnostics available on the module to help determine the cause of dropped communications and the sniff mode event?
1 of 1 people found this helpful
There are few flags defined in the SPP application itself which will be helpful for testing.
Also, you can try printing the buffer statistics (wiced_bt_get_buffer_usage) periodically to monitor it.
Following compilation flags are important for testing:
HCI_TRACE_OVER_TRANSPORT - configures HCI traces to be routed to the WICED HCI interface
WICED_BT_TRACE_ENABLE - enables WICED_BT_TRACEs. You can also modify makefile.mk to build with _debug version of the library.
SEND_DATA_ON_INTERRUPT - if defined, the app will send 1Meg of data on application button push
SEND_DATA_ON_TIMEOUT - if enabled, the app will send 4 bytes every second while session is up
LOOPBACK_DATA - if enabled, the app sends back received data