[SOLVED] Need help with Compiling to TM4C123glx with arm-none-eabi-gcc

Question

Hello !
I was using the 'arm-none-eabi-gcc' package from 'comunity' on Arch Linux in order to compile some projects to my TI TM4C123gxl.
In order to test the compiler, I rebuild a pre-build example sent with the 'Tivaware' software package (qs-rgb). The compilation was smooth, but the final binary didn't run on the board. (about 14KB)
After that, I downloaded a toolchain from this website:
https://launchpad.net/gcc-arm-embedded
Which also ships an 'arm-none-eabi-gcc'.
The compilation with the toolchain above could generate a binary that could run on my board. (about 10KB)
At first, I thought it was a bug, and I was on my way to file a bug report.  But then I remember that this toolchain can be build with several different options, so I need to ask:
Do your package have support to this target? (TI TM4C123glx)
Is there a difference between the two toolchains that I should have noticed?
Sorry if my questions are some obvious things. I have no much information about toolchain building.
If you need any more informations about this, I will be happy to send you.
If you prefer I open a bug report, I will be happy to do so.
Thank you!
Last edited by leonardo (2014-11-07 00:24:38)

Answer 1

leonardo, here is completely untested patch that makes arm-none-eabi-gcc use newlib-nano instead of newlib. Get the PKGBUILD from ABS, apply the patch and rebuild the *-gcc. Let me know if it makes any difference.
The -nano project goal is provide smaller footprint in probably the reason of smaller binary with linaro toolchain.
Index: PKGBUILD
===================================================================
--- PKGBUILD (revision 121494)
+++ PKGBUILD (working copy)
@@ -8,6 +8,7 @@
pkgrel=1
#_snapshot=4.9-20140604
_newlibver=2.1.0
+_newlibnanover=2.1
pkgdesc='The GNU Compiler Collection - cross compiler for ARM EABI (bare-metal) target'
arch=(i686 x86_64)
url='http://gcc.gnu.org/'
@@ -18,12 +19,12 @@
options=(!emptydirs !strip staticlibs)
source=(ftp://gcc.gnu.org/pub/gcc/releases/gcc-$pkgver/gcc-$pkgver.tar.bz2
#ftp://gcc.gnu.org/pub/gcc/snapshots/$_snapshot/gcc-$_snapshot.tar.bz2
- ftp://sourceware.org/pub/newlib/newlib-$_newlibver.tar.gz
+ https://github.com/32bitmicro/newlib-nano-2/archive/newlib-nano-$_newlibnanover.zip
gcc-multilib.patch
gcc-no-exceptions.patch
libgloss-configure-fix.patch)
sha256sums=('d334781a124ada6f38e63b545e2a3b8c2183049515a1abab6d513f109f1d717e'
- '3e4d5ab9f0508942b6231b8ade4f8e5048cf92c96ed574c2bd6bd3320a599a48'
+ '51cdc44ff7821837701316e4145d48b2dc27e43713f88194f6f147c6f09651a9'
'998d1face674cc8d1af5bf28ded15caaaa18936a28f278123448f29555a07775'
'7f59b28475aa2018a7edfb81ea81444a6eb098fd3847d8e605809ae6fbeabde5'
'eac96c034d3d7d16080d9aef4749e4eda493563a3348e6a06f08e8a330b027ba')
@@ -36,7 +37,7 @@
prepare() {
# Apply configure fix from newlib CVS
- cd "$srcdir/newlib-$_newlibver/libgloss/arm"
+ cd "$srcdir/newlib-nano-2-newlib-nano-$_newlibnanover/libgloss/arm"
patch -Np0 -i "$srcdir/libgloss-configure-fix.patch"
autoreconf
@@ -47,8 +48,8 @@
patch -Np0 -i "$srcdir"/gcc-no-exceptions.patch
# Move newlib and libgloss to gcc source directory
- mv "$srcdir"/newlib-$_newlibver/newlib "$srcdir/$_basedir"
- mv "$srcdir"/newlib-$_newlibver/libgloss "$srcdir/$_basedir"
+ mv "$srcdir"/newlib-nano-2-newlib-nano-$_newlibnanover/newlib "$srcdir/$_basedir"
+ mv "$srcdir"/newlib-nano-2-newlib-nano-$_newlibnanover/libgloss "$srcdir/$_basedir"
# hack! - some configure tests for header files using "$CPP $CPPFLAGS"
sed -i "/ac_cpp=/s/\$CPPFLAGS/\$CPPFLAGS -O2/" "$srcdir"/$_basedir/{libiberty,gcc}/configure