Hi Eigil, > Which version of the CodeSourcery tool chain do you use. I have > "arm-none-eabi". When I use that chain to compile eCos + app. I have the > problem, that e.g. printf doesn't call the eCos function and thus nothing is > printed. > > Did you build the libraries youself? >
I use arm-none-eabi and I like with: "-Ttarget.ld -nostdlib -L<path>/ecos_install/lib" Which arm cpu do you use? Bye... > > -----Original Message----- > From: Stefan Sommerfeld [mailto:[email protected]] > Sent: 5. april 2011 10:22 > To: Eigil Krogh Sørensen > Cc: [email protected] > Subject: Re: [ECOS] Questions about CodeSourcery g++ Lite tool chain and eCos > > Hi Eigil, > >> >> . Is it possible to use CodeSourcery g++ Lite toolchain for eCos? I would >> like to use that because the compiler is newer, gcc-4.5.1, than the gnutools >> for ARM, that comes with eCos, gcc-4.3. gcc-4.5. can make code ARM11 and >> Cortex-R/A. >> >> . Can CodeSourcery g++ Lite toolchain be used together with eCos config tool >> in Windows? >> >> . Which version of the CodeSourcery g++ Lite toolchain should be used with >> eCos? >> > > I'm using latest CodeSourcery toolchain for eCos (the arm gcc). If you want to > use cygwin you need make version 3.80, because the latest make doesn't work > correctly with non-cygwin paths and a correctly set CYGPATH variable. Build > directly in ecos config tool does not work, but creating a config and running > make in the *_build dir does. > > I hope this helps you. > > Bye... > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
