• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 2509 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.

Error Message while setting second breakpoint - "Trouble Setting Breakpoint with the Action "Halt Target" at 0x31c1f9: Error 0x00000008/-2048 Error during: Break Point, Unable to set hardware watchpoint 1 at 0x0031C1F9. Watchpoint 1 is alre

Ashutosh Jha
Prodigy 30 points

I am using C28xx processor, Code Composer Studio 3.3 with XDS510 Emulator. When I setbreakpoint at one location, enable the profile clock with auto reset option and run to the breakpoint I observe the following error message while trying to set new breakpoints

"Trouble Setting Breakpoint with the Action "Halt Target" at 0x31c1f9: Error 0x00000008/-2048 Error during: Break Point,  Unable to set hardware watchpoint 1 at 0x0031C1F9. Watchpoint 1 is already in use. Some hardware breakpoints may be used by analysis."

I am running the code from Flash and understand that in this environment I can use maximum 2 hardware breakpoints. So, before trying to set the 2nd and 3rd breakpoint I am deleting the first breakpoint and disabling the Profile -> Clock setup. It looks like even after disabling the Profile -> Clock setup, all the resources reserved for clock are not released leading to above error message.

I want to know how to check and explicitly release the resources reserved for Profile -> Clock.

Any help in this regard is appreciated.

Thanks in advance.

 

Regards

Ashutosh

  • 0
    TI__Guru**** 173310 points

    Ashutosh Jha said:

    I am running the code from Flash and understand that in this environment I can use maximum 2 hardware breakpoints. So, before trying to set the 2nd and 3rd breakpoint I am deleting the first breakpoint and disabling the Profile -> Clock setup. It looks like even after disabling the Profile -> Clock setup, all the resources reserved for clock are not released leading to above error message.

    You are correct that in Flash you are limited to 2 hardware breakpoints. I tried setting a breakpoint and enabling Profile clock as you described and it appears that in CCS 3.3, the breakpoint used by profile clock is not being released even if the clock is disabled. I tried the same scenario in CCSv5.1 and it does release it and allows setting breakpoints as expected. I suspect there was a bug in CCS 3.3 which was later fixed. Unfortunately, if you have to stay with CCS 3.3, I don't think there is a good workaround to release the breakpoint used by the profile clock other than restarting the debug session.

    Also, just an FYI, the debugger usually takes up breakpoint resources for "end of program" breakpoint and "cio" breakpoint. When working in Flash it is advisable to turn these off to maximize the number of available breakpoints for the user. These can be turned off from the menu Option->Customize->Program/Project CIO

     

  • 0 in reply to AartiG
    Prodigy 30 points

    Aarti,

    Thank you for responding to my post.

    Your response is helpful in ascertaining that  the problem exists in Code Composer Studio Ver:3.3. Unfortuantely, I cannot swith to higher version of Code Composer at this stage. As you have mentioned that a good workaround to release the breakpoint used by the profile clock is to restart the debug session, do you mean restarting the target by selecting the menu DEBUG - > Restart?

    Are you aware of any patch installing which may resolve this problem in Code Composer Studio Ver:3.3?

    Regards

    Ashutosh

     

     

  • 0 in reply to Ashutosh Jha
    TI__Guru**** 173310 points

    Ashutosh Jha said:
    As you have mentioned that a good workaround to release the breakpoint used by the profile clock is to restart the debug session, do you mean restarting the target by selecting the menu DEBUG - > Restart?

    Actually I think you may need to restart CCS itself, as I could not get it released with simply a disconnect/reconnect or Debug->Restart.

    Sorry unfortunately I don't think there is a patch for CCS 3.3 that resolves it.