MSP430FR2433: Very long term LPM 4.5

Hi U-SK,

What application need to stay in LPM4.5 for such a long time?

Regards,
Ling

It seems to me that this steps beyond the technical into product/deployment concerns. I would be somewhat nervous about deploying something for years with no means of knowing whether it's still operable. I'd want it to at least wake up occasionally to self-check.

Some specifics that come to mind:

1) If you're running off a battery, the battery will probably discharge itself in that time. (And if you're not using a battery, the need for LPM4.5 is less compelling.)
2) The WDT and RTC don't operate in LPM4.5 (SLAU445G sec 1.4.3.1 states it the other way around, but the effect is the same). You could use an external WDT and/or RTC, but that also negates the value of LPM4.5.

I wonder if there's a different way of accomplishing your goal?

Hi Ling,

What application need to stay in LPM4.5 for such a long time?

→It's IoT sensor.

   There is a possibility that the sensor need to wait 2 to 3 years until the user operates it

What kind of things should I be careful to keep operating continuously with LPM 4.5 for 2 to 3 years?

Is it possible?

Regards,

U-SK

Hi Bruce, Ling,

Unless user wakes Device up, MSP430FR2433 is need to keep following states .
・GPIO output
・Low power as less as possible
・Device can wake up gpio outside signal anytime

I can not predict when a user wakes the device.
I'm going to stay device in LPM4.5 to reduce supply current as less as possible and all clock is not used.
I think the device can't do self check because WDT can't functional in LPM4.5.

So, I have a question.
How long Can LPM4.5 keep GPIO's output and being able to wake from the outside?

Regards,

U-SK

Hi,

Do you have any updates about my question?

Regards,

U-SK