Alex Taradov

Capture running or not is a purely logical thing, it does not affect the transceiver state, so it should not matter. Order of device connection also should not matter. Something...

Although no, there are SOF and Get Device Descriptor requests from the host. The device does not respond, so it is not the sniffer that can't see the frames. You...

I have no idea what it could be. I doubt it is the transceiver. If anything, it would be the comparators. I have not done significant testing with hubs, since...

Also, RTS5411 sees to support USB3.2 Gen1, so it is not just UBS2.0 hub. And in either case, none of them should care, since we are clearly only using USB2.0...

Another possible factor - the cables. I just tried to experiment with hubs. The only type of hubs I have is this https://www.amazon.com/gp/product/B00JX1ZS5O . I chained two of them just...

And this is something to keep in mind too - with the sniffer you have double the cable length. Even if the sniffer is ideal and does not cause additional...

Impossible to tell without having proper measurement equipment and understanding what any of the issues are. And I don't have such equipment. I don't consider it to be a serious...

Most likely you have some issues with the USB PHY IC and it is not producing 60 MHz clock. Up to the test point it would matter, but the test...

Do you see 60 MHz as well? If not, then yes, something is wrong with the USB PHY. It should start producing 60 MHz clock for the FPGA. Without it...

And the most obvious thing to check that is it soldered in a correct orientation.