I have succesfully installed and licensed CCS 5.2 on my Ubuntu 12.04 laptop.
I have connected a LM3S8962 evaluation board to my laptop, then I started
CC2 5.2 and:
Project -> Import Existing CCS/CCE Eclipse Project.
In the search-directory box, I browsed to StellarisWare/boards/ek-lm3s8962/blinky
but I get the following error:
File connections\Stellaris_ICDI_Connection.xml does not exist. Was included by file /home/user/CodeComposerStudio/workspace_5.2/blinky/target_config.ccxml
Any ideas on how to solve this problem?
Thanks in advance,
We are still working on support for Stellaris in Linux. First of all, aside from that error, did your project import okay? You probably have the red "X" by the target configuration file but otherwise all the files are there, and you should be able to successfully build the project?
The target configuration file has windows style path separators so that is one reason you are getting an error. We are fixing the path separators in the next StellarisWare release. However, that file is not actually present because we do not yet have good support for Stellaris ICDI on linux. We have been able to make it work, but it does not always work on all systems and we have not been able to debug the reason for this yet but it has something to do with USB drivers.
So, I would like to say that if you want to use CCS on Linux with Stellaris boards, we highly recommend that you use an XDS100v2(ARM). This works well:
If you want to try and get the ICDI direct connection working, you are welcome to do that and we will try to help but may not be successful. If you want to do that then you need to create a file with the following contents:
<?xml version="1.0"?><connection id="Stellaris In-Circuit Debug Interface" class="31040"> <connectionType Type="LM_ICDI"/> <property Type="hiddenfield" Value="No" id="dataFileRequired"/></connection>
Name this file "Stellaris_ICDI_Connection.xml"
And place it in the path (relative to where you installed ccs):
In reply to Stellaris Joe:
Thank you for the tip. Following it, I was able to add the "Stellaris In Circuit Interface" as the connection option of my LM4F232 project. However, it still did not work and I had to do some tweaks to get it working. I wrote them here, in case anyone may find them useful.
First of all, although CCS graphical environment kept complaining about target being missing, I noticed some warnings in the text console regarding libftd2xx.so and libusb-1.0.so not being found on the system. libftd2xx.so was indeed not on my system, so I downloaded it from FTDI web page (http://www.ftdichip.com/Drivers/D2XX.htm). I copied the "i386 libftd2xx.so.1.1.12" binary to my /usr/lib folder and then created a symbolic link to it, also in /usr/lib:
sudo ln -s libftd2xx.so.1.1.12 libftd2xx.so
libusb-1.0 was already instaled on my system (Ubuntu 10.04), but is was named as "libusb-1.0.so.0", so I also created a symbolic link to it in /lib:
sudo ln -s libusb-1.0.so.0 libusb-1.0.so
CCS still wasn't working, and now it complained about the target's clock, but again, in the console there were some warning now regarding the permissions of the device file placed in "/dev/bus/usb/...." folder. So I added this to one of the existing udev rule files.
And now, apparently, it works!
In reply to Jose Manuel Cano Garcia:
I can confirm that Jose Manuel's solution works ok in a Ubuntu 11.10 64 bits SO. However, you must use i386 "libftd2xx.so.1.12" instead of 64 bits one, as it doens't work with the later. It's probably due to CCS is a 32 bits program.
In reply to Ignacio Herrero:
I tried Jose's solution while working on a ubuntu 12.04 64bits environment for my Stellaris Evalbot which is based on Lm3S9B92 but It didn't work completely. To make it work in 12.04 64, not only ibftd2xx.so has to be the i386 version, (like Ignacio mentioned above,) but also the file libusb-1.0.so. Although I'm not sure if it helped, I also used the i386 versions of libdbusmenu-gtk.so.4, libdbusmenu-glib.so.4, and libappmenu.so since these files were causing errors as well.
I got all the necessary i386 versions from https://launchpad.net/ubuntu/precise/i386. And used them to replace the 64bit versions existing in /lib/ (for libusb-1.0.so), /usr/lib (for libdbusmenu-gtk.so.4, libdbusmenu-glib.so.4), and /usr/lib/gtk-2.0/2.10.0/menuproxies/ (for libappmenu.so). After that, I was able to load blinky onto the board.
If you do that like I did, then I'd recommend to restore the 64bit files after finishing working with ccs since the i386 versions could break other programs (so far no program has broken though).
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.