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.

MSP430f5529 low power issues

Other Parts Discussed in Thread: MSP430F5529, ENERGYTRACE, MSP-FET, BOOSTXL-CC1120-90, CC1120

Hello All,

Hopefully you can help me out.  I'm going crazy trying to get this to work. Here is the code I've used:

#include <msp430f5529.h>
#include <msp430.h>

void main(void)
{
  WDTCTL = WDTPW | WDTHOLD; // Stop watchdog timer
  UCSCTL6 = XT2OFF;
  _BIS_SR(LPM4_bits); // LPM4 with interrupts enabled
//LPM4;
}

When I measure the current w/usb connected I get ~34mA, when I unplug usb I get ~10mA.
When I configure all the outputs via:
P1DIR = 0xff;
P1OUT = 0x00;
...
P7DIR = 0xff;
P7OUT = 0x00;

I pull 110 mA w usb connected, ~90 mA without usb connected.

I've tried removing all jumpers, except from the 5V and GND jumper and it pulls ~15mA without usb connected.
I'm powering from a benchtop PS @5V going into the 5V pin.
I've also tried running 3.3V into the 3v3 pin, and that gives me slightly lower consumption ~10-12 mA without USB connected.
I've also tried this on another identical board, and I get the same results.


I'm pretty sure I'm missing something with the low power configuration, but I just cant seem to find it.

Thanks,

