SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

RE: SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

Egidijus — Fri, 25 Jan 2019 06:53:48 GMT

Thank you. After disabling logger and setting #if 1 in port_cmsis_systick.c i get result I was looking for.

RE: SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

flip-flop — Thu, 24 Jan 2019 21:59:26 GMT

devzone.nordicsemi.com/.../port_5F00_cmsis_5F00_systick.txt

Here =)

RE: SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

Egidijus — Thu, 24 Jan 2019 21:23:21 GMT

Hi flip,

Can you share your modifications in port_cmsis_systick.c file? High current consumption is blocking me for using freertos in my application too.

RE: SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

flip-flop — Thu, 24 Jan 2019 12:40:45 GMT

Yup yup. I was comparing two different things but still, I made it!

SDK 15.2 + SD 132 + freeRTOS with ble_app_hrs_freertos example + change in the SDK\external\freertos\portable\CMSIS\port_cmsis_systick.c file => 1.5uA in sleep. That's what I was looking for =) Thank you.

RE: SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

Susheel Nuguru — Tue, 22 Jan 2019 07:56:56 GMT

Hi flip,

I think you are comparing two different things.

If you want to see the power overhead of FreeRTOS, then you should compare power consumption of two examples which are ble_app_hrs_freertos and ble_app_hrs (without freertos)

I think the average current overhead of running the FreeRTOS kernel itself is a bit more than 100uA. The kernel needs to do the bookkeeping and that needs a lot of CPU time. If you are using tickless configuration, then increasing the advertising interval would definitely bring down sole FreeRTOS current overhead too.

What I am saying is do the comparision between these two examples by increasing the radio parameters. I do not think iBeacon example without FreeRTOS is a fair comparision to do with ble_app_hrs_freertos

RE: SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

flip-flop — Mon, 21 Jan 2019 10:58:14 GMT

Hi Susheel.

First of all, thank you very much for your reply.

Comment/uncomment the code snippet definitely have a huge impact on power consumption. In my case: commented snippet: power consumption: 1mA. Uncommented: 7.5mA. This is power consumption on ble_app_hrs_freertos example (The GATT is disabled in the main, peer manager is there).

But 1mA is still very far from 1.6uA. I'm referencing to the iBeacon example. For example, if I set adv. interval to 2 seconds, I measure between-advertisement-current 1.6uA. So it seems like the SD is inactive when there's no need for it. The same case with simple freeRTOS application without BLE. FreeRTOS goes to 1.6uA sleep when there's no task to execute. So I do not understand why BLE and freeRTOS combined do not work. Do I need to maybe use app_scheaduler for BLE events or peer_manager? I'm feeling like I'm missing something...

Any thoughts?

RE: SDK15.2 + SD 132 + freeRTOS = huge power consumtpion

Susheel Nuguru — Mon, 21 Jan 2019 08:04:52 GMT

Hi flip,

I think there is some anamoly with sd_app_evt_wait using MWU peripheral (unconfirmed)

If you see the link here, I have added the #if 0 to comment out sd_app_evt_wait as I have seen some board use a lot of power using it. But later few customers said that commenting out sd_app_evt_wait results in increased power. So if on your board, sd_app_evt_wait consumes less power, then comment out the '#if 0' part in port_cmsis_systick.c file.