bentprong / ocp_xavier

Xavier NIC3 Test & Monitoring Board firmware.
Apache License 2.0
0 stars 0 forks source link

USB connection/disconnection and reset issue #15

Open bentprong opened 1 year ago

bentprong commented 1 year ago

TTF and Xavier share the same processor and code base. However, they act differently when connected to a Windows laptop. Xavier is not as "reliable" as TTF and requires special handling. For example, you have to close TeraTerm when power cycling for Xavier but not for TTF. Note that the behavior of TTF and Xavier is the same and without issue when connecting to a Mac. The behavior of both is also affected by which USB port on the Windows computer is used. USB-A works better than USB-C. This point is not relevant to Macs. Purpose of this issue is a) to note this behavior and b) to request an in-depth review of the hardware designs of both to see what the differences are. Xavier is now more usable than before but there are still some strange behaviors particularly in TeraTerm. Assigning to both Jon and Rick B for coverage. I'm labeling this as a hardware issue because of the identical code base of both projects. That could be incorrect so please review and update this issue with any findings. Thanks.

bentprong commented 1 year ago

Also, the reset button does not restart the USB connection Xavier.

bentprong commented 1 year ago

One obvious difference is that in Xavier, the USB connectors A4, A9, B4 and B9 are tied to USB_5V but those pins are NC on TTF.

rickbrandwein commented 1 year ago

U43 can be de-popped if the USB isn't used for power.

rickbrandwein commented 1 year ago

The Reset button asserts the RESET pin on the micro. Does it need a HW change to reset the USB connection?

rickbrandwein commented 1 year ago

I have removed all of the circuitry related to the regulator attached to the USB port. The reliability of the connection was not changed.
Tera Term may be the problem. It tends to hang up while trying to connect. Pressing and holding the reset button releases Tera Term. Also found that the Com port sometimes gets an "unrecognized" error and then the card changes com port.