(3) typc_print:
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
(4) serial_print:
[ 5.232075] nvpps c6a0000.nvpps: nvpps cdev(507:0)
[ 5.232096] nvpps c6a0000.nvpps: TSC config ptx 0x113
[ 5.286309] tegra-qspi 3270000.spi: Adding to iommu group 5
[ 5.291611] spi-nor spi0.0: mx25u51279g (65536 Kbytes)
No known UDC device found
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-5.1#
(5) maybe need to modify dts, do you have the answer to the question ?
the dts as below:
88 ports {
89 usb2-0 {
90 mode = “otg”;
91 usb-role-switch;
92 status = “okay”;
93 port {
94 hs_typec_p1: endpoint {
95 remote-endpoint = <&hs_ucsi_ccg_p1>;
96 };
97 };
98 };
99
100 usb2-1 {
101 mode = “host”;
102 status = “okay”;
103 port {
104 hs_typec_p0: endpoint {
105 remote-endpoint = <&hs_ucsi_ccg_p0>;
106 };
107 };
108 };
109
110 usb2-2 {
111 mode = “host”;
112 status = “okay”;
113 };
114
115 usb2-3 {
116 mode = “host”;
117 status = “okay”;
118 };
119
“bsp_kernel/hardware/nvidia/t23x/nv-public/tegra234-p3737-0000+p3701-0000.dts” 440L, 10513C
*** Please note that this reply is generated by LLM automatically ***
The issue you’re encountering appears to be related to a failed flashing process on a Jetson AGX Orin device, specifically when attempting to burn an image onto the device. The error messages and logs provided suggest several potential issues, including problems with the device tree configuration, USB connectivity, and the flashing process itself. Let’s break down the key points and potential solutions:
Flashing Process Issue: The command you’re using to flash the device is quite detailed, involving the use of sudo for root privileges, specifying the ROOTFS_AB partition, and indicating the use of an NVMe device (nvme0n1p1). The repeated “Waiting for target to bootup” messages suggest that the flashing process is not completing successfully, and the device is not booting up as expected.
Device Tree Configuration: The provided device tree snippet (dts) shows configurations for USB ports (usb2_0, usb2_1, usb2_2, usb2_3) with their respective modes (otg, host) and statuses. The mention of potentially needing to modify the dts suggests that there might be an issue with how the USB ports are configured, which could be affecting the flashing process or the device’s ability to boot correctly.
USB Connectivity Issues: The error messages “bash: cannot set terminal process group” and “bash: no job control in this shell” indicate issues with the shell environment, possibly related to the USB connection or the way the device is interacting with the host machine. These could be symptoms of a deeper problem, such as incorrect device tree configurations affecting USB functionality.
Comparison with Similar Issues: Looking at the context provided, there are several instances of issues related to booting, device tree configurations, and USB connectivity across different Jetson models (Orin, Xavier, Nano). For example, the “Rin Nano 8GB Developer Kit - Realtek PHY MAC Address Change Causes Boot Issue” suggests that changes to hardware configurations can lead to boot issues, similar to what you’re experiencing. The “Custom board PMIC” and “Lan7430 issue for custom board Jetson Orin Nano” threads imply that custom board configurations and device tree settings can significantly impact the functionality and bootability of the device.
Potential Solutions:
Verify Device Tree Configuration: Ensure that the device tree configuration (dts) is correct and properly set up for your specific hardware configuration. Pay particular attention to the USB port configurations, as they seem to be a point of contention.
Check USB Connectivity: Confirm that the USB connection between the host machine and the Jetson AGX Orin is stable and functioning correctly. Try using a different USB port or cable if possible.
Reflash the Device: If the flashing process is failing, try reflashing the device with the correct image and ensure that all prerequisites (such as unlocking the bootloader, if necessary) are met.
Consult Documentation and Forums: Given the complexity of the issue and the specificity of the device and configurations involved, consulting the official NVIDIA documentation and forums where similar issues are discussed can provide valuable insights and potential solutions.
In conclusion, the issue you’re facing seems to involve a combination of factors related to the flashing process, device tree configuration, and possibly USB connectivity. Addressing these areas through careful configuration, verification of the setup, and potentially seeking guidance from official resources or community forums should help in resolving the problem.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
hellow,
(1) is AGX Orin devkit;
(2) download source code to compile ,from Jetson Linux | NVIDIA Developer
(3) maybe typec is not in device mode; because don’t exist /sys/class/usb_role/usb2-0-role-switch
(4) log in attachment; serial_print.txt (76.3 KB) typec_print.txt (294.4 KB)
I think AGX Orin devkit should be flashed successfully with SDK manager w/o any config modification.
Please just use SDK manager to flash the devkit directly.