In the Jetson AGX Orin development kit hardware layout below, USB micro-B port(J26 and mark 9) is used to see the boot logs through minicom.
When we check in the Jetson AGX Orin Carrier Board Block Diagram, 4 signals from SOM to USB micro B are connected(highlighted in red color). If we connect only “UART3_DEBUG” signal from SOM to USB micro-B connector then we can get the boot logs?
Hi,
We suggest use micro-B to type-A cable to connect AGX Orin developer kit to x86 host PC to the uart log. Other kinds of connection may not work properly.
I am confused as to whether you are talking about the behavior of the dev kit, or if you are using it as an example for building a custom carrier board. That USB-OTG connector, when a micro-B USB plugs into it, is by default set up for serial devices to appear to the host PC. One is for serial console. No host mode is available due to wiring.
For the custom carrier board. We are planning to use only UART3_DEBUG line from the SOM module. As per the “Jetson AGX Carrier Board block diagram” four signals (NVJTAG/DBG_SEL, UART2, UART3_DEBUG and I2C2) signals are connected to USB Micro B connector through Level Shifters and Debug MCU. In the custom carrier bord the intention of using micro USB B port is to get the boot logs and login to the board after bootup. So using only UART3_DEBUG to micro USB B connector is fine?
.
I don’t know the details, but essentially it would be correct that only one port is used for boot logs, and that the port for this uses only device mode. Someone else would have to verify details (but a USB type-B is fine).
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
