From owner-freebsd-usb@freebsd.org Wed Jan 13 09:02:28 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 0B668A81F45 for ; Wed, 13 Jan 2016 09:02:28 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9463613D2 for ; Wed, 13 Jan 2016 09:02:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 0AAEB1FE024; Wed, 13 Jan 2016 10:02:23 +0100 (CET) Subject: Re: CP2102 UART adapter not attaching To: Mark Johnston References: <20160110040732.GA2606@raichu> <56936A9D.2060209@selasky.org> <20160113060434.GA2434@raichu> <5695EBE0.8020501@selasky.org> <20160113061722.GB2434@raichu> <569602F1.70401@selasky.org> <20160113163008.GA1974@raichu> Cc: freebsd-usb@freebsd.org From: Hans Petter Selasky Message-ID: <56961325.1000901@selasky.org> Date: Wed, 13 Jan 2016 10:04:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20160113163008.GA1974@raichu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 09:02:28 -0000 On 01/13/16 17:30, Mark Johnston wrote: > 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 > Try to set: hw.usb.xhci.xhci_port_route=0 or hw.usb.xhci.xhci_port_route=0xffffffff In /boot/loader.conf Any difference? --HPS