freertos high power consumption in SDK 12.2

[vit bernatik]

Hello, I wanted to updated to SDK 12.2 and I noticed that FreeRtos is consuming 800uA in sleep!!! We do battery powered application and with this power consumption our battery would be dead in 10 days. It is not acceptable for our application. The problem is within update of file: freertos\portable\CMSIS\nrf52\port_cmsis_systick.c. Originally in 12.1 you called sd_app_evt_wait(); and it was working. In 12.2 you call directly __WFE(). So probably something in SoftDevice is not correctly turned off. Unfortunately SoftDevice is not public so I can not fix it for you :(. Can you please help me ASAP? Power consumption is crucial for us. The problem is visible also in your demo: examples\ble_peripheral\ble_app_hrs_freertos\pca10040\s132\arm5_no_packs\ble_app_hrs_freertos_pca10040_s132.uvprojx.

[Susheel Nuguru]

This has been fixed in 13.0.0. If you do not want to migrate to 13.0, then use freertos files from 13.0.0 and copy them to 12.2. You have to copy files from folder sdk/external/freertos

[vit bernatik]

Hello Aryan, thanks for response. I did not know there was 13.0 already out. I looked into source codes and it seems someone try to fix it. But I just tried example sdk13.0_orig\examples\ble_peripheral\ble_app_hrs_freertos\pca10040\s132\arm5_no_packs\ble_app_hrs_freertos_pca10040_s132.uvprojx and it has huge power consumption 7mA. I connected detect pin to turn off led but still 7mA. Can you remeasure and let someone fix the demo? But just now I tried the other option to overwrite freertos folder from 13.0->12.1. After merging FreeRTOSConfig.h I confirm I have expected 2 uA. Thank you!!! :))) But pelase fix your SDK 13.0 free rtos example...

[Vidar Berg]

Hi, all SDK 13.0.0 have logging enabled by default, and current consumption will drop back to normal if you disable it in sdk_config.h. More information here: devzone.nordicsemi.com/.../

[vit bernatik]

Ok thank you for help. I confirm the example is now working (going to sleep where consumes 2uA).

[Dave_couling]

Was this fixed in SDK 12.3?