Support for Jetson AGX Orin Developer Kit 32GB: not boot OS and can’t connect to NVIDIA SDK Manager

Hi team,

I have 1pcs Jetson AGX Orin Developer Kit 32GB, I checked and found some Issues as follows. Hope to receive your advice and support.

=====Issue 1:

When I power on, the DS2 LED is on, however the AGX Orin Dev Kit does not boot the operating system, and the AGX Orin Dev Kit fan does not work.

When I connect the USB Type-C port to NVIDIA SDK Manager, but SDK Manager does not recognize AGX Orin Dev Kit.

=> Question 1: Do you know what could be the reasons for this problem? Can you guide me which blocks I need to check to find the cause of this problem?

======Issue 2: 1V Block

I performed 2 resistance measurements in the 1V Block:

  • I measured the resistance between TP108 pin and GND and got a resistance of 477.6R

  • I measured the resistance between {Pin 6, Pin 7 (SW pin)} and {Pin 4, Pin 5 (GND pin)} of GS7303ACTD-R chip and it has a resistance of 275.7R

=> Question 2: Is the GS7303ACTD-R chip in 1V Block broken?
If this chip is broken, what do I need to do to order a replacement GS7303ACTD-R chip?
Or is there a chip that can replace this chip?

=====Issue 3: Type C (J40) Block

I check PI3DBS12212AZBSEX_EOL chip (U138):
=> B0+ short C0+
=> B0- short C0-
=> B1+ short C1+
=> B1- short C1-

=> Question 3: Is the PI3DBS12212AZBSEX_EOL chip in Type C (J40) Block broken?
If this chip is broken, what do I need to do to be able to order a PI3DBS12212AZBSEX_EOL chip to replace it?
Or is there a chip that can replace this chip?

=====Issue 4: Type C (J39) Block

I check PI3DBS12212AZBSEX_EOL chip (U137):
=> B0+ short C0+
=> B0- short C0-
=> B1+ short C1+
=> B1- short C1-

=> Question 4: Is the PI3DBS12212AZBSEX_EOL chip in Type C (J39) Block broken?
If this chip is broken, what do I need to do to order a PI3DBS12212AZBSEX_EOL chip to replace it?
Or is there a chip that can replace this chip?

Hi phamxuanvi93,

What’s the Jetpack version in use for AGX Orin devkit?

Could your devkit boot before?

We have to check the serial console log for any boot issue.
Please refer to the following instruction to capture that from micro-USB port.
NVIDIA Jetson Orin AGX - In Board - Getting in Board - Serial Console

I would suggest press REC button and plug the power cable to enter into force recovery state to check if SDK manager can recognize it through USB-C port.

1 Like

What is the history of this dev kit. Was it working previously? Is it a new dev kit?
Are you using a native Linux host PC/machine? If operating on a virtual machine there could be issues with IOs/USB ports ownership.

1 Like

Hi @KevinFFF ,
Hi @sgursal ,

=> “What’s the Jetpack version in use for AGX Orin devkit?”
Response: Jetpack 5.1.2 version that I use for this AGX Orin Dev Kit.

=> “Could your devkit boot before?” and “What is the history of this dev kit. Was it working previously? Is it a new dev kit?”
Response:
This AGX Orin Dev Kit has been in use for a while. Previously the Jetson AGX Orin Dev Kit was working fine, but suddenly the AGX Orin Dev Kit fan stopped working and the AGX Orin Dev Kit stopped working.
I unplugged and plugged in the power to AGX Orin but AGX Orin Dev Kit does not boot the operating system, and when using force recovery mode SDK Manager does not recognize AGX Orin Dev Kit.

=> “enter into force recovery state to check if SDK manager can recognize it through USB-C port.”
Response:
Prepare the device for test: I used (the new Jetson AGX Orin Developer Kit power adapter) and (a good usb type C cable) to perform the test.

I tested AGX Orin Dev Kit 32GB as follows:

video test: https://youtu.be/1NOQgaJqNk4

=> “check the serial console log for any boot issue”
Response:
I tested serial console log on AGX Orin Dev Kit 32GB as follows:

  • step 1: I connecting microUSB port on AGX Orin Dev Kit to a PC running Ubuntu using a micro-USB cable.

  • step 2: Plug in a DC power supply’s USB Type-C plug into the USB Type-C port above the DC jack. When the DS2 LED is on, I run the command line below:
    $ ls -al /dev/ttyACM*

  • step 3: I turn on minicom with the command line below:
    $ sudo minicom -D /dev/ttyACM0 -8 -b 115200

  • step 4: However when I unplug and plug the power back in to the AGX Orin Dev Kit there is no data on minicom
    video test: https://youtu.be/jrTxbdr-I2g

