RE: disconnect with reason BLE_HCI_CONNECTION_TIMEOUT after battery ADC

Martin — Sat, 10 May 2014 06:42:24 GMT

Hi, I am also concerned if this issue will be a problem when moving from iphone to android implementation. What I read is that there is some differences in how iOS and android implements BLE, but should today be no problem in android 4.x.

First I was woundering what the functions called in ADC irq handler was doing, not a good practice to do lengthy jobs in irq handler, better set a flag or value and execute in main loop or put sched event i this case with Nordic sdk code.

But couldn't this be the issue with calling BLE stack sd_ functions from a higher priority level? The function battery_start (with sd calls) is called from the radio_notify_evt which in prio high. Search for Hard falt, or does this high level restriction just apply certain sd (softdevice) function calls??

My understanding of calling ble stack/soft device with a higher priority is that it can be busy and doesn't allow any higer level "user land" code override and alter the ble internal state, therefor it catch it as hard falt cause it can be "unsafe"?

RE: disconnect with reason BLE_HCI_CONNECTION_TIMEOUT after battery ADC

Anthony Ambuehl — Mon, 07 Apr 2014 16:55:38 GMT

Is anyone at nordic looking into this issue? It has been 5 days with no response.