Date: Tue, 29 Sep 2015 18:19:54 +0100 From: Stephen Roome <Steve.Roome@bristol.ac.uk> To: freebsd-questions@freebsd.org Subject: Serial comms with espruino - stty? Message-ID: <CAA8gwy9sxZxrfi2q2MCNCaj2vP1wqUJip15g7%2BdFoGvbjAaydg@mail.gmail.com> In-Reply-To: <CAA8gwy_FRaOsrJpCTL8nrLBg1pWZYJBTKnQvDBVQ-B==6CN5vQ@mail.gmail.com> References: <CAA8gwy--oAmAnNsKyQenSqYF=3opcht%2BwA0pb7KtRRocp_%2B1_Q@mail.gmail.com> <CAA8gwy_w_ctskmdpiC%2B-cJn9UV9MK7t1CVcZ5KQ5XHhguiK3PQ@mail.gmail.com> <CAA8gwy-qUWTerGKoNhC=ouw0ObOO-sj4gLDXyLEbsQnjk_K1jg@mail.gmail.com> <CAA8gwy_FRaOsrJpCTL8nrLBg1pWZYJBTKnQvDBVQ-B==6CN5vQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi folks, I've recently been given a tiny ARM chip on a usb board - an Espruino Pico. Unfortunately, I'm not having a lot of luck in FreeBSD with this. In Linux and OSX the device attaches as /dev/tty.something and /dev/cusomething and ... screen /dev/tty.something works great on both. In FreeBSD however it attaches via umodem as... /dev/cuaU0 /dev/ttyU0 /dev/cuaU0.lock /dev/cuaU0.init /dev/ttyU0.init and /dev/ttyU0.lock screen /dev/ttuU0 sort of works however umodem or ucom or tty or something seems to buffer the last character of input or output. i.e. typing is hard work. screen is effectively always exactly one keypress behind. I've played with the stty settings (which I think, but I'm not certain, that I have to make to /dev/ttyU0.init for them to actually be applied - hey, is this documented somewhere ???) but to no avail. Does anyone know how I affect the umodem/ucom/tty settings to make comms over screen usable. I get the same with cu as well. For bonus points. .. If after that you can suggest how to get chrome.serial javascript functions to work I'll be even more grateful - but that seems a long shot. I'm assuming this is all my fault of course. Ta Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA8gwy9sxZxrfi2q2MCNCaj2vP1wqUJip15g7%2BdFoGvbjAaydg>