MSPM0L1304: MSPM0 ADC trigger support in STOP2 mode – clarification

so can you provide me any reference code or example code to me for mspm0l104 adc using stop2 mode and lfclk.

C:\ti\mspm0_sdk_2_09_00_01\examples\nortos\LP_MSPM0G3507\driverlib\adc12_simultaneous_trigger_event_stop

And these are the self made demo from my self, but not related to your requirement:

adc12_sequenceManager_C1106.zip

7573.adc12_sequence_DMA_G3507.zip

And, happy new year~

Happy new year to you too.
If i need further help i will tell you.
Regards.

How can i switch between two modes using firmware i am unable to find it can you please Provide me code to switch between stop2 and run0 mode?

Run0 is CPU running code, if CPU run __WFI();, device will enter low power mode that you set in syscfg.

If it's STOP2, device will enter it, when interrupt comes, device wake up back to RUN0, and continue run code until hit next __WFI();

Thank you.

Hello TI Expert Team,

I am working with MSP M0L1304 and currently evaluating power consumption in different low-power modes using SysConfig.

Below is the measured current consumption on my hardware (VDD = 3.3 V):

• Run mode: 2.68 mA

• Standby 0: 0.405 mA

• Stop 0: 0.714 mA

• Stop 1: 0.55 mA

• Stop 2: 0.447 mA

However, according to the datasheet (Section 7.5.2 STOP/STANDBY Modes), the expected current consumption—especially for STOP2 and STANDBY modes—should be in the tens of microamps (µA) range, not hundreds of microamps or milliamps.

Test Code Used

#include "ti_msp_dl_config.h" void delay_seconds(uint32_t seconds) { for (uint32_t s = 0; s < seconds; s++) { for (volatile uint32_t i = 0; i < 3200000; i++); } } int main(void) { SYSCFG_DL_init(); while (1) { delay_seconds(5); // Run mode for first 5 seconds __WFI(); // Enter low-power mode configured in SysConfig } }

Test Behavior

• For the first 5 seconds, the device runs in Run mode.

• After that, it enters the low-power mode configured in SysConfig (Stop0 / Stop1 / Stop2 / Standby).

• Current is measured after entering __WFI().

Issue

The measured current is significantly higher than the datasheet typical values, especially for STOP2 and STANDBY, where the datasheet specifies values around 40–50 µA, but I am observing ~400–700 µA.

Questions / Clarification Needed

1. Are there additional requirements (GPIO state, clock source, SRAM retention, debug settings, regulators, etc.) that must be explicitly configured to reach datasheet-level current?

2. Does SysConfig alone correctly disable all clocks and peripherals for STOP2/Standby, or is manual de-initialization required?

3. Could debug interface (SWD), unused GPIOs, or internal regulators be causing the higher current?

4. Is there a recommended reference example or checklist to achieve datasheet-specified low-power current on MSPM0L1304?

Any guidance on what configurations or steps I am missing would be very helpful.

Thank you for your support.

Best regards,
Harsh Modi
Embedded Firmware Engineer
MSP M0 Series User

Based on test on Launchpad, please remove all jumper on EVM. And test current again.

Harsh Modi said:

Are there additional requirements (GPIO state, clock source, SRAM retention, debug settings, regulators, etc.) that must be explicitly configured to reach datasheet-level current?

WFI in software is enough, but for GPIO, please refer to this document https://www.ti.com/lit/pdf/slaaeo9

Harsh Modi said:

Does SysConfig alone correctly disable all clocks and peripherals for STOP2/Standby, or is manual de-initialization required?

If you don't add any other peripherals in syscfg, there is no need to de-init.

WFI is enough.

Harsh Modi said:

Could debug interface (SWD), unused GPIOs, or internal regulators be causing the higher current?

Can not in debug mode. Leave unused GPIO NC and un-configured.

Harsh Modi said:

Is there a recommended reference example or checklist to achieve datasheet-specified low-power current on MSPM0L1304?

Using Launchpad and remove all jumper, only keep GND and 3V3 to power M0. then monitor the current on 3V3.