Possible Ticker BLE_API conflict causing problems with Nordic devices? about ble HOT 7 OPEN

ARM Internal Ref: IOTSFW-2794

from ble.

@seajayshore Tickers are not used anymore by implementation of BLE API on Nordic platforms.
Your ticker issue is more likely related to an overflow in the ticker code.
Investigations are still going on.

from ble.

@pan- Thanks v. much for the update! :-)

Ah, OK, I see. There is a Timeout used in nRF5xGap.h in the ble-nrf51822 library I thought was getting called, but I seem to have been wrong.

So if I drive all interrupts / periodic updates to my app via the radioNotificationCallback in Gap.h, and remove my application-level Ticker, I should avoid this Ticker issue altogether right? (Unless another Ticker is being used by some other library obviously).

from ble.

@seajayshore The radio notification callback is a terrible way to drive anything (it should be removed at some point ...). The best would be to wait for a patch and still use the Ticker.

from ble.

OK, thanks for the straight-up advice! I'll follow! :-)

Maybe I'll have to look at using the Nordic app_timer of some lower level API using the RTC1 timer.

from ble.

any activity done through radio notification callbacks can potentially delay the radio from doing timing sensitive operations. Radio notification callback handler should be very brief.

from ble.

OK, thanks for the tip. It's only setting a single flag variable in the callback context so should be ok I guess.
In anycase my application is working much more reliably having removed the normal ticker & using the radiocallback flag. Issue from my point of view is I now have no/limited control over frequency of this callback as its determined by the connection interval from the central.

from ble.