From: Daniel.Andersson@combitechsystems.com
To: jlarmour@redhat.com
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] "Invalid download offset" when downloading eCos
Date: Wed, 18 Apr 2001 23:48:00 -0000 [thread overview]
Message-ID: <2253171AF143D21185A60000F8FA748B02DA4CB0@pluto.combitech.se> (raw)
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:
-----------clip------------
Program Header:
LOAD off 0x00008000 vaddr 0x02000000 paddr 0x02000000 align 2**15
filesz 0x0000a07c memsz 0x0001239c flags rwx
private flags = 0: [interworking not enabled] [APCS-32] [floats passed in
integer registers] [absolute position]
-----------clip------------
What does it mean by LOAD off 0x00008000? It seems to me that it is this
offset that isn't correct...?
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.
/Daniel
next reply other threads:[~2001-04-18 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 23:48 Daniel.Andersson [this message]
2001-04-19 6:20 ` Lewin A.R.W. Edwards
2001-04-19 14:27 ` Jonathan Larmour
-- 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=2253171AF143D21185A60000F8FA748B02DA4CB0@pluto.combitech.se \
--to=daniel.andersson@combitechsystems.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@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).