You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@pan-@rgrover : It is easy to simply return BLE_ERROR_UNSPECIFIED when a call to ble_init() fails. However, this might not be the ideal solution. The main problem is that we do not have sufficient error codes to be more specific about the cause of the problem. Is it acceptable to return BLE_ERROR_UNSPECIFIED when there is a failed call to ble_init()? Should we are more error codes to ble/blecommon.h in BLE API?
See this at: https://github.com/ARMmbed/ble-nrf51822/blob/master/source/nRF5xn.cpp#L94 .
The init process should check and report if something has gone wrong
The text was updated successfully, but these errors were encountered: