• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 241 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-CC1352P: sleep state of simple_peripheral vs simple_peripheral_oad

Ben Andre
Prodigy 50 points
Part Number: LAUNCHXL-CC1352P


Hardware: LAUNCHXL-CC1352P-2 dev-kit

RF: BLE

CCS:10.0.0.00010

SDK: simplelink_cc13x2_26x2_sdk_4_10_00_78

I inherited a project based on the simple_peripheral example and have been asked to add OAD functionality. I am porting it to the simple_peripheral_oad example. We have noticed that the low power state of the simple_peripheral_oad based application is in the range of 500-600 uA, while the simple_peripheral based application gets down to ~15uA.

As a sanity check, we measured current consumption of unmodified examples running on the same dev-kit (no hardware variability) and see that simple_peripheral is running at ~100uA, while the simple_peripheral_oad example is running at 500uA. Based on forum posts and the data sheet, we think this means that the OAD example is in idle mode, while the non-OAD example is in sleep mode. The POWER_SAVING macro is defined for both projects. I have diffed the syscfg files for the two projects and the primary difference seems to be the NVS external flash and the GPIO outputs for the LEDs. Nothing jumps out at me as blocking sleep mode in the OAD example.

Questions:

  1. Is there any fundamental reason why the OAD example can't get to the same low power state as the non-OAD version?
  2. What modifications do we need to make to the OAD example to enable full sleep?

Thanks,

Ben

  • 0
    TI__Intellectual 2180 points

    Hi Ben,

    I have assigned an expert to comment.

    Regards,
    Michael

  • 0
    TI__Genius 14845 points

    Hi Ben,

    Thanks for providing a nice background to your questions and apologies for the delay.

    1. I don't see a reason why the same low-power state can't be used for both the OAD and the non-OAD projects.

    2. My initial thought would be that no modifications should be necessary in order to make the OAD projects go into sleep mode. 

    I'm going away on vacation but I will assign a team member to follow up on your issue. 

    Thanks, 
    Elin