• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 53 subscribers
  • Views 4519 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.

Default variable format is 'natural' - prefer CCS remembered last format setting

PeterO
Intellectual 885 points
Other Parts Discussed in Thread: MSP430F5438

Code Composer version 4.1.3:

It would be great if the debugger remembered the last format selected for each variable name.
In the 'Local' tab the default format is Natural.  This is a pain.  With everytime you load an application to debug, you have to change the variable format [for each variable] from Natural to Decimal or Hex - as required.

Can anyone suggest a solution or workaround?

Peter

  • 0
    TI__Guru**** 173310 points

    Peter,

    This is a known issue and is being tracked in defect # SDSCM00037694. Currently the modified format is preserved for global variables but not locals.

  • 0 in reply to AartiG
    Intellectual 885 points

    Being severity major I'm looking to seeing this item done in the next production release.  Cheers for the reply. 

  • 0 in reply to PeterO
    Intellectual 885 points

    Also on a related topic, the hoover over and display the value seems to work for globals but not the local variables.  Maybe you can sort out both of these are the same time.

  • 0 in reply to PeterO
    TI__Guru**** 173310 points

    Peter,

    The hover over should display values for locals as along as you are within scope of the function that contains that local. I haven't seen or heard of issues with hovering not working. Could you please provide more details?

  • 0 in reply to AartiG
    Intellectual 885 points

    Aarti, keeping in mind hover over only works when a stack or register variable is in scope, there are parts of the code where it works and other parts where it does not work.  Where it works and does not work is consistent for a build of code.  Meaning, if you change the code, recompile and load that's a different build of code.  My application is probably larger then most, using about 110k bytes of flash.  The micro is a MSP430F5438 and Code Composer is version 4.1.3.

    As I'm debugging I'm trying to see when it works and when it does not work.  Will post more when I know more - ie when have done more debugging. Writing a new chunk of code over next few days.  Then after a few days of debugging say mid next week I can more clearly define the problem.

     

  • 0 in reply to PeterO
    Intellectual 885 points

    Pushed the hover over out to a new thread.  see  hover over

    Marked this thread as verified given the raised issue has been given a defect number.

     

     

  • 0 in reply to PeterO
    Intellectual 885 points

    Hi TI, re the item reported at the top of this thread, when is it going to be fixed?  Defect #SDSCM00037694 will fix it?  Been waiting > 3 months for this item to be fixed.

  • 0 in reply to PeterO
    TI__Guru**** 169894 points

    Peter,

    According to the bug report, this implementation will be available in release 4.2.2.

    Regards,

    Rafael

     

  • 0 in reply to desouza
    Intellectual 885 points

    Sure, read that in SDOWP.  When is the version due for release?  Not looking to hold you to a date.

  • 0 in reply to PeterO
    TI__Guru**** 451391 points

    Hello,

    This defect will be fixed in the next v4 update (4.2.2). 4.2.2 release is scheduled for the end of the month.

    Thanks

    ki