From: "John Hein" <3fbmqnhaz4@snkmail.com>
To: cygwin@cygwin.com
Subject: Re: stty icrnl
Date: Thu, 09 Jun 2016 22:49:00 -0000 [thread overview]
Message-ID: <3714-1465512516-93510@sneakemail.com> (raw)
In-Reply-To: <72EAE5BB-D905-4394-BEB4-5303ED8879A4@etr-usa.com>
Warren Young wrote at 12:34 -0600 on Jun 9, 2016:
> On Jun 7, 2016, at 6:05 PM, Brian Inglis <Brian.Inglis@SystematicSw.ab.ca> wrote:
> >
> >
> > cu is the normal Unixy way of using a remote USB->serial line, but I can't
> > find it in Cygwin packages
>
> Taylor UUCP builds out of the box on Cygwin:
>
> $ wget ftp://ftp.gnu.org/pub/gnu/uucp/uucp-1.07.tar.gz
> $ tar xf uucp-1.07.tar.gz
> $ cd uucp-1.07
> $ configure && make -j11
> $ ./cu --version
> cu (Taylor UUCP) 1.07
> Copyright (C) 1991, 92, 93, 94, 1995, 2002 Ian Lance Taylor
> This program is free software; you may redistribute it under the terms of
> the GNU General Public LIcense. This program has ABSOLUTELY NO WARRANTY.
>
> > searching for \<cu\>, and cu spews too many hits.
>
> When searching on the Cygwin package search page, adding .exe to executables narrows the results considerably.
>
> As it happens, there is a Cygwin package shipping *cu.exe, but it is not the cu(1) you are looking for. Move along.
>
> Adding a leading slash fixes that:
>
> Found 0 matches for /cu.exe
>
> If you were searching elsewhere (e.g. Google) then, yes, “cu” is a bad search term. But if you knew that cu comes from the UUCP package, “cu uucp” leads you right to Taylor UUCP.
>
> See, I *knew* there was a reason I was spending my days on amber VT220s hacking Unix back when I could have been out making Vitamin D!
miniterm.py is a nice cross-platform (pure python) serial program
that is CLI (like tip/cu). It's part of the pyserial package.
In the past, it (pyserial) has not been in the cygwin repo, but it
may be now. If not, just install python-setuptools and do
'easy_install pyserial'. I've used 'pip install pyserial' as well
(but probably had to 'easy_install pip' since pip also isn't
cygwin-packagified either).
I always meant to package pyserial for cygwin but never got around to
it. A nice feature is the ability to toggle dynamically between
different settings including presentation modes (raw, escaped control
characters, hex), baud rate, flow ctrl or not, cr/lf line endings.
Plus it's easy to write little python scripts using the pyserial API
to twiddle things on the serial port
(http://pythonhosted.org/pyserial/).
Here's the live help screen:
--- pySerial (2.7) - miniterm - help
---
--- Ctrl+] Exit program
--- Ctrl+T Menu escape key, followed by:
--- Menu keys:
--- Ctrl+T Send the menu character itself to remote
--- Ctrl+] Send the exit character itself to remote
--- Ctrl+I Show info
--- Ctrl+U Upload file (prompt will be shown)
--- Toggles:
--- Ctrl+R RTS Ctrl+E local echo
--- Ctrl+D DTR Ctrl+B BREAK
--- Ctrl+L line feed Ctrl+A Cycle repr mode
---
--- Port settings (Ctrl+T followed by the following):
--- p change port
--- 7 8 set data bits
--- n e o s m change parity (None, Even, Odd, Space, Mark)
--- 1 2 3 set stop bits (1, 2, 1.5)
--- b change baud rate
--- x X disable/enable software flow control
--- r R disable/enable hardware flow control
and --help:
miniterm.py --help
Usage: miniterm.py [options] [port [baudrate]]
Miniterm - A simple terminal program for the serial port.
Options:
-h, --help show this help message and exit
Port settings:
-p PORT, --port=PORT
port, a number or a device name. (deprecated option,
use parameter instead)
-b BAUDRATE, --baud=BAUDRATE
set baud rate, default 9600
--parity=PARITY set parity, one of [N, E, O, S, M], default=N
--rtscts enable RTS/CTS flow control (default off)
--xonxoff enable software flow control (default off)
--rts=RTS_STATE set initial RTS line state (possible values: 0, 1)
--dtr=DTR_STATE set initial DTR line state (possible values: 0, 1)
Data handling:
-e, --echo enable local echo (default off)
--cr do not send CR+LF, send CR only
--lf do not send CR+LF, send LF only
-D, --debug debug received data (escape non-printable chars)
--debug can be given multiple times: 0: just print
what is received 1: escape non-printable characters,
do newlines as unusual 2: escape non-printable
characters, newlines too 3: hex dump everything
Hotkeys:
--exit-char=EXIT_CHAR
ASCII code of special character that is used to exit
the application
--menu-char=MENU_CHAR
ASCII code of special character that is used to
control miniterm (menu)
Diagnostics:
-q, --quiet suppress non-error messages
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-06-09 22:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 12:05 Achim Gratz
2016-06-06 15:09 ` Achim Gratz
2016-06-07 9:31 ` Achim Gratz
2016-06-08 0:06 ` Brian Inglis
2016-06-08 5:40 ` Achim Gratz
2016-06-09 3:16 ` Andrey Repin
2016-06-09 18:58 ` Warren Young
2016-06-09 22:08 ` Achim Gratz
2016-06-09 22:31 ` Warren Young
2016-06-10 8:29 ` Achim Gratz
2016-06-10 15:38 ` Achim Gratz
2016-06-13 12:18 ` Achim Gratz
2016-06-10 8:42 ` Corinna Vinschen
2016-06-10 8:57 ` Helmut Karlowski
2016-06-10 10:00 ` Helmut Karlowski
2016-06-10 14:39 ` Corinna Vinschen
2016-06-10 19:45 ` Achim Gratz
2016-06-09 18:34 ` Warren Young
2016-06-09 22:49 ` John Hein [this message]
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=3714-1465512516-93510@sneakemail.com \
--to=3fbmqnhaz4@snkmail.com \
--cc=cygwin@cygwin.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).