Hi Olav, Thanks for posting, and I hope that we can guide you through some tests to quickly find the root cause of your issue. You have already provided some very useful information that the crystal stops (I am assuming that the crystal is what was driving the timer that wakes the part? ) I have some questions that will help to narrow down the issue: 1. Is the issue very reproducible? 2. Does pulling the RST line low reset the part and cause it to start running again, or do you have to fully power-cycle the part before it will start running again? 3. Can you get it to fail with the debugger connected, so that you can then pause it and see where in the code it is? Alternately, try connect to running target: processors.wiki.ti.com/.../MSP430_-_Connecting_to_a_running_target to see where the code it is when the issue occurs? 4. Could PMM27 be relevant? See www.ti.com/.../slaz627 - it would have to be on a Rev. A device. 5. Another thing that can cause issues is if noise on the TEST + RST line can cause the part to erroneously enter JTAG/SBW/BSL mode instead of main application mode, causing no code to run. Do you have long traces/wires/etc on these lines, or something that could produce noise on these lines in your system? This can typically be dealt with by placing a 4.7k pulldown resistor on the TEST line. 6. Does your timer code ever violate the note in the user's guide www.ti.com/.../slau367 section 19.2.1 about Modifying the Timer registers "TI recommends stopping the timer before modifying its operation (with exception of the interrupt enable, interrupt flag, and TACLR) to avoid errant operating conditions". However, I suspect if that was the case the crystal might still be running, just that your timer might get hung up - still a good best practice to check for. Regards, Katie
↧