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 18:39:00 -0000	[thread overview]
Message-ID: <20071217124414.GH3998@lunn.ch> (raw)
In-Reply-To: <CBE0A8E1D067704EA75C8D910F98B93D01E611E7@HYD-MKD-MBX01.wipro.com>

> 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.

And what exactly does the debugger say?

What does Wind River say? 

Like i said, this is a tool chain problem, not eCos.

     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

  parent reply	other threads:[~2007-12-17 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24 18:49 [ECOS] eCos and GCC 4.1.0 Marco Aurélio da Cruz
2006-03-26 22:54 ` Andrew Lunn
2006-03-27 16:40   ` Marco Aurélio da Cruz
2006-03-27 17:38     ` oliver munz @ s p e a g
2006-03-28  0:30       ` Marco Aurélio da Cruz
2006-03-28 12:38         ` Jonathan Larmour
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         ` Andrew Lunn [this message]
2007-12-14 10:38     ` Paul D. DeRocco
     [not found] <CBE0A8E1D067704EA75C8D910F98B93D01164E45@HYD-MKD-MBX01.wipro.com>
     [not found] ` <CBE0A8E1D067704EA75C8D910F98B93D01E611EA@HYD-MKD-MBX01.wipro.com>
2007-12-17 12:44   ` [ECOS] Ecos " Andrew Lunn

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=20071217124414.GH3998@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).