Achim Gratz NexGo.DE> writes:
> I've created cygport files for both and picocom works just fine. Have yet
> to test minicom, but I think it'll work as well.
For my purposes minicom works, albeit with more overhead then picocom.
However there are a few problems like popping up the help screen ac
Corinna Vinschen writes:
> It doesn't have to stay this way, you know?
Yes I know. But at the moment I need to get some other work done plus…
> Ideally by somebody who knows how this dreaded Windows serial line API
> works...
…I am unfortunately not somebody like that.
Regards,
Achim.
--
+<[
Achim Gratz nexgo.de> writes:
> Meanwhile I think my best option, based on how I plan to interact with
> the hardware, would be picocom. Will try both picocom and minicom some
> time next week (hopefully).
I've created cygport files for both and picocom works just fine. Have yet
to test minicom
On Jun 10 10:42, Helmut Karlowski wrote:
> ---
> > Ideally by somebody who knows how this dreaded Windows serial line API
> > works...
>
> Wouldn't someting like this work:
>
> term=$'\r'
> l=
> while true; do read -N1 c
> [ "$c" == $'\4' ] && break
---
> Ideally by somebody who knows how this dreaded Windows serial line API
> works...
Wouldn't someting like this work:
term=$'\r'
l=
while true; do read -N1 c
[ "$c" == $'\4' ] && break
[ "$c" == $term ] && { echo "<$l>"; l=; } || l="$l$c"
done
On Jun 10 00:07, Achim Gratz wrote:
> Warren Young writes:
> > Unfortunately, it is a GUI program, which seems to go against the OP’s
> > actual wish, which is for a command line program.
>
> Right. Plus it doesn't have the translation capabilities that I needed
> in this particular case.
>
>
Warren Young writes:
>> I've used minicom on Linux for similar hardware. It also doesn't have
>> the translation capabilities needed
>
> minicom -s ->
> Screen and keyboard ->
> Character conversion
> Add linefeed
> Add carriage return
>
> What more did you want?
OK, looks like I
Warren Young wrote at 12:34 -0600 on Jun 9, 2016:
> On Jun 7, 2016, at 6:05 PM, Brian Inglis
> 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
On Jun 9, 2016, at 4:07 PM, Achim Gratz wrote:
>
> Warren Young writes:
>> If the OP can stand a curses terminal program (as opposed to a purely
>> bytestream oriented program like cu or direct /dev/tty* access) then
>> I’d suggest minicom.
>
> I've used minicom on Linux for similar hardware. It
Warren Young writes:
> Unfortunately, it is a GUI program, which seems to go against the OP’s actual
> wish, which is for a command line program.
Right. Plus it doesn't have the translation capabilities that I needed
in this particular case.
> If the OP can stand a curses terminal program (as
On Jun 8, 2016, at 9:04 AM, Andrey Repin wrote:
>
>> Brian Inglis writes:
>
>>> Maybe try Windows putty non-TCP/IP serial I/O?
>
>> I was specifically trying to avoid a Windows program.
>
> putty is not a Windows program.
PuTTY started out as a Windows-only program and is certainly still best
On Jun 7, 2016, at 6:05 PM, Brian Inglis
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
$ c
Greetings, Achim Gratz!
> Brian Inglis writes:
>> cu is the normal Unixy way of using a remote USB->serial line, but I can't
>> find it in Cygwin packages searching for \, and cu spews too many hits.
> Yup, that was one of the first alternatives I've looked for.
>> Maybe try Windows putty non-T
Brian Inglis writes:
> cu is the normal Unixy way of using a remote USB->serial line, but I can't
> find it in Cygwin packages searching for \, and cu spews too many hits.
Yup, that was one of the first alternatives I've looked for.
> Maybe try Windows putty non-TCP/IP serial I/O?
I was specif
Achim Gratz NexGo.DE> writes:
> I'm trying to connect to a development board via a (USB) serial line. It's
> using CR rather than NL for line ends, so I was hoping for stty to set that
> up so I could use screen to communicate with that board. No such joy on
> Cygwin since the cooked modes are n
For the record, this is what I ended up with:
---8<---
#!/bin/dash
cleanup () {
/bin/kill $cpid
exec 6<&- 6>&-
/bin/stty $stty
}
if [ $# -ne 2 ] ; then
echo "Usage: ${0##*/} "
exit 1
fi
tty=$1; shift
baud=$1; shift
stty=$(/bin/stty -g)
/bin/stty -icanon -echo
Achim Gratz NexGo.DE> writes:
> Is there some other terminal emulator/program that would let me use this
> board anyway via Cygwin until Cygwin learns cooked mode for terminals?
The following script does almost what I want, save for some ickyness with
the echo of the input that I might attempt to
I'm trying to connect to a development board via a (USB) serial line. It's
using CR rather than NL for line ends, so I was hoping for stty to set that
up so I could use screen to communicate with that board. No such joy on
Cygwin since the cooked modes are not implemented apparently. Connecting
18 matches
Mail list logo
