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.

Minor Issue with MSP430 Debug Clock Control

Other Parts Discussed in Thread: MSP430F5438A

This is a pretty minor issue in my mind, but still one that can probably trip some people up (it tripped me up for a bit).

When you go to the debug options, then click the "Target" tab, expand "MSP430 Properties," and then click on "Clock Control," there is an option to stop "Timer_A" and "Timer_B."  I'm using the MSP430F5438A, which has two Timer A's (A0 and A1) and one Timer B (B0).  Checking the option to disable Timer B appears to disable the second Timer A (A1) and not Timer B.  Don't check the option to disable Timer B, and A1 simply continues to run during debugging.

As I said, it's not a huge issue, but it might trip some people up.  I don't know if there is some way to change the debug options GUI depending on what MSP430 is being targeted to allow for options to disable each of those three timers.  At the very least, checking "Timer_B" should probably disable Timer B0 instead of Timer A1. ;-)

I'm using CCS version 4.1.2.00027.

EDIT: I guess I should mention that I was using ACLK (itself running from REFO) to run all three timers.  My debug options were also set to "stop Auxiliary Clock (ACLK) on emulation halt,"  so I don't know if that is another bug or not.  Maybe my understanding is wrong, but that sounds like if ACLK gets stopped, then the Timers running on ACLK should also be stopped, regardless of if their individual enable/disable options are marked.