Hi,
We are using ORIN NX 8GB module, the carrier card is our own design, I connected a USB3.0 interface to the TYPE-A connector, this connector does not connect the USB2.0 signal, only the USB3.0 signal.
When I inserted the USB flash drive of USB3.0 interface, the board was powered on again, but the system could not recognize the device after startup. After entering the reboot command, the device still could not be recognized after startup.
But this USB flash drive can be identified by the system after hot swap, may I ask why this is, “hot swap can identify the device” this phenomenon shows that the signal quality of USB3.0 is normal, may I ask what I should do?
I checked the system power-on log and did not find any USB error message.
Hi,
Why can’t the VBUS power supply always exist? The VBUS POWER supply of the onboard card is controlled by the POWER ON pin of the ORIN NX 8GB module. After I input the reboot command, I tested the POWER ON pin, which was always at a high level.
I looked at the device tree file and found that this USB3.0 interface is bound to another set of USB2.0 interfaces. Should I set this USB3.0 interface as a separate port?
Hi,
The ORIN NX module has 3 USB3.2 interfaces and 3 USB2.0 interfaces (including USB0). We connect USB0 and a USB3.0 interface to the TYPE-A connector as one port. I asked whether USB0 interface can be set to HOST mode before. You replied that if USB0 is set to HOST mode, “initrd flash will have problem.” So we can only use this USB separately, with USB2.0 (USB0) as the dedicated interface for recovery mode and USB3.0 as the independent HOST interface. Is there any problem with this?
Thanks.
When USB0 is operating in OTG mode, do I use the USB0_VBUS_DET pin only to determine whether the external device is HOST or device? Can we modify the software to do that?
In the process of use, there are only two cases: HOST and Device.
Hi,
By looking at the schematic file “P3768_A04_Concept_schematics.pdf” provided by NVIDIA, I did not find this ID pin. I found a set of I2C interfaces that seem to be used to obtain ids.
That is because p3768 A04 designs the port as a type C.
We have separate type C controller from other vendor there to control the data role/power role. And the communication between jetson usb driver and that controller is through i2c.