RE: Achieving low power consumption for BLE advertising

Vidar Berg — Mon, 21 Jun 2021 07:50:14 GMT

Thank you for the update. Yes, that explains it, LFSYNT will force the high frequency oscillator to be always on.

RE: Achieving low power consumption for BLE advertising

Cookiejar — Mon, 21 Jun 2021 01:54:15 GMT

Thank you for your quick response and support - the issue was an incorrectly set clock source - using LFSYNT instead of LFRC. We are now getting 1.5uA between advertising events.

RE: Achieving low power consumption for BLE advertising

Vidar Berg — Fri, 18 Jun 2021 12:57:45 GMT

Hello,

1. The power profiler estimates include the LF clock source pluss RTC0 used internally by the Softdevice, but not RTC1 used by the app timer. However, the run current for an RTC instance is typically only around 0.1 uA so it doesn't explain why you measure 250 uA on average.

2. No, it shouldn't be neccesary. The Softdevice will run advertising in the background at the interval you have specified in the application before you called "advertising start"

3. The measurements results should have been close to the estimates given by the online power profiler. Are you using the Nordic power profiler kit for measurement? It would be interesting to know if the floor current between advertising and timer events match the typical sleep current given in the product spec: Sleep.

Would you be able share the code you are using for this test? Maybe I will be able to see what the problem is then.

Best regards,

Vidar