public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Perry Wang" <perrywang@nmnc.com>
To: <jlarmour@cygnus.co.uk>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] LIBC and STDIO
Date: Fri, 17 Dec 1999 16:05:00 -0000	[thread overview]
Message-ID: <NDBBKBNDILCIAEJMGDCGEEECCBAA.perrywang@nmnc.com> (raw)
In-Reply-To: <385A9BA7.DF48BC9@cygnus.co.uk>

Hi Mr. Larmour,

I don't know what did it, but after downloading and setting up the latest
CVS source tree, the printf works with "/dev/tty1"

thanks for all the help.  appreciate it.

btw, that gdb/sniffing really sounds impressive.  I used to only use it for
hacking purpose :)

regards,

Perry

> -----Original Message-----
> From: jlarmour@cygnus.co.uk [ mailto:jlarmour@cygnus.co.uk ]
> Sent: Friday, December 17, 1999 12:23 PM
> To: Perry Wang
> Cc: jskov@cygnus.co.uk; ecos-discuss@sourceware.cygnus.com
> Subject: Re: [ECOS] LIBC and STDIO
>
>
> Perry Wang wrote:
> >
> > I do have the serial package enabled.. some of the defines are here:
> >
> [snip]
> > io write to /dev/tty1 or /dev/ser1 directly works fine.
> However the libc
> > printf doesn't like it.  I guess I'm still missing something.  Changing
> > CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE back to "/dev/haldiag" will
> work, but it
> > prints out some garbage only GDB will understand.
>
> I suppose it isn't very helpful for me to say that I just tried it here on
> an AEB-1B and (from what I could tell[1]) I could run the libc stdiooutput
> test fine.
>
> Have you tried the other serial line? It could be some conflict
> between the
> hal diag initialization and the serial driver initialization - we've had
> such things happen before. If that doesn't work either, it at least gives
> you the chance to debug it (using GDB attached to the first
> serial line) to
> see what is going on.
>
> [1] For reasons to long to explain, I connected with GDB over a TCP
> connection to a proxy test server, and used an ethernet packet
> sniffer since
> GDB silently discards anything not in remote protocol packets. Yes, I'm
> lazy.
>
> Jifl
> --
> Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44
> (1223) 728762
> "I used to have an open mind but || Get yer free open source
> RTOS's here...
>  my brains kept falling out."    || http://sourceware.cygnus.com/ecos
> Help fight spam! http://spam.abuse.net/  These opinions are all
> my own fault

  reply	other threads:[~1999-12-17 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-16 16:35 Perry Wang
1999-12-17  0:30 ` Jesper Skov
1999-12-17 11:04   ` Perry Wang
1999-12-17 12:23     ` Jonathan Larmour
1999-12-17 16:05       ` Perry Wang [this message]
1999-12-21 14:51     ` [ECOS] tty driver Perry Wang
1999-12-21 14:56       ` Perry Wang

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=NDBBKBNDILCIAEJMGDCGEEECCBAA.perrywang@nmnc.com \
    --to=perrywang@nmnc.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).