> This is a question for people using Linux to develop for RIOT-OS.
> What program do you use to connect to the (USB) serial? picocom?
> minicom? miniterm? grabserial? something else?
I sometimes use minicom, because it's generally available and can send BREAK,
but I usually wind up using screen, because then I can run it on my serial
console server, and connect to it from multiple places.
I also use rtty, but it isn't as useable because USB serial devices don't
> I'm looking for a program that can automatically reconnect to the USB
> serial after the RIOT board does a restart. So far I only found that
> minicom will do that, but not automatically.
> I like the three others much better because I can more easily log the
> output. However, when the board resets, it loses the connection.
Are you using a board with an FTDI chip attached to a serial console?
Or one with a built-in USB?
It's a SODAQ board (basically an Arduino Zero compatible board) with
a SAMD21 that has onchip USB.
There is also the interaction with the
flashing process, which sometimes needsd the USB connection.
I'd like to convince the minicom and screen guys to do some kind of back-off
when the flasher asks.
(This is also kinda a call for dual TTY devices that showed up in SunOS
4,AIX,etc. back in the 1990s that let UUCP run well before we had mgetty.)
Well, minicom is kinda old, from the modem era. The thing I don't like
about it that it really tries to emulate a terminal. With a curses-style
popup when the tty device is gone. You can hit enter and it reconnects.
Picocom, miniterm (Python pyserial) and grabserial is what I like. I can
pipe (or tee) the output in a file.
But like I said, if my program hits a watchdog reset, it reboots, and my
USB connection is gone. In my startup I want to print the reset cause
to know what was going on.
In the past I was using one of the UARTs of the SAMD21. In a sense that
was much easier.
I hate to say it, but it seems on Windows there is a solution (they tell
That, by itself, bothers me too