Date: Wed, 12 Oct 2022 14:26:56 +1030 From: "Daniel O'Connor" <darius@dons.net.au> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-usb@freebsd.org Subject: Re: Failed control transfer Message-ID: <8F91F636-2536-4405-90B0-8F1DA3C417CE@dons.net.au> In-Reply-To: <a4ea1837-dcb8-0338-b3b3-f32147732b5e@selasky.org> References: <7FF9CB5C-26B0-4DBA-B7E4-80DBF50A80BB@dons.net.au> <7e1de023-094f-4247-146d-9e8f498ae0e7@selasky.org> <DF88E7EE-B986-4853-9CF8-9047B084F03C@dons.net.au> <577bcb8a-b2ab-8d38-b657-0d085a8a2df6@selasky.org> <C11CE896-7F67-4C2D-8194-22D4C218DD91@dons.net.au> <75c25972-e998-c7f2-578f-31a364554fd7@selasky.org> <a4ea1837-dcb8-0338-b3b3-f32147732b5e@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 11 Oct 2022, at 22:12, Hans Petter Selasky <hps@selasky.org> wrote: >> What does "usbdump -i usbusX -f Y -s 65536 -vvv" say? >=20 > Maybe you should trace using usbdump from the start of attachment. Sorry to waste your time I just realised my mistake.. When it was connected to Linux/MacOS a tool automatically ran which = silently patched(!) the Cypress FX2 code (it reset the CPU but didn't = cause a reconnection so I didn't notice). After the code is patched the serial number command works (but xc3sprog = blows up because it changes the protocol) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8F91F636-2536-4405-90B0-8F1DA3C417CE>