Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #220967

Re: Serial Port Issues

From deloptes <deloptes@gmail.com>
Newsgroups linux.debian.user
Subject Re: Serial Port Issues
Date 2020-04-06 10:10 +0200
Message-ID <zSuZr-ik-11@gated-at.bofh.it> (permalink)
References <zSsuB-7a0-3@gated-at.bofh.it> <zStTI-7So-13@gated-at.bofh.it> <zSuwq-8kD-9@gated-at.bofh.it> <zSuPM-8rp-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


tomas@tuxteam.de wrote:

> What has agetty to do with not being able to access a port?
> 
>> I doubt it's that. 9600 is a sort of default these days, and a serial
>> port which could not use it would be of limited use. The XBee radio
>> modules, for example, come from the factory running at 9600, though of
>> course they will go much higher. But the configuration utility must run
>> at 9600 to begin with.
> 
> Besides, the wrong baud rate wouldn't preclude a program from *reading*
> from a serial interface. It would just get garbage, that's all.
> 
> Besides, a wrong baud rate would much less explain that writing is
> possible, but reading isn't. Not for classical "serials" (i.e. RS-232).

Well, I must admit you are right (once again). I don't agree with Joes
statement that 9600 is default. 

I just now have a memory enlight. I was also not able to write on the RPIs
UART port until I disabled the hardware flow control. Found out that for
the UART it doesn't matter if soft/hard is enabled or not.

[   | F - Hardware Flow Control : No
[   | G - Software Flow Control : No

it is worth checking

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Serial Port Issues Chris Rhodin <cprhodin@gmail.com> - 2020-04-06 07:30 +0200
  Re: Serial Port Issues deloptes <deloptes@gmail.com> - 2020-04-06 09:00 +0200
    Re: Serial Port Issues Joe <joe@jretrading.com> - 2020-04-06 09:40 +0200
      Re: Serial Port Issues <tomas@tuxteam.de> - 2020-04-06 10:00 +0200
        Re: Serial Port Issues deloptes <deloptes@gmail.com> - 2020-04-06 10:10 +0200
        Re: Serial Port Issues rhkramer@gmail.com - 2020-04-06 16:00 +0200
          Re: Serial Port Issues <tomas@tuxteam.de> - 2020-04-06 16:10 +0200
            Fwd: Serial Port Issues Chris Rhodin <cprhodin@gmail.com> - 2020-04-07 08:00 +0200
              Re: Fwd: Serial Port Issues deloptes <deloptes@gmail.com> - 2020-04-07 08:50 +0200
                Re: Fwd: Serial Port Issues "Martin McCormick" <martin.m@suddenlink.net> - 2020-04-07 15:30 +0200
                Re: Serial Port Issues Joe <joe@jretrading.com> - 2020-04-07 18:50 +0200
              Re: Serial Port Issues Chris Rhodin <cprhodin@gmail.com> - 2020-04-07 09:00 +0200
                Re: Serial Port Issues <tomas@tuxteam.de> - 2020-04-07 09:10 +0200
                Re: Serial Port Issues Chris Rhodin <cprhodin@gmail.com> - 2020-04-07 09:10 +0200
                Re: Serial Port Issues songbird <songbird@anthive.com> - 2020-04-08 13:50 +0200
              Re: Serial Port Issues Joe <joe@jretrading.com> - 2020-04-07 09:30 +0200
      Re: Serial Port Issues Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-06 14:40 +0200
        Re: Serial Port Issues Joe <joe@jretrading.com> - 2020-04-06 15:30 +0200

csiph-web