From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: "amassa@cts.com" <amassa@cts.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: MBX Board
Date: Tue, 30 May 2000 14:25:00 -0000 [thread overview]
Message-ID: <393431D1.28DDEDF6@redhat.co.uk> (raw)
In-Reply-To: <200005302113.OAA67770@batman.cts.com>
"amassa@cts.com" wrote:
>
> I am using the MBX860 board for development. This board has the EPPC-bug
> firmware programmed into flash.
>
> What I want to do is to be able to download my own programs - initially just
> a basic program. I would like to have GDB support present as well.
>
> I don't know if I need to compile a gdb stub and download that first into
> RAM and then use that to connect insight and download my application code.
>
> I would like to leave the EPPC-bug firmware as is in ROM, and not program
> over it.
You should include the GDB support in the application you download, in the
form of GDB stubs.
To do this, go to the "eCos HAL" package and under "Source-level debugging
support" there is the "Include GDB stubs in HAL" option (aka
CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS), which you should enable. If you want
Ctrl-C to work with stubs enabled, you should also enable GDB break support
for stubs (CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT).
Jesper may have some more input.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next parent reply other threads:[~2000-05-30 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200005302113.OAA67770@batman.cts.com>
2000-05-30 14:25 ` Jonathan Larmour [this message]
2000-05-30 14:29 ` Gary Thomas
[not found] <200005302201.PAA70440@batman.cts.com>
2000-05-30 15:10 ` Gary Thomas
[not found] <200005302219.PAA71424@batman.cts.com>
2000-05-30 16:38 ` Gary Thomas
[not found] <200006061724.KAA77998@batman.cts.com>
2000-06-06 23:51 ` [ECOS] " Jesper Skov
[not found] <200006071617.JAA24571@batman.cts.com>
2000-06-08 0:41 ` Jesper Skov
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=393431D1.28DDEDF6@redhat.co.uk \
--to=jlarmour@redhat.co.uk \
--cc=amassa@cts.com \
--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).