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.

OMAP-L138: Power consumption of a timer

Part Number: OMAP-L138

Hi,

I've been using the OMAP-L138 power consumption spreadsheet provided here 'processors.wiki.ti.com/.../OMAP-L138_Power_Consumption_Summary have a question about the power consumption of the Timer modules.

Timers 0 and 1 are driven from PLL0_AUXCLK which is OSCIN lets say 24MHz.

Timers 2 and 3 are driven from PLL0_SYSCLK2 or PLL1_SYSCLK2 which will typically have a much higher frequency.

The spreadsheet says for the Timer 0/1 frequency fields 'Program this field with the timer frequency in MHz (max value of 12MHz).'. What is this frequency? Is it the module frequency (in that case limiting to 12MHz seems odd) or the timer period as a frequency or something else?

If the spreadsheet is configured for 'Typical - 456MHz' using the button at the bottom and then I set Timer 0 to have a frequency of 1MHz the spreadsheet says the timer takes 8.2mW that seems a lot considering there is no I/O and it is just counting up. It's more than a SPI device running at 27MHz, 100% utilisation. Is there a bug in the spreadsheet or does the timer really take this much power? Also entering anything below 12MHz results in the same power consumption of 8.2mW, when you enter 12MHz it jumps to 12.4mW.

Thanks

Nigel

  • Hi Nigel


    >>The spreadsheet says for the Timer 0/1 frequency fields 'Program this field with the timer frequency in MHz (max value of 12MHz).'. What is this frequency? Is it the module frequency (in that case limiting to 12MHz seems odd) or the timer period as a frequency or something else?

    It is essentially the output frequency or the frequency at which can have the timer input pin to toggle every cycle. The tests were instrumented to give an upper bound of maximum activity power, so we did with assuming period set to 0 , and max clock frequency where pin is toggling every cycle. The module clock frequency is somewhat baked in the cvdd power already , once you put an output frequency in the frequency field.


    >>If the spreadsheet is configured for 'Typical - 456MHz' using the button at the bottom and then I set Timer 0 to have a frequency of 1MHz the spreadsheet says the timer takes 8.2mW that seems a lot considering there is no I/O and it is just counting up. It's more than a SPI device running at 27MHz, 100% utilisation. Is there a bug in the spreadsheet or does the timer really take this much power? Also entering anything below 12MHz results in the same power consumption of 8.2mW, when you enter 12MHz it jumps to 12.4mW.

    Again think of this as as the worst case when timers are enabled in a potentially artificially high activity test - once the timer is doing something meaningful , it consumes ~ 8 mW and if you bump of the frequency some more it does increase by some extent , but that is mostly core logic driving data externally etc, so the increment is a bit non linear.

    Is there a certain power goal you are trying to get to with this device and not meeting it or is this just some initial assessment on device power looking at the "estimation" tool?

    Regards
    Mukul
  • Hi Mukul,

    Thanks for the quick reply.

    This is for some initial assessment to estimate power consumption and therefore battery life. We will need the timers to provide system ticks to the DSP and ARM cores (possibly different millisecond rates) and also a system wide time counter. All of these will be internally clocked from the PLL and not drive any output pins. Can we assume that the power consumption for this configuration of timers will be significantly less than the spreadsheet implies? Is there a way to get a better estimate other than configuring a real device as we want it and then trying to measure it? 

    Regards

    Nigel

  • Hi Nigel

    Thanks for clarifying the background behind your queries

    >>Can we assume that the power consumption for this configuration of timers will be significantly less than the spreadsheet implies? Is there a way to get a better estimate other than configuring a real device as we want it and then trying to measure it? 

    I dont know if it will be "significantly" lower , but you could potentially assume 50% of what you see based on your inputs to the spreadsheet . Do note that this is not a generic statement for every module/row in the power estimation tool - but I know with timer we were trying to show some upper bounds. 

    Additionally the power estimation tool models the leakage for the worst case process - there is "some" variance between  nominal/typical process vs hot process over high temp (not as much as some of our newer process node devices in 28.m) - hope you are aware of that , because some customers prefer using typical/nominal power for battery life estimation. However we do not provide any nominal/typical data for these devices. 

    Feel free to share your use-case spreadsheet for us to see if there are any other areas for power optimization. 

    The device family is popular in  portable/land mobile radio space so we have seen customer use it successfully for battery life applications similar to that. 

    If you are looking at deep sleep mode, please do be careful - as the wake up from deep sleep is from RTC wake up *OR* deep sleep pin , and these are mutually exclusive. I have seen customers trip on this before and assume both will work interchangeably etc.

    Regards

    Mukul