public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: venumadhav.josyula@wipro.com
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Ecos and GCC 4.1.1
Date: Mon, 17 Dec 2007 12:44:00 -0000	[thread overview]
Message-ID: <20071217112933.GE3998@lunn.ch> (raw)
In-Reply-To: <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

       reply	other threads:[~2007-12-17 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CBE0A8E1D067704EA75C8D910F98B93D01164E45@HYD-MKD-MBX01.wipro.com>
     [not found] ` <CBE0A8E1D067704EA75C8D910F98B93D01E611EA@HYD-MKD-MBX01.wipro.com>
2007-12-17 12:44   ` Andrew Lunn [this message]
2006-03-24 18:49 [ECOS] eCos and GCC 4.1.0 Marco Aurélio da Cruz
2006-03-26 22:54 ` Andrew Lunn
2007-12-14  9:47   ` [ECOS] eCos and GCC 4.1.1 venumadhav
2007-12-14 10:29     ` Andrew Lunn
     [not found]       ` <CBE0A8E1D067704EA75C8D910F98B93D01E611E7@HYD-MKD-MBX01.wipro.com>
2007-12-17 18:39         ` [ECOS] Ecos " Andrew Lunn
2007-12-14 10:38     ` [ECOS] eCos " Paul D. DeRocco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071217112933.GE3998@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=venumadhav.josyula@wipro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).