From: jens.ohlund@secrc.abb.se
To: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Moving eCos stubb in memory ?
Date: Tue, 04 Jul 2000 00:26:00 -0000 [thread overview]
Message-ID: <OF17C0843E.41A85F2D-ONC1256912.002899BF@secrc.abb.se> (raw)
Hi !
Is it really that tricky ?
I mean, the code already exist for the platform, I just want to change the offset of the gdb stub.
Seems like an awfully lots of work for just a small thing.
But hey, what do i know, I'm just a whining user ;)
yours
Jens
ecos-discuss-owner@sourceware.cygnus.com
2000-07-03 22:15
Please respond to ecos <ecos-discuss@sourceware.cygnus.com>
To: ecos <ecos-discuss@sourceware.cygnus.com>
cc:
Subject: Re: [ECOS] Moving eCos stubb in memory ?
Security Level:? Internal
jens.ohlund@secrc.abb.se wrote:
>
> Hi !
>
> Just a short question.
>
> I have a AEB-1. On the flash there is the bootstrap, Angel and eCos after
> following the usual instructions.
>
> But if I want to remove Angel and move eCos to the place directly after the
> bootstrap, what files am I to change ?
> Or it isn't possible ?
>
> yours
> Jens Ohlund
Hi Jens
I was working on that a few months ago and and almost got a gdb stub
working but had to put that aside to get back to finishing the hardware
design. From a terminal I was getting character strings that looked
like gdb packets but gdb didn't seem to recognize them, I will be back
working on it in about 2 weeks.
The documentation, on porting eCos, I was working with was a bit stale
but here is a link for some more up-to-date info.
http://sourceware.cygnus.com/ecos/docs-latest/porting/
--
Ormund
next reply other threads:[~2000-07-04 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-04 0:26 jens.ohlund [this message]
2000-07-04 6:43 ` Ormund Williams
-- strict thread matches above, loose matches on Subject: below --
2000-07-03 7:57 jens.ohlund
2000-07-03 13:07 ` Ormund Williams
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=OF17C0843E.41A85F2D-ONC1256912.002899BF@secrc.abb.se \
--to=jens.ohlund@secrc.abb.se \
--cc=ecos-discuss@sourceware.cygnus.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).