-Patrick

  • Hi Patrick,

    I tried running the 'MSP430F55xx_LPM4.c' example code on the MSP430F5529 LaunchPad (no USB connected, no jumpers connected), and I saw current consumption (displayed on the bench power supply) shown as less than 1 mA for VCC=3.3V. This code does disable VUSB LDO. Can you describe how you're measuring the current? Are you using a LaunchPad or a custom board?

    Keep in mind that the MSP430 goes to sleep in the LPMx modes, so this results in discontinuous, pulsed currents. These pulses are typically difficult for a multimeter to measure (too slow), as discussed in these two threads.

    The most accurate way to measure the power consumption would be to use the EnergyTrace feature in CCS with the MSP-FET. However, this which would require a target board or custom board to be used, since the MSP-FET can't be used directly with the MSP430F5529 LaunchPad. An alternative (cheaper) approach could be using the MSP432 LaunchPad, since its on-board XDS-110 emulator supports EnergyTrace, as described here.

    /* --COPYRIGHT--,BSD_EX
     * Copyright (c) 2012, Texas Instruments Incorporated
     * All rights reserved.
     *
     * Redistribution and use in source and binary forms, with or without
     * modification, are permitted provided that the following conditions
     * are met:
     *
     * *  Redistributions of source code must retain the above copyright
     *    notice, this list of conditions and the following disclaimer.
     *
     * *  Redistributions in binary form must reproduce the above copyright
     *    notice, this list of conditions and the following disclaimer in the
     *    documentation and/or other materials provided with the distribution.
     *
     * *  Neither the name of Texas Instruments Incorporated nor the names of
     *    its contributors may be used to endorse or promote products derived
     *    from this software without specific prior written permission.
     *
     * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
     * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
     * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
     * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
     * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
     * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
     * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
     * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
     * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
     * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
     * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
     *
     *******************************************************************************
     *
     *                       MSP430 CODE EXAMPLE DISCLAIMER
     *
     * MSP430 code examples are self-contained low-level programs that typically
     * demonstrate a single peripheral function or device feature in a highly
     * concise manner. For this the code may rely on the device's power-on default
     * register values and settings such as the clock configuration and care must
     * be taken when combining code from several examples to avoid potential side
     * effects. Also see www.ti.com/grace for a GUI- and www.ti.com/msp430ware
     * for an API functional library-approach to peripheral configuration.
     *
     * --/COPYRIGHT--*/
    //******************************************************************************
    //   MSP430x552x Demo - Enters LPM4, LFXT1, REF0 disabled,
    //                      VUSB LDO and SLDO disabled, SVS disabled
    //
    //   Description: Configure ports and enter LPM4. Measure current (~1.2uA).
    //   MCLK = SMCLK = default DCO
    //
    //                MSP430F552x
    //             -----------------
    //        /|\ |              XIN|-
    //         |  |                 | 32kHz
    //         ---|RST          XOUT|-
    //            |                 |
    //
    //   F. Chen
    //   Texas Instruments Inc.
    //   December 2012
    //   Built with CCS Version: 5.3.0 and IAR Embedded Workbench Version: 5.51.1
    //******************************************************************************
    
    #include <msp430.h>
    
    int main(void)
    {
      WDTCTL = WDTPW | WDTHOLD;                 // Stop WDT
    
     // Setup UCS
      UCSCTL4 = SELA_1;                       // Ensure VLO is ACLK source
    
      // Port Configuration
      P1OUT = 0x00;P2OUT = 0x00;P3OUT = 0x00;P4OUT = 0x00;P5OUT = 0x00;P6OUT = 0x00;
      P7OUT = 0x00;P8OUT = 0x00;PJOUT = 0x00;
      P1DIR = 0xFF;P2DIR = 0xFF;P3DIR = 0xFF;P4DIR = 0xFF;P5DIR = 0xFF;P6DIR = 0xFF;
      P7DIR = 0xFF;P8DIR = 0xFF;PJDIR = 0xFF;
    
      // Disable VUSB LDO and SLDO
      USBKEYPID   =     0x9628;           // set USB KEYandPID to 0x9628
                                          // access to USB config registers enabled
      USBPWRCTL &= ~(SLDOEN+VUSBEN);      // Disable the VUSB LDO and the SLDO
      USBKEYPID   =    0x9600;            // access to USB config registers disabled
    
      // Disable SVS
      PMMCTL0_H = PMMPW_H;                // PMM Password
      SVSMHCTL &= ~(SVMHE+SVSHE);         // Disable High side SVS
      SVSMLCTL &= ~(SVMLE+SVSLE);         // Disable Low side SVS
    
      __bis_SR_register(LPM4_bits);             // Enter LPM4
      __no_operation();
    
    }

    Regards,

    James

    MSP Customer Applications

  • Hi James,
    FYI. All the steps I did above was without the sigfox module connected.
    I am using the launchpad with BOOSTXL-cc1120-90 sigfox module.
    I am measuring current from the power supply through a fluke dmm.
    I originally left GND, 5V, 3V3 jumpers in place ( as per the sigfox instructions) and that is why I had 10+mA draw.
    Once I removed those jumpers I was able to see current draw go down to less than 15uA.
    However with those jumpers removed, the sigfox module no longer transmits. Should I follow up with sigfox on using the module in low power modes?
    Thanks,
    -Patrick
  • Hi Patrick,

    As discussed in Section 2.3 in the LaunchPad User's Guide, keep in mind the effect that the backchannel UART and any circuitry attached to the F5529 may have on current draw. Also, USB current levels can vary widely, depending on whether the connection is active or suspended, how much bus activity is happening, how long the cable is, and other factors. If you're concerned about the power consumption of the MSP430F5529, I'd recommend isolating it and measuring the current using the instructions in Section 2.3.

    If your jumper and external power supply configurations don't match those given in Section 2.4 in the LaunchPad User's Guide, additional power could be consumed by back-powering the emulation MCU through its I/Os. I'd encourage you to read through these sections carefully.  

    Regarding the BOOSTXL-CC1120-90, I see in the CC1120 datasheet that the lowest current consumption (2 mA) during RX/TX occurs in RX Sniff mode. When powered down, the CC1120 appears to only consume 0.12 uA (see page 1 of datasheet). Keep in mind these values are for the CC1120, not the entire BoosterPack. Depending on what mode the CC1120 is in, 10+ mA total current consumption doesn't seem unreasonable.

    If you have further questions about the CC1120, I'd suggest posting them in our Low Power RF Tools Forum. I've seen some recent discussion about MSP430F5529 + CC1120 that may be helpful.

    Regards,

    James

    MSP Customer Applications

**Attention** This is a public forum