From owner-freebsd-questions@freebsd.org Tue Sep 29 17:19:56 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 24F2DA0C2B8 for ; Tue, 29 Sep 2015 17:19:56 +0000 (UTC) (envelope-from aesbr@bristol.ac.uk) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4FE71249 for ; Tue, 29 Sep 2015 17:19:55 +0000 (UTC) (envelope-from aesbr@bristol.ac.uk) Received: by iofb144 with SMTP id b144so18644515iof.1 for ; Tue, 29 Sep 2015 10:19:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bristol.ac.uk; s=google; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=PzVeUvrDcZ3/19vaUUxkVBkt2ElV4ul79ULlgtyOqHY=; b=EiSUNqq/xDwzKosCrIPVVUw8121Gn1JPyQNyo0Do7ur3NbgFYLlQwfVUZNqqlrONlb t85vngxXgub0BGXPVWIk1D5VLfI7DkkEZA2IWF+mWDTtjmc+AzDszrRZtZyEtTN/pLw8 NjeOg+zWXbB59Ar7ZmOvJRN+vUHIeBNFAMU0c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=PzVeUvrDcZ3/19vaUUxkVBkt2ElV4ul79ULlgtyOqHY=; b=gQK0pzrJrOnqPYBnW4+pdbVAgm07iq/fkIHh3rYBH6PwVGdAaDnZ5LTRi7hCVKAMWs dGomrseyieFwC36GYZLHZINfuQnxDRAB6+bLZbSNboPcbFtjE9fBuLt/BHfKCP98BBX0 5mD0Ai6idO6WQt1iCpWHh1BErHkAuQJ2dlFJ7oge0w8nZ8zTYNbT4/NBLrG87+Nbgenw ym7g3GKYsLmQ5mnMsoJ/R8xQFDV9grKgfNOylpULcjOIaQFH1HB+oqfLM+JKp/qVfIhf xsLGR58XSVCgvYtwAEr2GuXQO40g1ZxI7+6IIs1GexZVFskA4cbwI8Bb5P8Xe9PsrWNl Cazg== X-Gm-Message-State: ALoCoQkN9qSmyzmTTt8miCGOCnBTPRL2P+mHHLWuR12DP2QA4Z3P5egwjVgCUgkvFYEQPOubMZkE MIME-Version: 1.0 X-Received: by 10.107.10.203 with SMTP id 72mr25255567iok.117.1443547195005; Tue, 29 Sep 2015 10:19:55 -0700 (PDT) Reply-To: Steve.Roome@bristol.ac.uk Received: by 10.36.57.85 with HTTP; Tue, 29 Sep 2015 10:19:54 -0700 (PDT) Received: by 10.36.57.85 with HTTP; Tue, 29 Sep 2015 10:19:54 -0700 (PDT) In-Reply-To: References: Date: Tue, 29 Sep 2015 18:19:54 +0100 Message-ID: Subject: Serial comms with espruino - stty? From: Stephen Roome To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Tue, 29 Sep 2015 17:19:56 -0000 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