public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Miguel J. Vega" <mserrano@engin.umich.edu>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Configuring serial ports for Redboot and GDB
Date: Wed, 07 Jul 2004 16:27:00 -0000	[thread overview]
Message-ID: <1089217662.3988.1546.camel@hermes> (raw)
In-Reply-To: <Pine.GSO.4.58.0407062141450.11615@azure.engin.umich.edu>

On Tue, 2004-07-06 at 20:00, Miguel J. Vega wrote:
> Hi Gary and list,
> 
> I have built redboot with CYGPKG_REDBOOT_ANY_CONSOLE disabled, debugging
> serial port set to channel 0 (serial port 1 on board), diagnostic serial
> port set to channel 1 (serial port 2 on board). I disabled
> CYGPKG_REDBOOT_ANY_CONSOLE to simplify things and spare myself some
> confusion.
> 
> When I start up, redboot's output (redboot start-up banner, commands,
> etc.) comes from the debug port, which I assume is correct. I also use
> this port to communicate with the GDB-console (load, continue, inserting
> breakpoints, etc.). The only thing that I was not expecting was for the
> printf() functions (when I am running programs from GDB) to output through
> the diagnostic port. This output appears on a hyperterminal window that
> I have open on another PC, since I only have one com port available on
> each PC.
> 
> I would like for the printf() output to go to the GDB-console,
> but the GDB-console currently communicates to the board via the debugging
> port. Any ideas on how I can make it happen?

This is how it is supposed to work - all "console" output through GDB
goes via the debug channel.

If you want to have a debug channel (used by GDB and diag_printf()), and
separate other channel for printf() to use (of course, this would 
require two serial connections), then you'll need to do some 
configuring.  

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2004-07-07 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07  2:00 Miguel J. Vega
2004-07-07 16:27 ` Gary Thomas [this message]
2004-08-16 16:57   ` [ECOS] redboot help Sam Pham

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=1089217662.3988.1546.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=mserrano@engin.umich.edu \
    /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).