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

Profile Clock using CCSv4

Steve Ratzlaff
Prodigy 40 points

Hi,

I have been trying to determine the time between two functions using CCSv4.

I have been working with a Spectrum Digital eZDSP board. I have been running from Flash, using TMS320F28355, and using the DSPBios. I have disabled the breakpoints for CIO and end of program halt.

When I try and use the profile clock (with no breakpoints enabled) I get this error message: "C28xx: Can't Run Target CPU: Error 0x00000020/-1042 Error during: Execution, Contention for target processor analysis resources. "

It seems like that may be because I do not have enough breakpoints? I have only been able to set one hardware breakpoint at a time.

So I guess my primary question is: how can I determine the time between two instructions? Preferebly time in seconds, but number of cycles would be fine too. If there is another way of doing this besides using the profile clock, then that would be satisfactory.

A secondary question is: is there a way  to get more hardware breakpoints? Even if there is another way to do the primary question, I would like to know if there is a way to get more breakpoints. It would make some debugging a little easier. A coworker said that in CCSv3.3 he was able to get 2 hardware breakpoints, but in v4 only 1.

 

Thank you

 

  • 0
    TI__Guru**** 463291 points

    Hi Steve,

    I don't believe that just enabling the profile clock would use a breakpoint resource. I see that error message more often when something else is using the clock or other required module needed by the profile clock, such as some emulation analysis tool plug-in or counter used by the application.

    Regarding the one breakpoint being available, is your application auto-running to main on program load/flash? If so, a breakpoint might be used for that.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    Ki,

    I have been using CCSv3.3 as well to see the differences.  I am able to use two h/w breakpoints with 3.3. If I enable the profile clock then I can only use one hw breakpoint. So I do believe that the profile clock uses a breakpoint in some way. 

    A colleague of mine has also been in contact with tech support about the issue of 1 hw breakpoint with 4.0 and 2 in 3.3. The tech support (I believe it was Aarti) said  that this was expected, and that 3.3 has 2 hw bp until the BIOS ROV window is opened then it is limited to 1 hw bp for the rest of the debug session. With 4.0 the hw bp is used throughout the debug session. 

     

    Ki-Soo Lee said:

    Regarding the one breakpoint being available, is your application auto-running to main on program load/flash? If so, a breakpoint might be used for that.

    I did disable this and I continued to only have access to 1 breakpoint.

     

    It seems like 4.0 limits access to breakpoints where 3.3 gives a little more access. I seem to be able to make due with the functionalitiy that 3.3 gives. It still is cumbersome, and at some point it would be nice if 4.0 had the functionality to utilize two h/w breakpoints.

     

    Thank you for your reply.

     

    -Steve

  • 0 in reply to Steve Ratzlaff
    TI__Guru**** 173310 points

    Steve,

    There is a way to disable the breakpoint used by default by CCS v4 in BIOS applications. This can be done by disabling "RTDX" from the BIOS app.

    The attached slide shows how to disable RTDX. First change the HST link type to "NONE", then uncheck the "Enable RTDX" box. This should restore usage of that breakpoint.

    disable-RTDX.ppt