Hello,
customer has one device which stucks in LPM3 and is not coming up again (only with POR or reset). Is there a possibility to connect the JTAG debugger and read out the registers? What possibility to debug this device somehow?
Regards, Holger
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.
Hello,
customer has one device which stucks in LPM3 and is not coming up again (only with POR or reset). Is there a possibility to connect the JTAG debugger and read out the registers? What possibility to debug this device somehow?
Regards, Holger
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
**Attention** This is a public forum