From owner-freebsd-questions@freebsd.org Wed Sep 30 19:16:18 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C2B7A0C283 for ; Wed, 30 Sep 2015 19:16:18 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D094C104E for ; Wed, 30 Sep 2015 19:16:17 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id t8UJG8jq073224 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 30 Sep 2015 13:16:08 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id t8UJG7Ga073209; Wed, 30 Sep 2015 13:16:08 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 30 Sep 2015 13:16:07 -0600 (MDT) From: Warren Block To: Stephen Roome cc: freebsd-questions@freebsd.org Subject: Re: Serial comms with espruino - stty? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 30 Sep 2015 13:16:08 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2015 19:16:18 -0000 On Tue, 29 Sep 2015, Stephen Roome wrote: > 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. There is the "Serial Port Configuration" section of the serial chapter of the Handbook: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serial.html#serial-hw-config Of course it all depends on how a particular cable is wired. I got thoroughly sick of RS232 many years back, swore never to wire yet another serial cable, and began avoiding it. But every time I think it's dead forever, it comes back. Most lately, I'm trying to figure out why pasting text to a NodeMCU board acts like hardware handshaking does not work and loses pasted characters while a line is processed. Thirty years ago, having to set an EOL delay was not unexpected. Today, well, at least it can be trusted to be the same old fight to get it to work.