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

RTDX?

zizhong tan
Prodigy 110 points

Other Parts Discussed in Thread: TMS320VC5509A

I want to communicate the  CCS3.3 with LABVIEW, but i when i run a project, it said "Can't enable RTDX as it requires AU1 which is already claimed for profiling or breakpoint(s) ", what should i do to deal with this question?  thank you very much..

  • 0
    TI__Genius 12575 points

    Hi,

    Can you let us know what hardware you are using ? and also CCS 3.3 is no longer supported, is it possible for you to upgrade to CCS5.x ?

    Regards

     Vasanth

  • 0 in reply to Vasantha K
    Prodigy 110 points

    The LabVIEW own a toolkit called debugging_workbench, it seemed that using this toolkit can directly communication with CCS3.3, and i can link with ccs3.3 in my computer. but when i run the RTDX module, it cause a error as side above information. 

    I use a TMS320VC5509A EVM to finish this project. 

    Do you mean i need to update the ccs3.3 to ccs5.x ?   As a result, this will deal with this question? 

    thank you very much? 

    if you have time, i can send the toolkit (debugging_workbench) to you, you can try to use. 

    i hope you can help me . thank you very much....

  • 0
    TI__Guru**** 480451 points

    Hello,

    Note that both CCSv3.3 and RTDX is no longer supported. So there is very little help we can provide on these topics. But here is a hint:

    zizhong tan said:
    "Can't enable RTDX as it requires AU1 which is already claimed for profiling or breakpoint(s) "

    Enabling RTDX will use a hardware resource, the same that the profile clock or an hardware breakpoint would use. There are a limited number of these resources supported on a target. Try looking at your debug session and see if there are some resources you can free up by disabling the clock, HW breakpoints or other related features.

    Thanks

    ki