3 years ago.
Tickers crash/hang on the nRF51822, especially when multiple Tickers & a Softdevice are used.
This is a bit of a cross-post from an issue on the github page but I'm hoping it may reach a wider audience and/or someone with some insight.
The github link is here: https://github.com/mbedmicro/mbed/issues/1533
When using Tickers on the nRF51 platform it seems things get missed or interrupts generated can collide just perfectly so as to effectively crash all the application-level interrupts and cause the app to "freeze" whilst any Softdevice running underneath continues happily onwards (but having nothing to send from the application).
Is anyone else experiencing this problem? Anyone found a quick & dirty way to fix?
How about using the nRF51822-SDK app_timer API directly? I know changes to the mbed Ticker function aimed at fixing older, worse versions of this bug replaced using the app_timer with using the directly-controller RTC1 timer on the nRF51822 but this seems to have just shrunk the problem so it's unlikely rather than really solved...
3 years ago.
I think I hit this bug too, and is weird because it looks like it never goes back to the main, the i2c becomes crazy and the aplication freezes. But the bluetooth part keeps working.
My problem seems to happen after a 30 minutes, sometimes more.
I have an i2c with mpu6050, 3 interrupt driven buttons.
I have no idea what causes this, however I try to avoid it using only one ticker.
To post an answer, please log in.