Date: Wed, 2 Sep 2020 16:33:19 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Strange USB loop Message-ID: <20200902233319.GA67239@www.zefox.net> In-Reply-To: <20200827170221.GA24247@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> <20200827170221.GA24247@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 27, 2020 at 10:02:21AM -0700, bob prohaska wrote: > 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 > > With the system updated to r364900 both FT232 devices seem to be working. The machine boots from a USB disk successfully with mouse, keyboard and FT232 connected at powerup. Thanks for your help, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200902233319.GA67239>