Low Power Optimizations
==========================
If the device seems to be drawing too much current for your
application, the following section will guide through the 
most common issues.

.. note::
    Please refer to :ref:`energytrace-users-guide` as well 
    as the `Current Consumption Application Note <https://www.ti.com/lit/swra478>`_  
    for how to setup device for current consumption testing.


*   Check if the debugger is currently detached from the 
    device. If using the XDS110 as debuger make sure to only 
    connect the Ground and Power pins (this can be accomplished 
    with jumper cables).

.. figure:: ../energy-trace/resources/Mod_LP_Config_2.png
   :align: center

   Modular LP EnergyTrace stand-alone Configuration

.. warning::
    Confirm that the device has been power cycled since last
    time it was connected to the debugger.

*   Isolate the |DEVICE| from all peripheral devices (such as
    LEDS, External Flash, etc..) as these leakage currents 
    might be the cause of higher power consumption than expected.
    If using a Launchpad confirm all jumpers are removed.

*   Isolate threads in the application until the thread with 
    high power consumption is found. Once found, start isolating
    which peripherals (UART, I2C, SPI, ADC, Timers) are used
    in the thread and check if one of these could be the source 
    of the issue. If any peripheral is set to start a transfer 
    in blocking mode, the |DEVICE| will not be able to go into 
    standby if the transfer never finished. Ex, if UART is set
    to restart receiving in blocking mode, the device will not
    go into standby until the expected data is received.
