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

CCSv5.1 M5 ARM CodeSourcery Linux Tools Not Working

meg
Intellectual 300 points
Other Parts Discussed in Thread: AM3517

I was using CCSv5.0 and was able to get the CodeSourcery tools to build a project.

Problems with GDB caused me to upgrade to CCSv5.1 M5.

Now the build no longer works.

Is this supported?

My target is AM3517 Experimenter...

 

  • 0
    TI__Genius 15580 points

    hi, 

    How did you obtain CCSv5? Was it a standalone release or was it part of a larger SDK that had other content. Some AM devices include a much larger software distribution which CCS is part of. That version of CCS is customized to include some additional content to help with development of linux apps. 

    In general the answer to your question is yes, but resolving the issue might change depending on which type of CCS you have installed. Standard 5.1 releases that are available on 5.1 download site are customized to facilitate DSP/microcontroller development, thus some functionality is disabled to simplify the GUI. 

     

    Martin

     

  • 0 in reply to MartinS
    Intellectual 300 points

    I downloaded CCS 5.1.05000 from

    http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5#Downloads

    so I guess it would be called a stand alone release?

    Yes - compared to what I was using (CCS 5.0.1.00026) it's menu options appeared much more limited.

    The CCS 5.0.1.00026 version is what was recommended on TI's site for the AM3517 target. However, I had problems getting GNU debug to work and saw a forum post saying that the CCS 5.1.05000 version had fixes with regard to GNU remote debugging.

    So currently I am stuck, one version has issues with GDB but appears to build the target, another version supposedly has fixes for GDB but has problems building the target...

    Host Ubuntu 10.04 With CCS

    Target Linux on LogicPD AM3517 Experimenter

     

     

  • 0 in reply to meg
    TI__Genius 15580 points

    5.1 is customized, but that functionality is just disabled it is not gone. You can enable most of the functionality in M5 by going to Window->Preferences and then go into General : Capabilities, then enable check boxes for 

    C/C++ Perspective

    CDT GDB Debugging

    RSE Project

    I would suggest that you use C/C++ Perspective rather than CCS Edit perspective. Window->Open Perspective (if is not in the short list then click on "Other"), then choose "C/C++". 

    One thing to note that your version of CCS 5.0.x may have included a GNU ARM Plugin. This plugin provided compiler specific options/switches in project properties when using Code Sourcery compilers. This plugin can be installed separately, unfortunately, there seems to be a bug where this plugin does not seem to work well with CCS v5.1. I was not able to start new C or C++ Project wizard with this plugin installed. You should be able to use regular GNU projects support, you just will not see an GUI options for adding code sourcery specific compiler options. 

     

    Martin

     

  • 0 in reply to MartinS
    Intellectual 300 points

    Martin -

    I have no Window-Preferences/General/Capabilities item so can't select anything.

    My version is 5.1.0.201105121800

    On the older CCS 5.0.x version, I did not initially have the GNU ARM Plugin installed and saw it mentioned in the forums so I installed it. In the end, not sure if that was required to get a project to build. I manually set the PATH to the CodeSourcery/bin and got it to work.

    Right now with the 5.1 version when I look at Project/Properties/C C++ Build/Settings I see 

    Orphaned configuration. No base extension cfg exists for org.eclipse.cdt.cross.arm.gnu.sourcery.linux.elf.debug.80347001

    and the Tool Settings tab is empty.

    Questions

    1) Is the goal with 5.1 and ARM to use C/C++ and Debug perspectives and projects in lieu of CCS C++ and CCS Debug projects and perspectives?

    2) As a trial I installed CCS 5.1 in a separate directory than CCS 5.0 so I could go back and forth. Did not uninstall 5.0. Will this create problems? The 5.0 still operates as it did prior to the 5.1 install.
    3) Is it possible to GNU Arm Debug over a serial port in lieu of an Ethernet port with CCS?
    Thanks!
  • 0 in reply to meg
    TI__Genius 15580 points

    You should have the way of adjusting capabilities see picture below. 

     

    Regarding your project: unfortunately, it looks like your project was created using that GNU ARM eclipse plugin, which does not seem to work for me in CCSv5.1 (at least I can't create new projects when that plugin is installed). The "no base extension for..." provided the necessary information.  org.eclipse.cdt.cross.arm.gnu... is the internal plugin name for GNU ARM Eclipse plugin. You do not have it installed in 5.1 hence the error message. 

     

    Questions:

    1) The answer is somewhat dependent on your application space. When using open source compilers/debuggers such as GNU compilers, GDB, etc, then answer is yes. CCS projects only work with TI produced compilers. The way to create a CCS project is by using a dedicated "CCS Project" wizard which has a different set of wizard pages, then what you used to create a code sourcery enabled project. 

    2) There should be no problems with this, main thing to keep in mind is to use a different directory to store your workspace. Workspace is the default location for projects, but it also used as a main storage area for plugin data (e.g. user options, layout, etc). 

    3) yes, but unfortunately I have never done this. Just poking around the menu's, I think you will need to create a new "C/C++ Attach to Application" launch configuration, and choose gdbserver as "debugger" under "Debugger" tab of your newly created launch configuration. You should then have the option to choose TCPIP or Serial connection to gdbserver. For some background information (seems to be v5.0 specific and for ethernet, in 5.1 options are a bit different) see this link:

    http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5

    martin