From owner-freebsd-usb@freebsd.org Wed Jan 13 08:30:13 2016 Return-Path: Delivered-To: freebsd-usb@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 B6289A81055 for ; Wed, 13 Jan 2016 08:30:13 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (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 8EA491244 for ; Wed, 13 Jan 2016 08:30:13 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pa0-x232.google.com with SMTP id uo6so338607635pac.1 for ; Wed, 13 Jan 2016 00:30:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=+0G96i0Hzxd0Jr5KI5+Slds79TrBx2J0EFpZ+hkNqCE=; b=qdsrPQj5ePXZtILEUgzmnjJLqnaSNyEal5CFNNiKrsnsAjwCNyZ48BH+VQ4nSTe6E6 Dk9YgyvlnoA+HrG4kIGenIMHGLEGx94QyMJBrF9RIkfotL69m/PRALfEAZMl2NFtrjYq LLpwnrfNH+ilmE0F6YrTBlbPQZ/H2SALfYK3HWLDcDVVxVWFX07JVmZv+WeGOA7tC6pt yQB2EMBKvTqSGhrYcgT/KjiE66/fl5WoCCZj4doa+4ffJbnxzY1C4VGTs8tpNaeugW1T G86Yx0INFeNbtgqfLkPE9HQ741xfN1yGwl36932nmOxrTy3xDcKoAmacF8lQ2PEe5uKP KU+w== X-Received: by 10.66.100.228 with SMTP id fb4mr191855347pab.84.1452673813051; Wed, 13 Jan 2016 00:30:13 -0800 (PST) Received: from raichu ([104.232.114.184]) by smtp.gmail.com with ESMTPSA id 75sm645683pfj.20.2016.01.13.00.30.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Jan 2016 00:30:12 -0800 (PST) Date: Wed, 13 Jan 2016 08:30:08 -0800 From: Mark Johnston To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org Subject: Re: CP2102 UART adapter not attaching Message-ID: <20160113163008.GA1974@raichu> References: <20160110040732.GA2606@raichu> <56936A9D.2060209@selasky.org> <20160113060434.GA2434@raichu> <5695EBE0.8020501@selasky.org> <20160113061722.GB2434@raichu> <569602F1.70401@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <569602F1.70401@selasky.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2016 08:30:13 -0000 On Wed, Jan 13, 2016 at 08:55:29AM +0100, Hans Petter Selasky wrote: > On 01/13/16 07:17, Mark Johnston wrote: > > On Wed, Jan 13, 2016 at 07:17:04AM +0100, Hans Petter Selasky wrote: > >> On 01/13/16 07:04, Mark Johnston wrote: > >>> On Mon, Jan 11, 2016 at 09:41:01AM +0100, Hans Petter Selasky wrote: > >>>> On 01/10/16 05:07, Mark Johnston wrote: > >>>>> Hi, > >>>>> > >>>>> I have the module listed here: > >>>>> http://www.amazon.com/KEDSUM%C2%AE-CP2102-Module-Download-Converter/dp/B009T2ZR6W > >>>>> > >>>>> Under Windows 8 it works perfectly, but on FreeBSD-CURRENT I get: > >>>>> > >>>>> usb_alloc_device: set address 3 failed (USB_ERR_STALLED, ignored) > >>>>> usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED > >>>>> usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) > >>>>> usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED > >>>>> usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) > >>>>> usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED > >>>>> usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) > >>>>> usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED > >>>>> usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) > >>>>> usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED > >>>>> ugen1.3: at usbus1 (disconnected) > >>>>> uhub_reattach_port: could not allocate new device > >>>>> > >>>>> It looks like this device should be handled by uslcom(4), but it looks > >>>>> like we can't even get the device descriptor. How can I go about > >>>>> debugging this? > >>>> > >>>> Hi, > >>>> > >>>> What does "usbconfig" say about your USB controllers? > >>>> > >>>> Did you try to connect through an external USB HUB? > >>> > >>> No, I don't have one handy. usbconfig shows: > >>> > >>> ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) > >>> ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) > >>> ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) > >>> > >> > >> Could you show what "pciconf -lv" says about xhci0. Sometimes you need > >> to set a special routing register before some XHCI controllers work! > > > > xhci0@pci0:0:20:0: class=0x0c0330 card=0x84ca1043 chip=0x1e318086 rev=0x04 hdr=0x00 > > vendor = 'Intel Corporation' > > device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' > > class = serial bus > > subclass = USB > > > > I'm plugging the module into the first EHCI controller though - it's a > > USB 2.0 device. > > > > In src/sys/dev/usb/controller/xhci_pci.c you can try adding the PCI chip > ID to the following list: It looks like 0x1e318086 is already in the list? > > case 0x0f358086: /* BayTrail */ > case 0x9c318086: /* Panther Point */ > case 0x1e318086: /* Panther Point */ > case 0x8c318086: /* Lynx Point */ > case 0x8cb18086: /* Wildcat Point */ > case 0x9cb18086: /* Broadwell Mobile Integrated */ > /* > * On Intel chipsets, reroute ports from EHCI to XHCI > * controller and use a different IMOD value. > */ > > > --HPS