public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andreas.Karlsson@combitechsystems.com
To: ecos-discuss@sourceware.cygnus.com, aeb@arm.com
Subject: [ECOS] UART communication
Date: Tue, 05 Sep 2000 06:16:00 -0000	[thread overview]
Message-ID: <2253171AF143D21185A60000F8FA748B0229A94D@pluto.combitech.se> (raw)

Hi,

While receiving several bytes on the UART0 port on my AEB-board the
eCos-serialdriver says it only received 1 byte with the value of 0.

The incoming data looks very nice on an oscilloscope. 

Just to be sure that I hadn't messed something up in my receiver-thread I
connected the TX and the RX pin and sent 4 bytes, the packet was received
just as it should.



I compiled the ser0 with a baud rate of 57600 since that's the only one I
can use. The other settings are 1 stop bit, no parity, wordsize=8 and
CTS/RTS enabled.

I noticed that the baudrate of 57600 wasn't supported in aeb_serial.h but
what happens when I make this selection in the configuration?

To be able to enable CTS/RTS I had to modify the select_baud-array in
aeb_serial.h. This because I should be able to set all fields in the
cyg_serial_info_t struct. I added the value of 26 on the bauddivisor for
57600, maybe this is the problem.

I really don't know what could be wrong so if anybody has a clue...

/Andreas

             reply	other threads:[~2000-09-05  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-05  6:16 Andreas.Karlsson [this message]
2000-09-05  8:52 ` Dave Airlie
2000-09-05  9:03   ` Gary Thomas
2000-09-05  9:04 ` Jonathan Larmour
2000-09-05 22:32 Andreas.Karlsson
2000-09-06 10:01 ` Jonathan Larmour
2000-09-07  0:25   ` Jesper Skov
2000-09-06 10:21 Andreas.Karlsson
2000-09-06 10:31 ` 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=2253171AF143D21185A60000F8FA748B0229A94D@pluto.combitech.se \
    --to=andreas.karlsson@combitechsystems.com \
    --cc=aeb@arm.com \
    --cc=ecos-discuss@sourceware.cygnus.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).