Orin NX failure to boot from external storage on custom carrier board

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
,
1

I have designed and build a custom carrier board for use with the Orin NX 8gb. It was designed around the Orin Nano Dev Kit, the only major difference is that it is configured to output over HDMI. As of right now I am running into an issue booting from a NVMe drive. I am new to working with the Jetson products so im sure its probably something fairly simple im missing.

This is the flash command im using to flash the device:
sudo ./tools/kernel_flash/l4t_intrd_flash.sh --external-device nvme0n1p1 \ -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c ./bootloader/generic/cfg/flash_t234_qspi.xml" \ --showlogs --network usb0 voyavox_desk_x1 internal

I am using Jetpack 6.0 R36.3 and generated the bootloader/kernel/rootfs files following the R36.3 linux dev guide. I am also using Ubuntu 20.04.6 LTS to build/flash. I do not get anything to the display but I can see the logs from the debug port. Im not sure if this is an issue/misconfiguration with the DTB files or something wrong with the flash process. It looks like it is failing to mount the NVMe drive during boot. I’ve attached the logs I get from the debug port during boot.

debug_output.txt (25.1 KB)

2

Some points from your log.

  1. Each line got truncated. Please resize your terminal and dump them again.

  2. Jetson’s pcie driver is kernel module but not inside kernel image anymore. I don’t see any pcie driver log in your log (though it is not completed). Without pcie driver, your nvme drive won’t be loaded up…

  3. The pcie driver is missing most likely due to your RT patch…

3

Thanks for the quick reply. I verified that my rootfs was configured incorrectly and I believe I have fixed it. The device now boots to the NVMe drive, but I still have no output from the display.

I ran this command with this result:

xrandr
Can't open display

I’ve attached a new dump from the debug console, hopefully this one copied correctly.
debug_output.txt (72.4 KB)

4

In my (limited) experience, xrandr will basically never output anything useful if the user hasn’t logged in on the desktop, as far as I can tell.

I’ve had better luck looking at X11 logs themselves. e.g. /var/log/Xorg.0.log on my machine has messages like this:

[  2281.498] (WW) NVIDIA: No DRM device: No direct render devices found.
[  2281.503] (II) NVIDIA(0): NVIDIA GPU Orin (nvgpu) (GA10B) at SoC (GPU-0)
[  2281.503] (--) NVIDIA(0): Memory: 15895848 kBytes
[  2281.504] (--) NVIDIA(0): VideoBIOS:
[  2281.507] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS PB277 (DFP-0): connected
[  2281.507] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS PB277 (DFP-0): Internal DisplayPort
[  2281.507] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS PB277 (DFP-0): 2380.0 MHz maximum pixel clock
[  2281.507] (--) NVIDIA(GPU-0):
[  2281.511] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2281.511] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2281.511] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2281.511] (--) NVIDIA(GPU-0):

^ That shows me that Linux found a my monitor (ASUS PB277) is connected.

Something you might try is to restart the display manager (GDM) and immediately watch all system logs from journalctl. Try running

$ sudo -s
# systemctl restart display-manager && journalctl --follow
5

Since the device is booting up now and just display not show, please file a new topic for your display.

6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.