• Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 520 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.

Problem with breakpoints with CCSv4 using XDS510LC-USB

Patrick Poulin
Prodigy 230 points


Hello...

I am using a F2809 or F28027 on 2 different products.  

I have CCSv4 (v4.2.5.00005).  First image 001.jpg is my actual Features versions.

I have a XDS510LC -USB (v4.2.3.02) to debug and emulate.

The problem I am experiencing now is the following:  

I start CCSv4, rebuild the project, etc.

I run the debugger, and I can run the code from here, no problem.

I break the code using the pause button, and the code stops.  I set a breakpoint in my code using the "Toggle Breakpoint" option in the dropdown menu, and a grey (like disabled) breakpoint symbol appears.  In the breakpoint window, the line of code where the breakpoint should be set is inserted there, but the checkbox is not marked.  Anyway, when I re-run the code, it stops on this line even if the checkbos is not marked and the breakpoint seems disabled.  

When I try to mark the checkbox, I get the message "Error programming AET Job..."  Anything I do with this, including "Remove all breakpoints" or any other command to remove or set it does not work.  And from now, when I run the code, it stops at the line I added the breakpoint.  To remove it, I have to stop the debugger and start it again (keeping CCSV4 running).  

My previous bug few months ago was that I was unable to set any breakpoint, now I can set some, but they stick forever.  Sometimes they don't stick either, I get the same error.  This is really annoying since I never really succeeded in setting the breakpoints on this product.

Can anyone help please ?

Pat

In the past, I have posted on this problem, it seemed that everything was back working, but soon after, the bug came back.  Can't explain what is causing it.

  • Prodigy 230 points

    As I am currently working on it, I will describe the steps I am following...

    - I deleted ctools.dll

    - I deleted my Workspace

    - I ran CCSv4 - clean (I got plenty of errors while lunching it (see image)

    - I loaded my project into this environment and it looks now that breakpoints are working, but I am running without any ctools.dll and I get a lot of errors at startup.  Can't guarantee right now that this will work like this in the next days.

    Still investigating...

  • TI__Guru**** 473401 points

    Hi Patrick,

    Not sure what is going on but i know that on 28x the number of hardware breakpoints are limited. A hardware breakpoint is an AET resource so you will get an out of AET resource error when you are trying to set a hardware breakpoint when you don't have any resources available. Just double-check that there are no "hidden" breakpoints being used (like at main or the exit point of the application) or any other AET resources are being used (like the profile clock enabled)

    Hope this helps 

    ki

  • in reply to Ki
    Prodigy 230 points

    Thank you Ki

    Already checked that a thousand of times.  For sure there are some invisible breakpoint or stuff taking these ressources being stucked so I can't use them after, but it seems they're impossible to remove without wiping the ctools file out.

    That's mainly the issue with this

    Pat

  • in reply to Patrick Poulin
    TI__Guru**** 473401 points

    I do know that there have been work on improving the robustness of ctools recently. If you have time, could you try out CCSv5.2 and see if your issues are resolved?

    Thanks

    ki