public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jamie Guinan <guinan@bluebutton.com>
To: Jonathan Larmour <jlarmour@cygnus.co.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] loader.bin sources?
Date: Sun, 18 Jul 1999 10:25:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.990718131234.873A-100000@newt.home.net> (raw)
In-Reply-To: <199907161917.UAA04869@peshwari.cygnus.co.uk>

On Fri, 16 Jul 1999, Jonathan Larmour wrote:

> 3. Edit pkgconf/hal.h *by hand* and enable the following "#define"s:
> 
> CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
> CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
> CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT
> CYG_HAL_ROM_MONITOR
> 
> You should also comment out the line:
> #define CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT

I found that I had to #undef CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT
or else I got "undefined reference to `dbg_currthread'" from
function "stub_lock_scheduler".

And there was no CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT to be
commented out.  GDB_BREAK_SUPPORT appears to handle ctrl-c
breaks, though.

Aside from that, I did manage to build a new stubrom image.
Thanks for the directions!

What I want to do next is make an stubrom image for the FADS 823
board.  I understand that the FADS is unsupported, but my client
(he has a Cygnus support contract) pointed me at the MBX HAL 
for an example.  For starters, it looks like the Cogent has
external 16550 uarts whereas the MBX and FADS use on-chip
SMCs or SCCs.

Bummer, I didn't bring home a copy of the MBX HAL code.  Any idea 
when the MBX code will make it into public CVS?

-Jamie

  reply	other threads:[~1999-07-18 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-16 11:10 Jamie Guinan
1999-07-16 12:18 ` Jonathan Larmour
1999-07-18 10:25   ` Jamie Guinan [this message]
1999-07-21  1:04     ` [ECOS] MBX stubrom (was [ECOS] loader.bin sources?) Jamie Guinan
1999-07-21  7:06       ` Gary Thomas
1999-07-21  8:45       ` [ECOS] " Jonathan Larmour
1999-07-21 10:02         ` Jamie Guinan
1999-07-21 10:06           ` 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=Pine.LNX.3.96.990718131234.873A-100000@newt.home.net \
    --to=guinan@bluebutton.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@cygnus.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).