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.

CCSv5: feature request: register field values by name

Other Parts Discussed in Thread: OMAP3530

As a Lauterbach user trying to move to CCS, one of the missing features is the very descriptive view of OMAP-specific registers in Lauterbach.  For example, when viewing a register bitfield, Lauterbach shows you the value of the register with a string, not only the hex value.

For example, consider the POWERSTATEST field of the PM_PWSTCTRL_MPU register (under MPU_PRM in CCSv5).   In CCS, you see the register value (e.g. 0x3) where as in Lauterbach you would see the string "On".  If you right click on the value, it would list all the options for the field: e.g. On, Inactive, Retention, Off.   And double-clicking on the value would cycle through the options (or toggle the value for single-bit fields.)

Being a kernel hacker, and not a UI developer, I'm assuming this is more of an eclipse feature than a CCS specific feature, but it is an extremely helpful tool, and voids having to have the TRM open along side the debugger for many case.

 

 

  • This is supported in CCS. I don't have an A8 board available at the moment, but here's a screenshot from a register view on a C674 part. When you are viewing the registers, if you click on the the "+" next to the register name, it expands to show you the bitfield view. If you hover over a field, it will give more info. Also, if you want to change the field, click on the value and if the field has an enumerated set or list of values will be available to choose from with nice descriptive names.

  • OK, nice to know it should work.  At lest this isn't available for the OMAP3 registers in the CCSv5 version I'm working with.

     

  • Kevin, 

    Which board/configuration are you using? I created an OMAP3530 configuration and I have many registers groups for various peripherals. CCSv5 does not have drop down selection for configuring individual bitfields with meaningful names (e.g. Enable/disable drop down). However, it does have description on all registers and bitfields. see screen capture below(I have A8 selected in debug view and I maximized register view to show more information)

     

    Martin

     

     

  • MartinS said:

    Which board/configuration are you using? I created an OMAP3530 configuration and I have many registers groups for various peripherals. CCSv5 does not have drop down selection for configuring individual bitfields with meaningful names (e.g. Enable/disable drop down). However, it does have description on all registers and bitfields. see screen capture below(I have A8 selected in debug view and I maximized register view to show more information)

    I am using omap3530/Beagle.

    I also see the description of all registers and bitfields, but what I am looking for is the configuring of individual bitfields with meaningful names.

    This seems to exist in the version Mark Grosen was using, is this available only in the windows version, or only available in CCSv4?

    Kevin

     

  • Kevin Hilman said:

    This seems to exist in the version Mark Grosen was using, is this available only in the windows version, or only available in CCSv4?

    Kev

    Sorry - I messed up. I mistakenly fired up CCS4.2 instead of CCS5 (hey - it was late on Friday :). I do see that the descriptions have moved into a column instead of hover-help, so the descriptions are there, but like Martin said, there is not support for the "directed" entry of  individual bitfields like in CCS4.2. Hopefully, that's coming soon, Martin? My guess is that this is one of the drawbacks of moving to "stock" Eclipse in CCS5 - CDT does not have as good a register view as the TI version does in 4.2.

    Mark

  • You are correct Mark. In 4.2 we had our own custom register window that had these features. In v5 we are using stock eclipse's register view that does not have these features. It is something that we will be looking to contribute and enable. 

     

    Martin

     

  • Thanks.  Nice to know that it's already on the list of desired features.