• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 186 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.

Bugs in Code composer studio v3.3

anu
Prodigy 225 points

Other Parts Discussed in Thread: TMS320C6727

Respected all

 I am working on Code composer v3.3 in TMS320c6727 processor , i was not able to debug the local variables and it is taking some junk values .could somebody help me to find the patch files of this version

regards

anu

  • 0
    TI__Expert 8055 points

    Anu,

    I suspect this is likely not a problem with CCS.  Did you build your .out file with full symbolic debug on and optimization off?  If not, rebuild with these settings and then try to debug local variables.

    CCS doesn't know the difference between a local and a global variable. It only knows to look for the variable at the address it's told by the compiler.  So, if this is really a bug, I'd expect it to be a compiler bug.  With that said, I don't think this is a compiler bug either, unless you are building with the settings that I mentioned.  It is normal to not be able to view local variables if optimization has been turned on.

    Regards,

    Dan