public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@redhat.com>
To: Jonathan Larmour <jlarmour@redhat.co.uk>
Cc: ecos-discuss@sourceware.cygnus.com, "amassa@cts.com" <amassa@cts.com>
Subject: RE: [ECOS] Re: MBX Board
Date: Tue, 30 May 2000 14:29:00 -0000	[thread overview]
Message-ID: <XFMail.000530152929.gthomas@redhat.com> (raw)
In-Reply-To: <393431D1.28DDEDF6@redhat.co.uk>

The MBX boards we have actually have two separate flash chips.  Based on the
use of jumper J4 you can select between the two.  My board has EPPC-bug in one
flash chip and eCos GDB stubs in the other.

On 30-May-00 Jonathan Larmour wrote:
> "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
> 

  reply	other threads:[~2000-05-30 14:29 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
2000-05-30 14:29   ` Gary Thomas [this message]
     [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=XFMail.000530152929.gthomas@redhat.com \
    --to=gthomas@redhat.com \
    --cc=amassa@cts.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.co.uk \
    /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).