This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: RE: eCos using Codesourcery Toolchain
- From: "simon dot kallweit at intefo dot ch" <simon dot kallweit at intefo dot ch>
- To: Chris Zimman <czimman at bloomberg dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 23 Sep 2008 15:16:25 +0200
- Subject: Re: [ECOS] RE: eCos using Codesourcery Toolchain
- References: <F31C1582037F5041B0CD525FD870AE6A77450F@ny2545.corp.bloomberg.com> <48CF7928.1060703@intefo.ch> <F31C1582037F5041B0CD525FD870AE6A774512@ny2545.corp.bloomberg.com> <48CFAF14.3050502@intefo.ch> <F31C1582037F5041B0CD525FD870AE6A774513@ny2545.corp.bloomberg.com> <48CFC11F.5010402@intefo.ch> <F31C1582037F5041B0CD525FD870AE6A774514@ny2545.corp.bloomberg.com> <48D8D38D.3080402@intefo.ch> <F31C1582037F5041B0CD525FD870AE6A77452B@ny2545.corp.bloomberg.com>
Chris Zimman wrote:
Hi Simon,
It may be that the RAM/ROM region you have respectively set is too small for
the image that's being created -- or it may just be a binutils bug.
I didn't have any issues with any particular 'wierdness' like that.
The ram/rom regions should be large enough to accommodate everything.
What happens if you build your code under ARM ELF? That was usually my
sanity check if I suspect the EABI tool chain was doing something weird.
What toolchain do you use for this? I can't really use the eCos arm-elf
toolchain as it does not come with cortex support.
Simon
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss