jsolarski 94 Posted October 9, 2012 Share Posted October 9, 2012 1.) What are my options for Linux (preferably source files) tool chain? I am looking for stellaris compatible, with the possibility of being able to compile for other arm chips in the future. 2.) What are my options to program the stellaris launchpad with linux? I have Tried googling, browsing TI's website, and other wiki's and am unable to find reliable info. FYI I do not have a windows box Quote Link to post Share on other sites
Guest Stellarisiti Posted October 9, 2012 Share Posted October 9, 2012 1.) What are my options for Linux (preferably source files) tool chain? I am looking for stellaris compatible, with the possibility of being able to compile for other arm chips in the future. 2.) What are my options to program the stellaris launchpad with linux? I have Tried googling, browsing TI's website, and other wiki's and am unable to find reliable info. FYI I do not have a windows box For CCS, check this post by Rick. You also can use code sourcery and eclipse as a tool chain. There is some setup involved. You may not be able to use the ICDI debugger on eclipse as its still being worked on, but third party debuggers like openocd and jlink work great. Quote Link to post Share on other sites
jsolarski 94 Posted October 9, 2012 Author Share Posted October 9, 2012 I am trying to stay away from CCS and eclipse, I know they work great for project management but all I really need the tool chain, and a programmer for the stellaris launchpad.......(debugger is not critical but is a plus). I am looking for the minimalist install....... CCS looks like it would work on most distros and could be promising , but I probably have a lot of work to get it working since I am using BLFS, if I have no other option then CCS I will try to get it to work. Quote Link to post Share on other sites
Rickta59 589 Posted October 9, 2012 Share Posted October 9, 2012 At this point there isn't a programmer. We are waiting on the openocd project to use the info TI provided them and create an interface to the TI ICDI device. The only option that works on linux now is to follow the steps outlined in the post mentioned above. Quote Link to post Share on other sites
xpg 127 Posted October 9, 2012 Share Posted October 9, 2012 I'm planning on using GCC (build using https://github.com/jsnyder/arm-eabi-toolchain) and OpenOCD with an Olimex JTAG. It seems that the StellarisWare software provides make-files that are gcc-compatible and should be usable as a template for new projects. Debugging directly with GDB is not quite as straight forward as using Eclipse but I've gotten used to it on different occasions :-) Quote Link to post Share on other sites
jsolarski 94 Posted October 10, 2012 Author Share Posted October 10, 2012 I will look forward to the openOCD, as for the CCS, I have to recompile ld-linux.so.2 libasound.so.2 libatk-1.0.so.0 libcairo.so.2 libc.so.6 (version 2.3.2 or higher) libdbus-1.so.3 libdbus-glib-1.so.2 libdl.so.2 libfontconfig.so.1 libfreetype.so.6 libgcc_s.so.1 libgdk_pixbuf-2.0.so.0 libgdk-x11-2.0.so.0 libglib-2.0.so.0 libgmodule-2.0.so.0 libgobject-2.0.so.0 libgthread-2.0.so.0 libgtk-x11-2.0.so.0 libm.so.6 libpango-1.0.so.0 libpangocairo-1.0.so.0 libpangoft2-1.0.so.0 libpthread.so.0 librt.so.1 libstdc++.so.6 (version 3.4.9 or higher) libX11.so.6 libXext.so.6 libXrender.so.1 libXt.so.6 libz.so.1 libjpeg62 in 32bit....then install ccs So I better start working....... If someone else is interested in a 32 library package for this, let me know. I'm planning on using GCC (build using https://github.com/j...-eabi-toolchain) and OpenOCD with an Olimex JTAG I will definitely look into this, but so far it only looks like they have binaries, and not source. One step at a time. Quote Link to post Share on other sites
squalyl 0 Posted October 22, 2012 Share Posted October 22, 2012 Based on the makefile from the github project above, I could build a native "vanilla" toolchain from official sources, with just two little glitches: -I have to manually create a $PREFIX/arm-none-eabi/usr/include folder before building gcc the second time, or it won't build! (but nothing gets installed there) I get a pretty message: "the directory that should contain system headers does not exist", but no one on the intarwebs seems to have a satisfying solution. I don't want to patch sources, the goal is to build from official tarballs. -ld cannot find crt0.o when running arm-none-eabi-gcc trivial.c (with an empty main function), but gcc -c does work. That may not be required for our platform. I used: binutils 2.22 gcc 4.7.2 (dependencies gmp 5.0.0 and mpfr 3.1.1) newlib 1.20.0 I will retry the build in a clean VM in an attempt to reproduce the issues, then attempt to cross build the toolchain for mingw. I did that before for cegcc. jsolarski 1 Quote Link to post Share on other sites
jsolarski 94 Posted October 23, 2012 Author Share Posted October 23, 2012 I used: binutils 2.22 gcc 4.7.2 (dependencies gmp 5.0.0 and mpfr 3.1.1) newlib 1.20.0 What target are you using when configuring binutils and gcc? what prefix are you using? and are you also prefixing binaries with something? Quote Link to post Share on other sites
squalyl 0 Posted October 23, 2012 Share Posted October 23, 2012 I just did like the github project. TARGET=arm-none-eabi the prefix is /opt/stella Do you have a preference for $PREFIX? the binaries have "natural" names, do arm-none-eabi-gcc et al. I know one can create a relocatable toolchain so that it does not depend on the prefix and can be installed elsewhere, I don't remember how to do this at the moment. I also cross-built binutils for mingw, working on gcc now. bluehash and jsolarski 2 Quote Link to post Share on other sites
jsolarski 94 Posted October 24, 2012 Author Share Posted October 24, 2012 Thanks for the info! Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.