We noticed issues regarding BLE activities when running our custom bootloader. It seems that we have located the cause but would like to have approval for that behavior.
We observed that advertisements were only send once every 16 seconds and connections were hard to establish and when established instable before our fix. While debugging we found out, that all these problems are not happening when we don't have a bootloader address set in the UICR NRFFW[0] register. We start the LFRC Clock in the bootloader as well as RTC0 with interrupt but forgot to stop and uninit both of them, which we now fixed with these lines:
nrfx_rtc_disable(&rtc0);
nrfx_rtc_uninit(&rtc0);
nrfx_clock_disable();
nrfx_clock_uninit();
It may be caused by a pending RTC interrupt (which we could not find out in the application) or by the reconfiguration of a running LFRC clock. Now it works fine, but since we could not track that bug to its direct cause. I would just like to ask if letting the RTC and LFRC running when exiting the bootloader would cause such a behavior.
