8 years, 9 months ago.

Declaring timer causes BLE softdevice stack to lock up on first write from app.

I'm using the ARCH BLE board and have some code that drives an OLED and some LEDs and its working great. I've had the soft device working with it with no problems until my last round of changes where it broke. Whereas before I could write from my test app with no problems now on first write the BLE side locks up and the app reports a connection error.

After working back through my last round of changes I found that it was the declaration of a timer,

Timer LEDtimer;

that was causing all the problems. I'm not even calling any of timer functions its simply the declaration that is enough to cause the soft device to have issues. Could there be a conflict with the timer and soft device?

Be the first to answer this question.