From nobody Thu Mar 23 16:19:46 2023 X-Original-To: freebsd-usb@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pj9Xd1QrXz41Wdl for ; Thu, 23 Mar 2023 16:19:45 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pj9Xc6XfDz3FWZ for ; Thu, 23 Mar 2023 16:19:44 +0000 (UTC) (envelope-from hps@selasky.org) Authentication-Results: mx1.freebsd.org; none Received: from [10.36.2.154] (unknown [46.212.121.255]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 5BF34260114; Thu, 23 Mar 2023 17:19:37 +0100 (CET) Message-ID: <27d8da5f-f2f8-af1d-8300-4d7ccb35744b@selasky.org> Date: Thu, 23 Mar 2023 17:19:46 +0100 List-Id: FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-usb List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: Which serial driver for the development board? Content-Language: en-US To: Milan Obuch , freebsd-usb@freebsd.org References: <20230323130418.5ba9954f@zeta.dino.sk> <88f9b5a4-1e7f-ea9e-e170-888a8713a060@selasky.org> <20230323170028.186d77ed@zeta.dino.sk> From: Hans Petter Selasky In-Reply-To: <20230323170028.186d77ed@zeta.dino.sk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Pj9Xc6XfDz3FWZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 3/23/23 17:00, Milan Obuch wrote: > On Thu, 23 Mar 2023 15:05:02 +0100 > Hans Petter Selasky wrote: > >> On 3/23/23 13:04, Milan Obuch wrote: >>> Hi, >>> >>> I just received Sparkfun QuickLogic board. After connecting it via >>> USB, I found following device: >>> >>> # usbconfig -d ugen0.5 dump_all_desc >>> ugen0.5: at usbus0, cfg=255 md=HOST >>> spd=FULL (12Mbps) pwr=ON (100mA) >>> >>> bLength = 0x0012 >>> bDescriptorType = 0x0001 >>> bcdUSB = 0x0200 >>> bDeviceClass = 0x0002 >>> bDeviceSubClass = 0x0000 >>> bDeviceProtocol = 0x0000 >>> bMaxPacketSize0 = 0x0020 >>> idVendor = 0x1d50 >>> idProduct = 0x6141 >>> bcdDevice = 0x0000 >>> iManufacturer = 0x0000 >>> iProduct = 0x0000 >>> iSerialNumber = 0x0000 >>> bNumConfigurations = 0x0001 >>> >>> Searching for VID and PID did not get me anything. Trying any of our >>> USB serial driver did not create any device. How can I connect to >>> this device? It should be some serial port because that's what >>> Sparkfun page says... Any hint? >>> >>> Regards, >>> Milan >>> >>> N. B. I was able to connect to this device using my Mac: >>> >>> # cu -l /dev/tty.usbmodem1411 >>> Connected. >>> ############## >>> >>> >>> >>> Hello world!! >>> >>> #******************* >>> Command Line Interface >>> App SW Version: qorc-sdk/qt_apps/qt_helloworldsw >>> #******************* >>> >> >> Hi! >> >> Did you try to dump the configuration descriptor? >> >> Maybe umodemX can handle it ... >> > > I forgot to write I have all available serial drivers loaded, i.e. in > kldstat output > > 54 1 0xffffffff81ae9000 23a0 umodem.ko > 55 7 0xffffffff81aec000 4d10 ucom.ko > 56 1 0xffffffff81af1000 22a0 uchcom.ko > 57 1 0xffffffff81af4000 2200 ucycom.ko > 58 1 0xffffffff81af7000 21e0 umoscom.ko > 59 1 0xffffffff81afa000 2aa0 uplcom.ko > 60 1 0xffffffff81afd000 32e0 uslcom.ko > 61 1 0xffffffff81b01000 2260 uvscom.ko > > This is from a 13.1-STABLE system. > > What you mean by configuration descriptor? Is it this: > > # usbconfig -d ugen0.5 dump_all_config_desc > ugen0.5: at usbus0, cfg=255 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) > > # usbconfig -d ugen0.5 dump_curr_config_desc > ugen0.5: at usbus0, cfg=255 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) > > There is just this, nothing more. Could some usbdump help to identify > the issue? I have no experience with this, also no idea how an initial > device discovery could be catch with usbdump :( > > Regards, > Milan Hi, cfg=255 means there is an error to set the configuration index. Try to use usbconfig to set config index 0 again? Maybe it just works? --HPS