• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 711 views
  • Users 0 members are here
Support feedback
Options
Options

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: Invalid variable values inside the variable/expression window

Paul Klose
Intellectual 260 points
Other Parts Discussed in Thread: MSP430F5659

Tool/software: Code Composer Studio

Hi,

i am debugging the msp430f5659 with CCS 5.5.

My code is working and compiling without errors. I can also step through the code and see what is happening.

The issue is now, if i stop at a breakpoint and look into the variables via variable/expression window in the debug mode i get results of 0xFF or 0xBE in all variables.

Please see the attached image for more details.

Is that a setting issue in CCS 5.5 or something different.

best regards

Paul

  • 0
    TI__Guru**** 451181 points
    Hi Paul,
    That is really odd. The first request I am going to make is if you can update your CCS version. CCSv5.5 is pretty old and unsupported. If you can move to something more recent (like 8.0), that would be great. After you update to 8, see if the issue is still there.

    If the issue still exists, or if you do not wish to update your CCS version, please provide a reproducible test case. Project + generated *.out file is what I am looking for. It doesn't have to be the original project. It can be a stripped down version that can reproduce the issue.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 260 points

    Hi Ki,

    thanks for your reply. The CCS v8 is working better. I installed it and did an update of the JTAG device for MSP430.

    Now the variable/expression window looks good and i don't have 0xFF or 0xBE values anymore.

    I will test it and hope the issue is fixed.

    best regards

    Paul

  • 0 in reply to Paul Klose
    TI__Guru**** 451181 points
    Thank you for updating and I am happy to hear that the issue (at first glance) appears to have gone away. There has been many stability fixes and enhancements since CCSv5.5, some of this must have addressed this issue.

    ki