public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Daniel.Andersson@combitechsystems.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] "Invalid download offset" when downloading eCos
Date: Thu, 19 Apr 2001 14:27:00 -0000	[thread overview]
Message-ID: <3ADF5828.CFCB9330@redhat.com> (raw)
In-Reply-To: <2253171AF143D21185A60000F8FA748B02DA4CB0@pluto.combitech.se>

Daniel.Andersson@combitechsystems.com wrote:
> 
> Hi,
> 
> >Daniel.Andersson@combitechsystems.com wrote:
> >>
> >> Hi,
> >>
> >> I am using Carl's version of eCos but i cant download any code. If i try
> >> then i get the below error message from gdb. I have tried downloading on
> >> different locations i.e. 0x02018000 and 0x02000000 and according to the
> >> manual it should be right. What else could be wrong?
> >
> >From the output it looks like the spaces in the filename path are confusing
> >it.
> >
> 
> I don't think so because i have a ledblink application in the same folder
> that is NOT using eCos and it works fine to download it. If i run an objdump
> on my output file i get the following:

It just seemed odd that the output was:

Connected to ARM RDI target.
gdb.ini:3: Error in sourced command file:
Invalid download offset: files/red hat/eCos/examples/kalle.out

Which implies that it was interpreting "file/red hat
eCos/examples/kalle.out" is a download offset. But instead I suspect that
it's just the error message output that is getting garbled because of the
space in the filename.

But if you have a different app that works,certainly compare your objdump
output with that, particularly given Lewin's comments.

> Another question: Is it possitble to download an eCos application with
> Angel and make it work fine or do i have to download an eCos gdb stub
> first.

Interworking with Angel has not been a priority due to its proprietary
nature, dearth of documentation and unreliability.

But we've made it work for the PID I believe. Check through the ARM HAL for
the option CYGSEM_HAL_ARM_PID_ANGEL_BOOT to see what is involved.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  parent reply	other threads:[~2001-04-19 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 23:48 Daniel.Andersson
2001-04-19  6:20 ` Lewin A.R.W. Edwards
2001-04-19 14:27 ` Jonathan Larmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-18  4:02 Daniel.Andersson
2001-04-18  8:57 ` Jonathan Larmour

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=3ADF5828.CFCB9330@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=Daniel.Andersson@combitechsystems.com \
    --cc=ecos-discuss@sources.redhat.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).