MSP430FR5969 standby current 0.4uA is it possible.

[jimpx225 0]

I have been round and round this this problem has anyone achieved this ?

 

If anyone has achieved 0.4uA  please could you share the code as i can only get in down to 220uA.

 

 

I can get the G2553 down to 60uA but not the FR5969.

 

I am using energia but have CCS setup as well.

 

 

[Fmilburn 446]

Please don't make multiple posts of the same question

[spirilis 1,265]

How/where are you measuring it?  Could there be parasitic losses from the eZFET section at the top of the launchpad skewing your numbers?  Have the eZFET jumper block shunts all been pulled?

[jimpx225 0]

Please don't make multiple posts of the same question

sorry just desperate for an answer .

[jimpx225 0]

How/where are you measuring it?  Could there be parasitic losses from the eZFET section at the top of the launchpad skewing your numbers?  Have the eZFET jumper block shunts all been pulled?

I have two version one home made and a launchpad and both have the same results, The meter is on the VCC line to the MSP.

 

I am thinking there needs to be something extra in the code for a FR5969 as all the usual LPM3 and stopping the watchdog doesn

[spirilis 1,265]

I have two version one home made and a launchpad and both have the same results, The meter is on the VCC line to the MSP.

 

I am thinking there needs to be something extra in the code for a FR5969 as all the usual LPM3 and stopping the watchdog doesn

[tripwire 139]

If anyone has achieved 0.4uA  please could you share the code as i can only get in down to 220uA.

 

I might be able to take a crack at this.  Post your whole sketch and I'll play around a bit.

 

I am using energia but have CCS setup as well.

 

I don't use Energia myself, but I had some trouble getting the datasheet power consumption on FR5969 launchpad.

 

There were two issues that caused excess power consumption in my case:

1. I'd set the unused pins to output low, but the UART TX/RX jumpers were in place on the launchpad. The UART output on the ez-FET sits at VCC when nothing is being sent, so grounding that pin draws a lot of current. Removing the UART jumpers fixed that.
2. I hadn't initialised the LFXT properly. As far as I can remember that results in the DCO being enabled to source ACLK, even in LPM3.

Once I fixed those I was able to achieve the datasheet specifications. I'm not sure how applicable those points are to Energia, though.

[spirilis 1,265]

Definitely remove all the eZFET jumper blocks, though I've mentioned that already...

 

Energia does initialize the LFXT, on MSP430G2 chips with no LFXT that has resulted in folks coming onto the forum and complaining about a 2 second startup time (drawing a lot of current in the process) since it'll wait up to 2 seconds for the LFXT to be stable.  It should be using the LFXT too in LPM3 modes (e.g. Energia's own sleep(), sleepSeconds() functions)

 

edit: If you intend to use the eZFET to power the chip, just connect the GND and 3.3V (Vcc) shunts and nothing else.

[jimpx225 0]

I don't use Energia myself, but I had some trouble getting the datasheet power consumption on FR5969 launchpad.

 

There were two issues that caused excess power consumption in my case:

1. I'd set the unused pins to output low, but the UART TX/RX jumpers were in place on the launchpad. The UART output on the ez-FET sits at VCC when nothing is being sent, so grounding that pin draws a lot of current. Removing the UART jumpers fixed that.
2. I hadn't initialised the LFXT properly. As far as I can remember that results in the DCO being enabled to source ACLK, even in LPM3.

Once I fixed those I was able to achieve the datasheet specifications. I'm not sure how applicable those points are to Energia, though.

thanks for the reply

 

do you have any sample code that works so i can check to see if something else is drawing current.

[jimpx225 0]

thanks for the reply

 

do you have any sample code that works so i can check to see if something else is drawing current.

 

big step forward..

 

i have found this code which i have added in and bingo  0.4ua.

 

what is it doing?

 

  P1OUT = 0;

  P1DIR = 0xFF;

 

  P2OUT = 0;

  P2DIR = 0xFF;

 

  P3OUT = 0;

  P3DIR = 0xFF;

 

  P4OUT = 0;

  P4DIR = 0xFF;

 

  PJOUT = 0;

  PJDIR = 0xFFFF;

 

[tripwire 139]

big step forward..

 

i have found this code which i have added in and bingo  0.4ua.

 

what is it doing?

 

  P1OUT = 0;

  P1DIR = 0xFF;

 

  [...]

 

That's setting all the GPIO ports to output low.