Kees Bakker <k...@ijzerbout.nl> wrote:
    >> Which board?  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.

So you lose your USB device each time it reboots.

    >> 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.

Yes, it reconnects.  The rest don't.
Either fix the rest to reconnect ...
Getting the USB to enumerate consistently is what bugs me.
It requires a unique ID in the USB, which most of the devices haven't
bothered to provision :-(

    > 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.

Sounds like ten lines of python.

    > I hate to say it, but it seems on Windows there is a solution (they
    > tell me).  That, by itself, bothers me too :-)

Windows GUI programs mostly can't pipe stuff.
The ones that can, are usually just using the Linux ABI now.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     m...@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

Attachment: signature.asc
Description: PGP signature

_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Reply via email to