MSP430F6720A: LPM3 debugging

The problem will be within whatever way they have for exiting LPM3. Which will be an interrupt. Assuming one was correctly set up and interrupts enabled.

A debugger is of course very handy.

Hi David,
so can the debugger be connected to the MSP430 when it is in LPM3?

Regard, Holger

Debugger can connect to the MSP430 in LPM3. Not very clear about the issues your customer facing with. It is normal that the code will stopped running when the device entry LPM3 until it wakeup from LPM3.

so he can connect the debugger to device which is stuck in LPM3 without reset. So you would go onto the target file and press right mouse button "Launch Selected Configuration" to be connected to the device, right? Can he read out the CPU registers then?

I don't get the question. You connect your JTAG or Spy by wire widget to the target, download code, then start execution. Then you can stop it at any time and poke around.

But you still don't need a debugger to think about why the particular conditions your code requires for LPM exit aren't happening.

Hi David,
customer has a faulty customer return. This device is stucked and can only get alive with a reset or POR. He thinks that it couldn't get up out of LPM3. He wants to read out the registers in this situation. This stucked device/case is rarely producible and he don't want to reset it. I assume the XT1 crystal stopped so it would be interesting to read the XT1LFOFFG bit.

Regards, Holger