From nobody Thu Mar 23 21:03:42 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 UTF8SMTP id 4PjHrL5d64z40L4g for ; Thu, 23 Mar 2023 21:03:46 +0000 (UTC) (envelope-from freebsd-usb@dino.sk) Received: from cm0.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (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 UTF8SMTPS id 4PjHrL21zgz4BG4 for ; Thu, 23 Mar 2023 21:03:46 +0000 (UTC) (envelope-from freebsd-usb@dino.sk) Authentication-Results: mx1.freebsd.org; none Received: from zeta.dino.sk ([84.245.95.254]) (AUTH: LOGIN milan, TLS: TLSv1.3,256bits,TLS_AES_256_GCM_SHA384) by cm0.netlabit.sk with ESMTPSA id 0000000000B05CBA.00000000641CBEAF.00014174; Thu, 23 Mar 2023 22:03:43 +0100 Date: Thu, 23 Mar 2023 22:03:42 +0100 From: Milan Obuch To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org Subject: Re: Which serial driver for the development board? Message-ID: <20230323220342.76a6c37a@zeta.dino.sk> In-Reply-To: <27d8da5f-f2f8-af1d-8300-4d7ccb35744b@selasky.org> References: <20230323130418.5ba9954f@zeta.dino.sk> <88f9b5a4-1e7f-ea9e-e170-888a8713a060@selasky.org> <20230323170028.186d77ed@zeta.dino.sk> <27d8da5f-f2f8-af1d-8300-4d7ccb35744b@selasky.org> X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; amd64-portbld-freebsd13.1) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4PjHrL21zgz4BG4 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:5578, ipnet:84.245.64.0/18, country:SK] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, 23 Mar 2023 17:19:46 +0100 Hans Petter Selasky wrote: > 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. [ snip ] > >>> 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 > If you mean issuing # usbconfig -d ugen0.5 set_config 0 it does not help. Descriptors are the same after this command: # 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 I think there is some bug in device's firmware, but as MacOS was able to communicate with it out-of-the-box, no configuration necessary on MAC, there should be a way... Regards, Milan