• State Answer Suggested
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 977 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430: AutoRun: Target not run as breakpoint could not be set: Could not set device breakpoint

sini sebastian
Prodigy 110 points

while debugging in the debug mode iam getting this error message.

MSP430: AutoRun: Target not run as breakpoint could not be set: Could not set device breakpoint

Iam not able to debugg properly

  • 0
    Intellectual 495 points

    Sini,

    The MSP430, like any other microcontroller,has a limited number of breakpoints. Some of these are used to break at main and other locations. I suggest you disable all your own breakpoints and run it again.

    Please tell us about the debugger you're using (CCS, IAR, CrossWorks, etc) as well as the MSP430 you're using.

    Regards,
    Gustavo

  • 0
    Prodigy 110 points

    iam using CCS.I have tried many times disable the break point and and put it back 

    what iam facing the problem means inside the switch case its not executing the proper staements.debugg point is excuting some wrong statements

  • 0 in reply to sini sebastian
    Intellectual 450 points

    Are you now able to debug correctly and set breakpoints? Not sure what you mean by this

    sini sebastian said:

    what iam facing the problem means inside the switch case its not executing the proper staements.debugg point is excuting some wrong statements

  • 0 in reply to psa
    Guru 227245 points

    psa said:
    Are you now able to debug correctly and set breakpoints? Not sure what you mean by this
    what iam facing the problem means inside the switch case its not executing the proper staements.debugg point is excuting some wrong statements

    [/quote]

    It is possible that due to code optimization the line where the breakpoint shall be set has been moved out of the case block (common subexpresseion elimination) or even has been eliminated totally (e.g. a redundant write or an assignment that isn't use anywhere later).
    In this case, the debugger is unable to locate the code that belongs to a certain code line, or the proper code line for the current execution point, either due to ambiguity or due to no code generated.

    Disable compiler optimization and try again. But be aware that thsi will generate larger and slower code.

**Attention** This is a public forum