Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Aug 2020 10:02:21 -0700
From:      bob prohaska <fbsd@www.zefox.net>
To:        Hans Petter Selasky <hps@selasky.org>, bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-arm@freebsd.org, freebsd-current@freebsd.org
Subject:   Re: Strange USB loop
Message-ID:  <20200827170221.GA24247@www.zefox.net>
In-Reply-To: <20200825182916.GA14015@www.zefox.net>
References:  <20200824163736.GA9845@www.zefox.net> <42038cfd-425c-c5cd-d3de-d3cace1ecd89@selasky.org> <20200825050304.GA11333@www.zefox.net> <8be06d6f-9837-cde6-1878-a25e84656d84@selasky.org> <20200825182916.GA14015@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 25, 2020 at 11:29:16AM -0700, bob prohaska wrote:

> With a _different_ FT232 plugged in it also came up normally.
> 
> Both are thought to be genuine, but they are of different age
> and produce different recognition messages:
> 
> The FT232 that causes trouble reports
> ugen1.4: <FTDI TTL232R-3V3> at usbus1
> uftdi0 on uhub1
> uftdi0: <TTL232R-3V3> on usbus1
> 
> The one that seems to work is newer and reports
> ugen1.4: <FTDI FT232R USB UART> at usbus1
> uftdi0 on uhub1
> uftdi0: <FT232R USB UART> on usbus1
> 
> On balance I think the new kernel is better-behaved. Beyond that
> I'm at a loss. If you can suggest other things to try please do.
> 
>  

This morning I found on the console a message:
uftdi0: at uhub1, port 3, addr 4 (disconnected)
uftdi0: detached

but, usbconfig -a repored
ugen1.4: <FTDI FT232R USB UART> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA)

and lsusb says
Bus /dev/usb Device /dev/ugen1.4: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC

The FT232 is plugged directly into the Pi. This the newer, supposedly
functional, ft232...

Unplugging and replugging put on the console
ugen1.4: <FTDI FT232R USB UART> at usbus1 (disconnected)
uftdi0: at uhub1, port 3, addr 4 (disconnected)
uftdi0: detached
ugen1.4: <FTDI FT232R USB UART> at usbus1
uftdi0 on uhub1
uftdi0: <FT232R USB UART> on usbus1

But it still can't connect to the serial port of the correspondent host,
which is up and running. 

Meanwhile, the FT232 which appeared faulty is working fine overnight
on RaspiOS Buster. 

Thanks for reading, and any suggestions....

bob prohaska




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200827170221.GA24247>