linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-serial@vger.kernel.org
Subject: Re: Serial port read working but not write.
Date: Fri, 23 Jul 2004 12:02:26 +0200	[thread overview]
Message-ID: <20040723100226.GU18676@lug-owl.de> (raw)
In-Reply-To: <4100DAA3.7060205@wincor-nixdorf.com>

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

On Fri, 2004-07-23 11:30:11 +0200, Salomon, Frank <frank.salomon@wincor-nixdorf.com>
wrote in message <4100DAA3.7060205@wincor-nixdorf.com>:
> Hi,
> the problem is you need a procedure which find out what the problem is.
> Hardware check:
> Your hole hardware you can divided in:
> - PC - com port
> - cable
> - external Hardware
> 
> Check the com-port:
> create a cable bridge between pin 2 and 3 of you port.
> run # dd bs=1 count=1 if=/dev/ttySx | hexdump
> on an other vt run # cat /dev/inittab > /dev/ttySx
> 
> If you don't see any output on the vt, which is running "dd bs=1 count=1 
> if=/dev/ttySx | hexdump", your com port is not working correct.

This doesn't need to work, depending on handshake settings. Also, (at
least in theory), you can have different sending and receiving speeds...

> Next you can connect your cable to the PC and pug the bridge to the
> end of the cable and perform the same test.

...which also depends on tty settings.

man stty

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-23 10:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 16:48 Serial port read working but not write suresh shenoy
2004-07-22 22:20 ` Lukasz Michal Rak
2004-07-23  8:18 ` Justinas
2004-07-23  9:30 ` Salomon, Frank
2004-07-23 10:02   ` Jan-Benedict Glaw [this message]
2004-07-23 12:12     ` Salomon, Frank
2004-07-23 12:41       ` Jan-Benedict Glaw
2004-07-23 12:50         ` Salomon, Frank
2004-07-23 13:14           ` Jan-Benedict Glaw
2004-07-23 13:49             ` Salomon, Frank
2004-07-23 14:16               ` Jan-Benedict Glaw
2004-07-23  9:40 ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2004-07-24  2:04 suresh shenoy
2004-07-24 14:39 serial " suresh shenoy
2004-07-24 15:11 ` Jan-Benedict Glaw
2004-07-24 23:36 suresh shenoy
2004-07-26  7:24 ` Salomon, Frank
2004-07-26  8:12   ` Jan-Benedict Glaw
2004-07-28 19:29     ` suresh shenoy
2004-07-28 20:08       ` Jan-Benedict Glaw

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=20040723100226.GU18676@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-serial@vger.kernel.org \
    /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 NNTP newsgroup(s).