This is the mail archive of the
mailing list for the eCos project.
RE: RE: eCos using Codesourcery Toolchain
- From: "Chris Zimman" <czimman at bloomberg dot com>
- To: <simon dot kallweit at intefo dot ch>
- Cc: <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 23 Sep 2008 09:26:54 -0400
- Subject: RE: [ECOS] RE: eCos using Codesourcery Toolchain
- References: <F31C1582037F5041B0CD525FD870AE6A77450F@ny2545.corp.bloomberg.com> <48CF7928.firstname.lastname@example.org> <F31C1582037F5041B0CD525FD870AE6A774512@ny2545.corp.bloomberg.com> <48CFAF14.email@example.com> <F31C1582037F5041B0CD525FD870AE6A774513@ny2545.corp.bloomberg.com> <48CFC11F.firstname.lastname@example.org> <F31C1582037F5041B0CD525FD870AE6A774514@ny2545.corp.bloomberg.com> <48D8D38D.email@example.com> <F31C1582037F5041B0CD525FD870AE6A77452B@ny2545.corp.bloomberg.com> <48D8EC29.firstname.lastname@example.org>
> The ram/rom regions should be large enough to accommodate everything.
OK, then I guess we can rule that out
> 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.
I was just using a generic GNU ARM tree, but I also wasn't targeting Cortex.
I think CodeSourcery has been contributing the ARMv7/Cortex support back into
mainline recently, as seen here:
I guess you can always try grabbing a snapshot and seeing how that works.
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss