• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 1548 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.

CCS does not recognize breakpoints, gives GEL_Expression window when trying run-to-line

Pat Harris
Genius 3890 points

Santosh,

I’m fighting breakpoints again, in my application this time. CCS seems to have difficulty determining h/w vs s/w. After repeated attempts / reloads, I can get the proper designation of s/w for ramfuncs routines. Still, the debugger will not hit them. Trying Run to Line – produces the GEL_Expression window but will not stop.

I can see that lower flash is being erased, but then it crashes and I cannot get a stop to determine why.

Any recommendations?

Thanks,

Pat

 

Email reply from Santosh:

Pat,

 

Make sure you have un-selected ‘skip all break points’ in the break point window. When you set a break point CCS should automatically decide whether to use a HW breakpoint or SW break point, you don’t have to worry about it.

 

If you are setting up any break points in RAM (SW break points) then do it after the function/code gets copied to RAM…meaning after RAMFUNCS copy code gets executed from flash. You should be able to use atleast 6 HW break points and unlimited SW breakpoints.

 

Would you be kind and post the questions to forum as well, there might be others who can answer the question better as well or learn from our chat.

 

Best Regards

Santosh

 

I have unselected skip all breakpoints. CCS does not reliably determine h/w vs s/w breakpoints, requiring many attempts, reloads, etc. I haven't figured out the formula to get CCS to behave properly. I have tried this with both the USB XDS100 as well as the XDS560. Both fail.

I am running CCS5.5 with the F28M35x Concerto.

Any help would be greatly appreciated.

Pat

 

  • 0
    TI__Guru**** 429930 points

    Hi Pat,

    Pat Harris said:
    CCS seems to have difficulty determining h/w vs s/w.

    How CCS figures out whether to set a HW or SW breakpoint at a program address is determined by the debugger memory map. If that address is in an address range that specified as read-only in the debugger memory map, CCS will use a HW breakpoint. Otherwise it will use a SW breakpoint. The debugger memory map is configured by the GEL startup file. One thing to check when you see this issue is to see what the current debugger memory map looks like and make sure it is set up correctly.

    Thanks

    ki