• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 78 subscribers
  • Views 72 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430FR5043: 13 HZ Peaks in 3.3V power rail

Christian Paetz
Prodigy 70 points
Part Number: MSP430FR5043

Tool/software:

Hello, I have a custom design with MSP430FR5043 as shown in the schematics. I disconnected all I/Os going to LEDs, Buzzers, etc. I measure the power consumption with the OTII device and I get very strange peaks of 500 uA  with 13 peaks per second while the power consumption for the rest is reasonable 10...15 uA. is there anything wrong with the power supply or does the strange 13 HZ signal on the 3.3V rail ring a bell? 

Some more info:

- I see the very same result when keeping the MSP in reset state ( /RST -> LOW and when using  the recommended firmware below

int main(void) {

WDTCTL = WDTPW | WDTHOLD;

P1DIR = 0xFF; P2DIR = 0xFF; P3DIR = 0xFF;

P1OUT = 0x00; P2OUT = 0x00; P3OUT = 0x00;

__bis_SR_register(LPM3_bits | GIE);

__no_operation();

return 0; }

- I did not connect the two transducers yet but shot cutting there inputs does not change the result.

Thank you for any hint. I am pretty much out of options.

Christian

  • 0
    TI__Genius 10270 points

    Hi Christian,

    If you still see these peaks when holding the device in reset, I am wondering if there is some external factor here. Holding the device in reset should stop the device from executing code and should therefor result in constant current consumption. 

    It also looks like you go into a low power mode without running any code, and with no interrupts to wake the device up. So it further appears that the spikes are due to some other factor. The MCU should not be having these 500 uA current spikes regularly.

    You could try removing more functionality (go straight into a no-operation loop with no peripherals enabled or pin assignments) to see if that changes anything, but currently I do not see what could be causing this. Even if the MCU was running I am not sure what would cause a 13Hz signal like that.

  • 0 in reply to Dylan OBrien
    Prodigy 70 points

    thanks this. reduces my search area further thanks!

**Attention** This is a public forum