• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 482 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.

TM4C123BH6ZRB: Current consumpation of each modules

yihe
Guru 66160 points
Part Number: TM4C123BH6ZRB

Hello Champs

in the data sheet Tab23-40, it has the max 54.9mA for all Perihperals On case.

I am wondering whether there is a max current consumption for each perpherals respecively so that we can estimate the maxium current need for the real application.

We are not using all the peripherals for sure.

Regards

Yihe

  • 0
    TI__Guru**** 191736 points
    Hi Yihe,
    Sorry, we don't have such breakdown at a peripheral granularity. I know some MCUs may provide some utilities like a spreadsheet based estimator that estimates the power consumption of different power domains when they are turned on. But I have not seen one that estimate per peripheral. The power will depend on the operating frequency of the peripherals. Some peripherals are small enough that they become insignificant at this process node. Big chuck of the power will come from the CPU, flash and SRAM memories, I/Os and some big peripherals such as USB, Ethernet and CAN.
  • 0
    Guru 117855 points

    yihe said:
    max current consumption for each peripherals respectively so that we can estimate the maximum current need...

    As Charles states - there is a dependency upon the setting of the System Clock - and sometimes the "intensity of a peripheral module's usage."

    You note "estimate" - yet would not, "Real World Measurement" based upon the client-user's "specific use case" - trump (any) estimation?

    Our firm has - at times - performed such measurements - especially across ARM MCUs of competing vendors.    

    The family of MCUs here - due to the power of the API - easily enables the, "Speed, Ease & Enhancement" of such measurements:

    • All peripheral modules are "effectively OFF" - unless specifically enabled.     (simply done via the API: "SysCtlPeripheralEnable()" )
    • Certain peripheral modules - on an individual TM4C device basis - may be "Powered Down"     (via : "SysCtlPeripheralPowerOff()" ... often confined to modules: CAN, USB, EMAC, LCD)
    • By measuring & recording the current draw - with all peripheral modules "disabled" - a "baseline, MCU's current measure" is obtained.
    • Then - via the selective (yet singular) enabling of those peripherals to be employed - any  "increase in current" reveals the "current consumption" of that specific peripheral.
    • Remember to "disable" that peripheral - prior to enabling another - in this manner "estimation has been replaced (trumped) w/real-world measures."

    As always - such measurements should occur across a multiple boards and/or MCUs - and the resulting "averaged readings" - proves of highest accuracy/confidence.     Insure that operating conditions are held as consistent as possible - across each/every such test.    System Clock frequency, Supply Voltage (even) Temperature - should be monitored & maintained.

    Some peripheral modules enable varied frequency control - these should be tested/measured at the "suspected" frequency of operation.     (although "purists" would prefer measures @  Fmin & Fmax.)