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


Groups > comp.arch.embedded > #29028 > unrolled thread

stty -F /dev/ttyUSB0

Started byJohann Klammer <klammerj@NOSPAM.a1.net>
First post2020-01-06 10:30 +0100
Last post2020-01-07 10:18 +0100
Articles 5 — 1 participant

Back to article view | Back to comp.arch.embedded


Contents

  stty -F /dev/ttyUSB0 Johann Klammer <klammerj@NOSPAM.a1.net> - 2020-01-06 10:30 +0100
    Re: stty -F /dev/ttyUSB0 Johann Klammer <klammerj@NOSPAM.a1.net> - 2020-01-06 13:33 +0100
      Re: stty -F /dev/ttyUSB0 Johann Klammer <klammerj@NOSPAM.a1.net> - 2020-01-06 14:13 +0100
        Re: stty -F /dev/ttyUSB0 Johann Klammer <klammerj@NOSPAM.a1.net> - 2020-01-07 09:08 +0100
          Re: stty -F /dev/ttyUSB0 Johann Klammer <klammerj@NOSPAM.a1.net> - 2020-01-07 10:18 +0100

#29028 — stty -F /dev/ttyUSB0

FromJohann Klammer <klammerj@NOSPAM.a1.net>
Date2020-01-06 10:30 +0100
Subjectstty -F /dev/ttyUSB0
Message-ID<quuuo7$mk6$1@gioia.aioe.org>
stty -F /dev/ttyUSB0
speed 0 baud; line = 0;
min = 1; time = 0;
-brkint -icrnl -imaxbel
-opost
-isig -icanon -iexten -echo

(something is wrong)

stty -F /dev/ttyUSB0 ispeed 38400
stty: /dev/ttyUSB0: unable to perform all requested operations

But if I give an obv wrong value it doesn't complain.
stty -F /dev/ttyUSB0 ispeed 3840


The dongle is a
FTDI Chip
TTL-232R-5V
USB to TTL Serial Cable(5.0V)-1.8m (2419945 at Farnell)

On Linux kernel Version 3.14.15

I guess since the're the monopolist 
they don't have to produce working hardware anymore.

And yes, I've read the crap about read write access on stackoverflow. 
I am in the plugdev group and it's read/writable for plugdev.

[toc] | [next] | [standalone]


#29031

FromJohann Klammer <klammerj@NOSPAM.a1.net>
Date2020-01-06 13:33 +0100
Message-ID<quv9fg$8c1$1@gioia.aioe.org>
In reply to#29028
Oh, and scoping the output shows that the actual rate is at least 1MBaud
(the narrowest pulses are around 1uS wide.)

[toc] | [prev] | [next] | [standalone]


#29033

FromJohann Klammer <klammerj@NOSPAM.a1.net>
Date2020-01-06 14:13 +0100
Message-ID<quvbpd$n9o$1@gioia.aioe.org>
In reply to#29031
On 01/06/2020 01:33 PM, Johann Klammer wrote:
> Oh, and scoping the output shows that the actual rate is at least 1MBaud
> (the narrowest pulses are around 1uS wide.)
> 
> 
ok. seems it's not the actual number that matters, but the number of invocations. 
It's some internal state that changes.

$ stty -F /dev/ttyUSB0 ispeed 38400
stty: /dev/ttyUSB0: unable to perform all requested operations
$ stty -F /dev/ttyUSB0 ispeed 38400
(this one succeeds)

[toc] | [prev] | [next] | [standalone]


#29054

FromJohann Klammer <klammerj@NOSPAM.a1.net>
Date2020-01-07 09:08 +0100
Message-ID<qv1e9c$5rq$1@gioia.aioe.org>
In reply to#29033
On 01/06/2020 02:13 PM, Johann Klammer wrote:
> $ stty -F /dev/ttyUSB0 ispeed 38400
> stty: /dev/ttyUSB0: unable to perform all requested operations
> $ stty -F /dev/ttyUSB0 ispeed 38400
> (this one succeeds)
> 
> 
may have been a user error.
$ stty -F /dev/ttyUSB0 38400
works at once.

I did scope the output again and observed a tau of 23 uS.
(=baud rate err of 0.11) Is this too much?
Because I still can't get the uC to respond..

[toc] | [prev] | [next] | [standalone]


#29059

FromJohann Klammer <klammerj@NOSPAM.a1.net>
Date2020-01-07 10:18 +0100
Message-ID<qv1idp$nt9$1@gioia.aioe.org>
In reply to#29054
On 01/07/2020 09:08 AM, Johann Klammer wrote:
> 
> I did scope the output again and observed a tau of 23 uS.
> (=baud rate err of 0.11) Is this too much?
> Because I still can't get the uC to respond..
> 
> 
Nah user error again. is closer to 25uS...

[toc] | [prev] | [standalone]


Back to top | Article view | comp.arch.embedded


csiph-web