Re: Which serial driver for the development board?

From: Hans Petter Selasky <hps_at_selasky.org>
Date: Fri, 24 Mar 2023 08:43:29 UTC 
On 3/23/23 22:03, Milan Obuch wrote:
> # usbconfig -d ugen0.5 dump_all_desc
> ugen0.5: <vendor 0x1d50 product 0x6141> at usbus0, cfg=255 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
> 
>    bLength = 0x0012
>    bDescriptorType = 0x0001
>    bcdUSB = 0x0200
>    bDeviceClass = 0x0002  <Communication device>
>    bDeviceSubClass = 0x0000
>    bDeviceProtocol = 0x0000
>    bMaxPacketSize0 = 0x0020
>    idVendor = 0x1d50
>    idProduct = 0x6141
>    bcdDevice = 0x0000
>    iManufacturer = 0x0000  <no string>
>    iProduct = 0x0000  <no string>
>    iSerialNumber = 0x0000  <no string>
>    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.

Hi,

You may need to run "usbdump" before plugging the device to figure out 
exactly what goes wrong.

cfg=255 means there is a permanent issue using the USB control endpoint 
data channel. Yes - likely a bug in the firmware that it does not handle 
error conditions properly.

--HPS