So I ref [Link] to set usb2-0 mode from otg to host, and rebuild the .dtb to put the line to /boot/extlinux/extlinux.conf on target. use below command to check:
Software
(1)extlinux:
OTG $ ls /proc/device-tree/bus@0/padctl@a808680000/ports/usb2-0
Hi,
We have validated the approach on AGX Thor developer kit and it works. Did you try it on developer kit?
And we have a patch to enable otg on AGX Thor developer kit: Jetson AGX Thor FAQ
You may test it on developer kit as a reference design. Since you don’t use same PD controller as our developer kit, it cannot be directly applied to the custom board.
Sorry for misunderstanding on Hardware part, our custom board uses the same Cypress PD controller as the devkit, but we use a Micro-fit connector for power input.
I’ve verified the patch on the developer kit. It works initially but is unstable; the USB device eventually stops being detected after multiple replugs.
Hi,
Could you share what USB device is used? A pendriver or USB camera? What is the failure rate out of 10 trials? We can test the same on AGX Thor developer kit.
What is the failure rate out of 10 trials?
→ It’s quite low; only 3 out of 10 tests passed.
My testing procedure is: once the USB device is detected, I unplug it and swap it for a USB Hub to check for a stable connection. Then, I switch back to the original device. A trial is only considered a “pass” if the device is successfully re-detected after these swaps.
How can I check the status of the I2C_CCG_SCL and I2C_CCG_SDA lines? Can these be accessed or controlled via software? I suspect there is an issue with the signal switching mechanism.
Hi,
On AGX Thor developer kit, the pins are controlled by PD controller. It cannot be controlled via software. PD controller shall set correct status to run in host or device mode.
Hi,
We tested on AGX Thor developer kit J81 port connecting type C to A adapter+ Transcend 128GB JetFlash920 USB disk. It passes plug/unplug test for 40 trials. Don’t hit the failure.
Do you have other C to A adapter or USB disk for a try? Probably the failure is specific to the USB disk.
Regarding your suggestion, I have already tested with a native USB Type-C drive Kingston datatraveler max 256GB, but the stability issues persist. I also tried swapping different USB disks using a Type-C to A adapter, and the results were the same—it remains unstable.
Furthermore, I would like to follow up on my previous query regarding the interrupt status. Could you please verify the state of interrupts = <TEGRA264_MAIN_GPIO(Z, 5) IRQ_TYPE_LEVEL_LOW>; on your side?
Specifically, could you check it using the same method I did: sudo cat /sys/kernel/debug/gpio | grep PZ.05 Lastly, during your 40 trials, did you observe any “ucsi_ccg 2-0008: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-5)” error messages in the dmesg? On my setup, this error appears frequently during plug/unplug events.