From owner-freebsd-usb@FreeBSD.ORG Fri Jun 21 21:06:08 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6B4BCAFD for ; Fri, 21 Jun 2013 21:06:08 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 2ADB2162E for ; Fri, 21 Jun 2013 21:06:07 +0000 (UTC) Received: from mail.bitfrost.no (mail.bitfrost.no [46.29.221.36]) by mta.bitpro.no (Postfix) with ESMTP id 0BEE67A121; Fri, 21 Jun 2013 23:06:07 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at bitfrost.no Received: from laptop015.hselasky.homeunix.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hanspetter) by mail.bitfrost.no (Postfix) with ESMTPSA id 29BE320683; Fri, 21 Jun 2013 23:06:05 +0200 (CEST) Message-ID: <51C4C07B.7040507@bitfrost.no> Date: Fri, 21 Jun 2013 23:07:07 +0200 From: Hans Petter Selasky Organization: Bitfrost A/S MIME-Version: 1.0 To: Mike Meyer Subject: Re: Issues 179505 References: <20130621195542.7d9103859f9edcbd1bd8b4d8@getmail.no> <20130621200326.ba4a8fd0e4b300b8b77c836e@getmail.no> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jun 2013 21:06:08 -0000 On 06/21/13 20:17, Mike Meyer wrote: > Sorry 'bout the extra emphasis there. > > Anyway, the problem is not *simply* the sketch code. It could be > something in the Arduino bootloader violating a USB spec that Linux > doesn't care about and FreeBSD does. But mucking about with the user > code on the Arudino (i.e. - sketches) doesn't change anything: I get > the same behavior whether it's running a trivial Blink demo (pretty > much no libraries used at all) or a complete interactive shell: > > It works as expected when connected to Linux running on a VBox VM, > with the umodem device always being present. > > If I don't connect it to the VM, the umodem device appears when the > board is plugged in or reset, then disappears before the sketch starts > running. Hi, I think I have one of these devices at work. I can have a look if I have time next week. Possibly the Arduino needs a fix. Look for so-called spurious VBUS pullup toggling in the software of the Arduino. --HPS