• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1663 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.

RTOS/LAUNCHXL-CC1310: Energy consumption too high

Pedro Henrique Fonseca
Intellectual 410 points
Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310

Tool/software: TI-RTOS

Hello there,

I have a routine with a clock every 10 seconds that run 2 tasks (TX and RX) in my CC1310. It also uses the adc module. The clock module use two semaphores to control the tasks, so they only run one time every 10 seconds. I used an external battery with 220mW/h capacity and the it only took 2:15 hours to deplete it, indicating a consumption of 26mA. I thought that if both tasks waited for the semaphores, TI-RTOS would enter sleep mode to lower this consumption since I have Task.enableIdleTask = true, butit seems it hasn't. I'd like to know if there is anything tht I have to do to make this owrk properly, or how to force the system to enter sleep or standby mode.

Thank you.
Pedro

  • 0
    TI__Expert 6540 points
    Hi, yes you are correct, between the tasks the system should enter Standby.
    Is this a custom design, or are you using one of TI boards?
    Are you able to do a power trace measurement to see what the consumption is for the various stages?
  • 0 in reply to FredG
    Intellectual 410 points
    Hello Fred,
    I am using CC1310 Launchpad. I can try to do a trace power measurement, but I don't know how. Is it possible to do it with just the CC1310 LAUNCHPAD and CCS? If so, can you tell me how.
    Thanks for the promptly response.

    Pedro
  • 0 in reply to FredG
    Intellectual 410 points

    Update:

    When setting up the UIA config to enable task load analysis (so I can see the idle task load) I got these errors:

    Don't know how to solve it. Any help would be appreciated.

    Thanks,

    Pedro

  • 0 in reply to FredG
    Intellectual 410 points

    Another update:

    I could see in ROV that the Idle task is running:

    So I'd like to know if you have any suggestions to what may be causing this high consumption.

    I am using the EasyLink API in the radio, maybe that's the problem (since I don't see the radio getting shutdown after EasyLink_transmit() or EasyLink_receive())??

    Also in ROV it says my clock instance (which I created dinamically) is uninitialized or corrupted, even though it works fine during execution:



    Any help will be appreciated.

    Pedro

  • 0 in reply to Pedro Henrique Fonseca
    TI__Expert 6540 points
    Hi Pedro. No, you would need external equipment such as a power analyser or similar to do a power trace measurement .
    Did you remove the jumpers on the board (LEDs, emulator)? Note that the external flash on this board will consume aprox. 8-10uA.
  • 0 in reply to FredG
    Intellectual 410 points
    8 - 10 uA is not a problem right now, since I have a much larger consumption overall (26mA). Unless it was a typo and you mean 8 - 10 mA, then it would be a problem.

    any clues for software implementations to reduce this? It still doesn't seem right...

    thx,
    Pedro
  • 0 in reply to FredG
    Intellectual 410 points
    Sorry I forgot to answer, but yes, I removed all the jumpers from the XDS emulator and changed the source jumper to external power. I did not remove the jumpers from the LEDs, but I am not using them, I just set them to zero in my init_fxn() and never used them again.
  • 0 in reply to Pedro Henrique Fonseca
    Intellectual 410 points
    FredG,

    I figured it out. Instead of sending a packet to synchronize the clocks (I have 2 boards that must be synched) every 12 hours, I was sending every 10 secs. Since I am using LRM and 14dBm power setup I should expect a very large energy consumption. Now I have my settings done right, so it should be able to last at least until tomorrow.
    Thank you for your promptly responses.

    Pedro