=> “Are you using a native Linux host PC/machine? If operating on a virtual machine there could be issues with IOs/USB ports ownership.”
Response: Can you describe it in more detail for me?

Hi @KevinFFF ,
Hi @sgursal ,
I performed the test as follows:

=> Test 1: AGX Orin module of Dev Kit A + carrier board of Dev Kit B => work OK, check the serial console log - have data output on /dev/ttyACM0 port.
=> Test 2: AGX Orin module of Dev Kit B + carrier board of Dev Kit A => NOT boot OS, can’t connect to NVIDIA SDK Manager and check the serial console log - NO data output on /dev/ttyACM0 port.

Do you have schematics and assembly drawing or any documentation of AGX Orin module, so I can check which part of AGX Orin module has problem and repair it?

Looking forward to hearing from you soon. Thanks!

Do you run any application which may cause the boot issue?

We want to know if you are using standalone Ubuntu as host PC. Or are you using VM for Ubuntu?

After you’ve enabled the serial interface for serial console log, you can just press RESET button to check if there’s any log output.

Could you run lsusb from your host to check if the devkit can be recognized?

Do you mean that the issue comes from AGX Orin module of B?

Hi @KevinFFF ,

=> “Do you run any application which may cause the boot issue?”
Response: I will ask in more detail what applications my customers have run on the AGX Orin Dev Kit, and get back to you with the information.

=> “We want to know if you are using standalone Ubuntu as host PC. Or are you using VM for Ubuntu?”
Response: I use standalone Ubuntu as host PC. I do not use VM for Ubuntu. Since we need a host PC with Ubuntu installed directly on it to test and flash OS for different Jetson versions, we do not use VM for Ubuntu.

=> “After you’ve enabled the serial interface for serial console log, you can just press RESET button to check if there’s any log output.”
“Could you run lsusb from your host to check if the devkit can be recognized?”
Response: I will try again as you instructed by pressing the RESET button to see what the result is.

=> “Do you mean that the issue comes from AGX Orin module of B?”
Response: Based on the results of Test 1 and Test 2, I now suspect that the AGX Orin module of Dev Kit B has a problem. Do you think I need to test anything else to verify this suspicion?
If there is an error problem with AGX Orin module of Dev Kit B, Can you tell me what could be the reasons why the Jetson Module B doesn’t work? Let me discuss with my customer.
Do you have schematics and assembly drawing or any documentation of AGX Orin module, so I can check which part of AGX Orin module has problem and repair it?

Looking forward to hearing from you soon. Thanks!

If you have did cross-validation and confirmed the following items, we would suggest you perform RMA for the AGX Orin module from devkit-B.

  1. no serial console log output
  2. can not be recognized through lsusb in forced-recovery state

Hi @KevinFFF ,

=> “Do you run any application which may cause the boot issue?”
Response: my customer uses yolo8 for image processing application on AGX Orin Dev Kit.

=> “After you’ve enabled the serial interface for serial console log, you can just press RESET button to check if there’s any log output.”
=> “recognized through lsusb in forced-recovery state”
Response:

I performed the test as follows:

=> Test 1: AGX Orin module of Dev Kit A + carrier board of Dev Kit B => press RESET button, check the serial console log - have data output on /dev/ttyACM0 port
=> Test 2: AGX Orin module of Dev Kit B + carrier board of Dev Kit A => press RESET button, check the serial console log - NO data output on /dev/ttyACM0 port.
=> Test 3: AGX Orin module of Dev Kit A + carrier board of Dev Kit B => in forced-recovery state, run command line $ sudo lsusb has the following results:

=> Test 4: AGX Orin module of Dev Kit B + carrier board of Dev Kit A => in forced-recovery state, run command line $ sudo lsusb has the following results:

=> “we would suggest you perform RMA for the AGX Orin module from devkit-B.”
Response: Can you please guide me in detail how to do it, or give me contact information so I can receive instructions to perform RMA?.
If there are repair costs, can you tell me what the estimated cost of repairs is? I tell my customer.

Looking forward to hearing from you soon. Thanks!

It seems you’ve performed A-B-A swap test, and it shows that the AGX Orin module from Dev Kit B is broken.

Please refer to What if I need an RMA (Return Material Authorization)? to perform RMA process.

Hi @KevinFFF ,
Thank you for your support!