Issue with Booting Jetson AGX Orin 32GB Module after Flashing with SDK Manager and Jetpack

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
, ,
1

Hello,

We built a custom card and procured a Jetson AGX Orin 32GB Module, Model-P3701, flashed with SDK Manager version 1.9.3 and Jetpack 5.1.2. The installation was completed successfully, but the board isn’t booting. We also attempted flashing within the L4T package using the command “sudo ./flash jetson-agx-orin-devkit mmcblk0p1” While it displayed the message “flash successfully completed,” the board still didn’t boot.

Could you please confirm if the flashing procedure is correct or if there are modifications needed in the flash commands?

Regards,
Parashuram

3

Hi,

are you sure your custom board is compatible with DevKits from NVIDIA?
Usually you need to create a separate config file containing the customized device tree.
Both of SDK Manager and jetson-agx-orin-devkit are meant to be used with DevKits but not custom boards.

4

Thank you for your response. I’m not sure about its compatibility. Could you kindly provide guidance on creating a distinct config file for custom carrier card? Is there any available documentation for this process? Your assistance would be highly valued.

Regards,
Parashuram

5

If you are building your own carrier board, then it’s like the first document you should read:
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html

6

Yes, I have gone through adaptation and bring up document. Our design is same with the reference schematic from the devkit, with no alterations to the pin configuration in the DP ports. While some other interfaces might not function optimally on our custom board, we do anticipate that, at the very least, the DP display should come up properly.

Regards
Parashuram

7

Then are you still able to login via serial console?
Please show the booting log, contents of /var/log/Xorg.0.log and xrandr here.

8

Console logs are accessible through the debug MCU. Currently, we haven’t programmed the MCU due to the unavailability of the debugger. We’ve successfully programmed the Power button MCU and can access the button as expected.
We are currently unable to access the debug MCU via the console. Are there alternative methods to access the console apart from the debug MCU? Additionally, I’m interested in whether Nvidia will supply a reference code for the ATSAMD21G16B MCU as used in the devkit.

Regards,
Parashuram

9

I think we won’t be able to proceed before you can get the debug console to be done.

10

Thank you for your response. I’ve made a rework on the carrier card, and now I can access the log. Please refer to the attached logs. However, I’m still facing an issue where the display DP port is not coming up. The design for the DP port in our carrier design is the same as the one we referred to for the AGX Orin dev kit.
xrandr
Can’t open display
Xorg log:
Xor.log (1.2 KB)
Flash log:
flash.log (83.3 KB)
UART log:
uart.log (87.5 KB)

11

Do you get anything from dmesg when you hot-plug the DP cable?