Power Consumption AWS IOT sample nrf9160DK

[Salvo]

Hi everyone, 

i'm writing to ask some advice for my NBIOT AWS application with the nRF9160 DK. 

1.  I'm currently using the aws_iot sample available as a baseline for my project, but i noticed that power consumption are really high using the sample application as it is, also enabling CONFIG_PM=y in prj.conf. Since UART in this example is largely used for debug purposes, is it better to start from a clean AT client sample application to achieve the best possible power performance adding one by one all that i need? Do i have take care of something else?
   
   
2. I red a lot about Power Manager of Zephyr, but i didn't understand how to use it in my application (Zephyr version should be 2.7.99 as printed in LTE  Link Monitor while running). I'm doing this steps for simplification:
   1. Add CONFIG_PM=y at top of prj.conf
   2. Include #include <pm/device.h>
   3. Initiate a task that calls the following function found on another ticket and modified to match my version as described here. 
      

      static void disable_uart0_fn(struct k_work *work)
      {
      	  // Turn off logging (which is using UART0):
        	console = device_get_binding(DT_LABEL(DT_CHOSEN(zephyr_console)));
        	pm_device_state_set(console, PM_DEVICE_STATE_OFF);
      }
      

      
      The result is that i'm not able to build the application because "pm_device_state_set is __deprecated" . Is there any guide to follow that could help me?

Thanks in advance.

Salvo

[Håkon Alseth]

Hi,

 

 I'm currently using the aws_iot sample available as a baseline for my project, but i noticed that power consumption are really high using the sample application as it is, also enabling CONFIG_PM=y in prj.conf. Since UART in this example is largely used for debug purposes, is it better to start from a clean AT client sample application to achieve the best possible power performance adding one by one all that i need? Do i have take care of something else?

If UART is only used for debugging purposes, you can disable serial and redo your current consumption testing.

You want to disable it in all child-images as well as your application.

Create the folder and file my-application/child_image/spm.conf

Try placing "CONFIG_SERIAL=n" in prj.conf and in the above spm.conf.

If you also use MCUBoot, you should create the file child_image/mcuboot.conf with "CONFIG_SERIAL=n" as well.

The result is that i'm not able to build the application because "pm_device_state_set is __deprecated" . Is there any guide to follow that could help me?

The power management API was reworked from zephyr v2.7. You should use the API as indicated in the documentation:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/zephyr/reference/pm/index.html#c.pm_device_state_set

Ie. this function:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/zephyr/reference/pm/index.html#group__subsys__pm__device_1ga3840d6e7832a00b93763247a5951bfde

 

Kind regards,

Håkon