• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 4836 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.

DSS/GEL - Stopping at SW breakpoints (source code file, line number)

Joshua Lawes
Intellectual 650 points
Other Parts Discussed in Thread: CODECOMPOSER, MSP430F249

Hello,

I have created a software breakpoint to a specific line of source code and printed out its properties (see below) however there doesn't appear to be any reference to the relevant program address (for other breakpoint types I would compare this with the value of the program counter as per examples).  Therefore, is there any way to tell (using DSS/GEL) that I have actually reached the correct breakpoint?

|=================================================================================================================
| TYPE:  Software
| ID:    16
|-----------------------------------------------------------------------------------------------------------------
| PROPERTY                                                          VALUE                ALLOWED VALUES                
| --------                                                          -----                --------------                
| Hardware Configuration.Location                                   C:/CodeComposer/Software/MyModule/mySource.c, line 36                               
| Debugger Response.Condition                                                                                          
| Debugger Response.Skip Count                                      0x0                                                
| Debugger Response.Skip Count.Current Count                        0x0                                                
| Debugger Response.Action                                          Remain Halted        Update View, Refresh All Windows, Control Profiling, Execute Expression (GEL), Enable a Group, Disable a Group, Read Data from File, Write Data to File, Remain Halted
| Miscellaneous.Group                                               Default Group        Default Group                 
| Miscellaneous.Name                                                                                                   
|=================================================================================================================

Thanks,

--

Joshua

  • 0
    TI__Guru*** 130875 points

    Hi Joshua,

    let me look into this for you and see if/what options you have available.

    Have all your other breakpoints been to a known address?  Ie address or symbol?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 650 points

    Hi Lisa,

    Thanks very much for your assistance; much appreciated.

    Yes, previously all of my breakpoints have been to known addresses (usually extracted from the symbol itself).

    Cheers,

    --

    Joshua

  • 0 in reply to Joshua Lawes
    Intellectual 650 points

    By the way, just for more information, the reason that I am using this method rather than just taking the actual program address directly from the Disassembly view is that otherwise I receive the error "Insufficient resources" (I think the number of HW breakpoints is rather limited on my target, the MSP430F249).

     

  • 0 in reply to Joshua Lawes
    TI__Guru*** 130875 points

    Hi Joshua,

    sorry again for the time here but I have a lot to learn myself.

    From what I can tell when you do a printProperties it only prints out items as that that were specifically set.   Unfortunate but I don't believe in your case there is a work around.

    All the best,

    Lisa