public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'Jesper Skov' <jskov@redhat.com>
Cc: "Ecos-List (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Fast serial debugging
Date: Wed, 26 Jul 2000 14:21:00 -0000	[thread overview]
Message-ID: <21DDE8E5343ED411840A00A0CC3340201047F8@EXCHANGE5_5> (raw)

> -----Original Message-----
> From: Jesper Skov [ mailto:jskov@redhat.com ]
> Subject: Re: [ECOS] Fast serial debugging
> 
> Have you tried connecting using a terminal emulator? It could just be
> that the board cannot keep up at 115200 - I don't think it's using the
> FIFO.

From the board manual, this is a ST16C552 UART with FIFO. And, according to
the manual the baud generator can be programmed to 56K or 115.2K as well as
38.4K. 

And we are abble to connect to the Angel monitor on this board with the ARM
dev tools. But it was not very reliable. ( The board User Guide say % ERROR
=2.77 for 56K...)
 
> eCos should be able to handle 57600. It may be that it has failed to
> do so in tests - and so has been disabled in the config. That would be
> a mistake. Try adding it to the CDL and see if it behaves correctly.

I added to the config, plus I had to modify two files (plf_stub.c and
hal_diag.c) to add the correct programming for 56K. By the way this is the
same duplicated code that I had to modify in those two files.

Then I recompiled the whole at 57600, and it doesn't work at 56K. But it
does work at 38400.
So I guess the stub serial driver doesn't use the same code than the HAL
serial driver.

thanks

A+
-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com 

             reply	other threads:[~2000-07-26 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-26 14:21 Fabrice Gautier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-26 16:45 Fabrice Gautier
2000-07-26 16:24 Fabrice Gautier
2000-07-24 12:46 Fabrice Gautier
2000-07-25  2:59 ` 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=21DDE8E5343ED411840A00A0CC3340201047F8@EXCHANGE5_5 \
    --to=fabrice_gautier@sdesigns.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jskov@redhat.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).