This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Ecos and GCC 4.1.1
- From: Andrew Lunn <andrew at lunn dot ch>
- To: venumadhav dot josyula at wipro dot com
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Mon, 17 Dec 2007 12:29:33 +0100
- Subject: Re: [ECOS] Ecos and GCC 4.1.1
- References: <CBE0A8E1D067704EA75C8D910F98B93D01164E45@HYD-MKD-MBX01.wipro.com> <CBE0A8E1D067704EA75C8D910F98B93D01E611EA@HYD-MKD-MBX01.wipro.com>
On Mon, Dec 17, 2007 at 04:22:37PM +0530, venumadhav.josyula@wipro.com wrote:
>
> Hi Andrew,
>
> I want to bit clear in
>
> experiment#1
> we compiled Ecos + stack + application using arm-elf-gcc 4.1.1
>
> experiment#2
> We compiled Ecos + stack + application using arm-elf-gcc 3.0
>
> Cheers,
> Venu
>
> ________________________________
>
> From: Venumadhav Josyula (WT01 - Wipro NewLogic)
> Sent: Monday, December 17, 2007 4:20 PM
> To: 'Andrew Lunn'
> Cc: 'ecos-discuss@ecos.sourceware.org'
> Subject: RE: [ECOS] Ecos and GCC 4.1.1
>
>
> Hi Andrew,
>
> I got over the problem by downloading the latest Ecos sources. After
> that I am facing a unique problem. After I built the Ecos library, I
> replaced the target.ld with the target.ld which we use for our
> development environment.
>
> Now we built our stack code and application using the library generated
> from the latest sources (these sources were compiled using arm-elf-gcc
> 4.1.1). We are able to generate the .axf image. But we are not able to
> load the .axf image using axd debugger.
This is a toolchain/debugger problem, not an eCos problem. Try looking
on the gcc mailling lists and talk to the tech support for axd.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss