• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 81 subscribers
  • Views 927 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

doubt debug mode

Anand
Intellectual 625 points
Other Parts Discussed in Thread: ENERGYTRACE

Hi,

Can anybody tell how much slower does the controller work in debug mode than the normal mode.

for example a  controller which works 25mhz in normal mode, what will be clock in debugging mode (does it work slower than the actual ? and how much slower)

little help would be appreciated

  • 0
    Guru 14640 points

    Debug mode is the same speed as normal mode. The only thing is being able to realize what your code may be doing - because the MSP430 does not have a "realtime mode" like some of the TI DSP's and the C2000 microcontroller, you will need to hone your "debug skills" a bit. A lot of this comes from just working with the unit under test, and there will probably be some head scratching about why things happen and do not happen.

    Sorry to not be more definitive. Some RTOS's will allow you better insight into what code may or may not be doing, but a lot of debug in the 430 world is using spare I/O to allow you to do timings of things.

  • 0 in reply to Todd Anderson78572
    Intellectual 625 points

    I am not using any rtos.I am having tough time with simple program with LCD works differently in both debugging and normal mode. never understand the reason why ?

  • 0
    Guru 227245 points

    If the debugger doesn’t stop the CPU to update the watch window, the CPU will work with full speed. Of course, when single-stepping, the speed is reduced to (almost) zero. Also, using hardware breakpoints (including conditional breakpoints, as long as supported by the CPU’s EEM) does not slow the processor down. However, using conditional software breakpoints does (by using a conditional hardware breakpoint and manually checking the condition).

  • 0 in reply to Jens-Michael Gross
    Intellectual 625 points

    Thanks Jens for reply,


    I am running it continuous without break points and single stepping. In this case cpu should run in same set clock. 

    correct me if I am wrong.

  • 0 in reply to Anand
    TI__Guru* 79261 points

    Hi Anand,

    This is correct - the CPU will run with the same clock. However, one thing to be aware of that might be different is the wake-up time for the part. When you debug say an F5xx device, and your code goes to LPM3 - when you run it with the debugger connected the part can't truly go into as low of a power mode and might wake up faster than it would when you run the device stand-alone. It is something to be aware of if you are trying to analyze timing in your system (it is also one of the reasons why you shouldn't measure current with the debugger connected and why energyTrace requires you to use Free Run mode when you want to make an absolute power measurement).

    Regards,

    Katie

  • 0 in reply to Anand
    Guru 227245 points

    If running with no breakpoints or memory/register vide updates, the CPU runs at full speed. Having the debugger attached may still prevent some deeper LPMs (reverting them to LPM0) but won’t affect active mode.

**Attention** This is a public forum