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.

Memory Browser not working in CCS v5.3

Other Parts Discussed in Thread: TMS320F28034, MSP430F2619

Hi,

I installed CCS v5.3 on Ubuntu Linux and installed the plugins into my existing Eclipse v3.8.2 installation.  The problem is that when I try to bring up the memory browser and enter a memory address, it just shows a blank memory tab.  I also tried upgrading to CCS v5.5, but the memory browser still does not seem to work.  The problem is not restricted to a particular processor either, I get the same behavior on MSP430F2619 and TMS320F28034.

With CCS v5.2 the memory browser works just fine.  The memory browser works just fine while debugging IA32 Linux applications.  Also, CCS v5.3 on Windows without installing plugins into an existing eclipse installation does not seem to have this problem.

Any ideas what could be wrong?

  • I am not entirely sure what could be different about installing CCS 5.3-5.5 over an existing Eclipse installation compared to 5.2, but this wiki page may be of some help: http://processors.wiki.ti.com/index.php/Installing_CCS_over_Eclipse

    I haven't heard of such problems with the full installation of CCS either (ie without installing it as a plugin to existing Eclipse installation) so perhaps you could do the full install of CCS 5.5 on Ubuntu as another option. I am sorry I don't have a better answer at the moment.

  • CCSv5.5 full release includes Eclipse 3.8.1 and CDT 8.1.1, where both must exist in your eclipse that you are trying to install CCS into. In theory 3.8.2 and 8.1.2 (which is what you are using I believe) should be compatible as they are supposed to contain only fixes, but we did have a case in the past where an eclipse service release broke CCS expression view. 

    When CCS is installed into an existing eclipse install, there are some behaviour differences. We are less agressive in tailoring eclipse to CCS user expectations. It is possible that memory browser is configured to use stock rendering and that is causing issues. You would need to open memory browser and open view menu (little triangle pointing down) and check if "Default Rendering" is set to "Memory Rendering". If this does not work, then there might be some errors in error log (yourworkspacedirectory\.metadata\.log ). It might help to see if there is anything there that provides a clue. 

    martin

  • I'm actually using Eclipse 3.8.2 with CDT 8.2.1 (not CDT 8.1.x).  Do you know of any updates in CDT 8.2.1 that could affect the memory browser with CCSv5.3?

    What version of Eclipse and CDT is CCSv5.3 based on?  Is it the same as CCSv5.5?  I can redo the install using the same Eclipse and CDT versions as CCSv5.3.  If that doesn't work, I'll try going to CCSv5.5.

  • Unfortunately, I don't know if we did or did not have issues. We have not really tried that combination. 

    5.3 is based on eclipse 3.8.0 and CDT 8.1.0 (i.e. RTM Juno release from end of June 2012). 

    Martin

  • I went reinstalled Eclipse 3.8.2 and CDT 8.1.2 with CCSv5.3, and the memory browser is working now.

    I guess CCS doesn't work well with CDT 8.2.x.