This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

current consumption issue during sleep mode

Hi,

Using SDK14.0.0, soft device: s132_nrf52_5.0.0

If Segger embedded used them use latest sdk as below, because sdk 14.0.0 has no support for segger embedded.

nRF5_SDK_17.0.2_d674dde\examples\ble_central_and_peripheral\experimental\ble_app_multirole_lesc\pca10040

& replace main file and check.

Other wise you can check it directly by importing it to eclipse IDE. & change sdk root path in make file for compilation.

Multirole_FreeRTOS_Example.7z file of application firmware attached: 

 https://smetgroup-my.sharepoint.com/:u:/g/personal/megha_choudhari_mysmindia_com/ES3k5Cbbg_FPoEH-Y0gWPUUBNVkzrM1cRiS0V5ee20m7Zw?e=kNPcxt

Sleep current Result observed on nRF52832 DK Board 

  1. Scanning ON/OFF every 30 sec . DCDC enable and Disable same sleep current ~ 23 uA  
  2. SW1 and SW2 pin configured as input interrupt pin with No_Pullup configuration Sleep current increase in both cases up to 100uA

 

Sleep current results observed on Device 

  1. If SW1 and SW2 Pin not configured as input interrupt pin : both DCDC Enable and Disable same sleep current observed .

Also, When Sleep mode enable current is 3uA, DCDC mode Disable in central profile sleep current observed 300uA & In Peripheral profile it is 3uA. Why this much of variations getting?

Help to review code.

Regards,

Megha Choudhari

Parents
  • Hi Megha

    I tested your application and the current consumption seems off indeed. I discussed this case with a colleague, and we wouldn't recommend using a FreeRTOS port that's this old (SDK 14) as there are two known bugs in SDK 14 related to FreeRTOS. They're listed here in the SDK 14.x.0 known issues.

    Please note that the fact that it draws the expected amount of current (3uA) in peripheral mode points to this not being a FreeRTOS related issue specifically, as it seems like the RTOS is behaving as expected. I was not able to see how the central is put into sleep mode, can you provide any details on how this is done?

    Best regards,

    Simon

Reply
  • Hi Megha

    I tested your application and the current consumption seems off indeed. I discussed this case with a colleague, and we wouldn't recommend using a FreeRTOS port that's this old (SDK 14) as there are two known bugs in SDK 14 related to FreeRTOS. They're listed here in the SDK 14.x.0 known issues.

    Please note that the fact that it draws the expected amount of current (3uA) in peripheral mode points to this not being a FreeRTOS related issue specifically, as it seems like the RTOS is behaving as expected. I was not able to see how the central is put into sleep mode, can you provide any details on how this is done?

    Best regards,

    Simon

Children
Related