Unable to boot and unable to flash via SDK Manager

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hey,

I’ve had this Xavier NX developer kit for over a year now and have been using it on and off for testing purposes. It has worked fine up until last month when it all of a sudden stopped booting. I didn’t do anything different, had the same SD card boot drive that worked before in it, and it just won’t boot at all. I am getting the green power light with no changes to that, unplugging everything didn’t work, different SD cards didn’t work, re-flashing the SD cards didn’t work, flashing via SDK manager didn’t work, and trying different JetPack versions didn’t work either. If I leave it plugged in, the heatsink gets hot but the fan never spins. My keyboard also won’t light up like it usually does.

I just tried a different SD card and flashed JetPack 5.1 on it which initially gave me the following minicom output:

[0000.024] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet lev.
[0000.033] I> MB1 (prd-version: 1.5.1.7-t194-41334769-98030a79)              
[0000.038] I> Boot-mode: Coldboot                                            
[0000.041] I> Chip revision : A02P                                           
[0000.044] I> Bootrom patch version : 15 (correctly patched)                 
[0000.049] I> ATE fuse revision : 0x200                                      
[0000.053] I> Ram repair fuse : 0x0                                          
[0000.056] I> Ram Code : 0x0                                                 
[0000.058] I> rst_source : 0x0                                               
[0000.061] I> rst_level : 0x0                                                
[0000.065] I> Boot-device: QSPI                                              
[0000.067] I> Qspi flash params source = brbct
[0000.071] I> Qspi using bpmp-dma                                               
[0000.156] I> Reset to recovery mode0000000000000000000000000000000000000000000

That didn’t do anything so then I tried going into recovery mode which ends up not showing anything but if I jump the reset headers, I get this output:

??
[0000.024] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.033] I> MB1 (prd-version: 1.5.1.7-t194-41334769-98030a79)
[0000.038] I> Boot-mode: Coldboot
[0000.041] I> Chip revision : A02P
[0000.044] I> Bootrom patch version : 15 (correctly patched)
[0000.049] I> ATE fuse revision : 0x200
[0000.053] I> Ram repair fuse : 0x0
[0000.056] I> Ram Code : 0x0
[0000.058] I> rst_source : 0x0
[0000.061] I> rst_level : 0x0
[0000.065] I> Boot-device: QSPI
[0000.067] I> Qspi flash params source = brbct
[0000.071] I> Qspi using bpmp-dma
[0000.074] I> Qspi clock source : pllp
[0000.078] I> QSPI Flash Size = 32 MB
[0000.081] I> Qspi initialized successfully
[0000.085] E> No bootable slot found
[0000.088] E> LOADER: Failed to get slot for boot chain from SMD.
[0000.094] E> LOADER: Failed to get storage info for binary 0 from loader.
[0000.100] E> LOADER: Failed to get info for binary 0 from loader.
[0000.106] C> LOADER: Could not read binary 0.
[0000.110] C> Fail to load mb1-bct bin
[0000.114] E> Task 24 failed (err: 0x1d540102)
[0000.118] E> Top caller module: LOADER, error module: AB_BOOTCTRL, reason: 0x02, aux_info: 0x01
[0000.126] I> MB1(1.5.1.7-t194-41334769-98030a79) BIT boot status dump :
0000000000011111111110111000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0000.156] I> Reset to recovery mode

I know that this SD card was working before flashing JP 5.1 to it as well.

When I try to use the SDK Manager, I get an error every time that it fails to run dpkg. This happens regardless of the version.

Could this be a hardware issue? Please let me know if there’s any more information I can provide.

Regards

3

Hi, ryanmsmith251,

Are you using Xavier NX devkit with SD module?

Could you help to provide the log from SDKM?

Are you using standalone Ubuntu18.04 or 20.04 as your host PC?

How do you flash the board? (the exact command you run)
Please provide the flash log for further check.

4

Hey KevinFFF,

Are you using Xavier NX devkit with SD module?

I apologize, I have been using SD card and microSD card interchangeably. I’m using the microSD card slot on the bottom of the daughter board as sort of shown by point 1 here

Could you help to provide the log from SDKM?

Yeah, sorry I should’ve included that the first time. I put the full dump into pastebin here. It looks like everything is good up until this point:

08:55:51.148 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Using rootfs directory of: /home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs
08:55:51.152 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Installing extlinux.conf into /boot/extlinux in target rootfs
08:55:51.152 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: /home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/nv_tegra/nv-apply-debs.sh
08:55:51.155 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Root file system directory is /home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs
08:55:51.156 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Copying public debian packages to rootfs
08:55:51.266 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Skipping installation of nvidia-l4t-dgpu-config_35.2.1-20230124153320_arm64.deb for dgpu ...
08:55:51.450 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Start L4T BSP package installation
08:55:51.450 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: QEMU binary is not available, looking for QEMU from host system
08:55:51.450 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Found /usr/bin/qemu-aarch64-static
08:55:51.450 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Installing QEMU binary in rootfs
08:55:51.456 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: /home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs /home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra
08:55:51.460 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Installing BSP Debian packages in /home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs
08:55:51.478 - error: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: chroot: failed to run command 'dpkg': Exec format error
08:55:51.478 - info: Event: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS - error is: chroot: failed to run command 'dpkg': Exec format error
08:55:51.478 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: [ Package Install Finished with Error ]
08:55:51.478 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: [host] [ 4.67 GB used. Disk Avail: 862.52 GB ]
08:55:51.479 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: [ NV_L4T_FILE_SYSTEM_AND_OS_COMP Install took 2m39s ]
08:55:51.480 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: 
08:55:51.480 - error: command error code: 11
08:55:51.480 - info: Event: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS - error code is: 1011
08:55:51.480 - error: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: command terminated with error
08:55:51.480 - info: Event: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS - error is: command terminated with error
08:55:51.484 - info: Event: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS - install ended - failure
08:55:51.485 - info: Summary: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Installation failed.

I am also seeing some failures with getcwd but it claims to be completing successfully:

08:52:28.928 - info: exec_command: sudo dpkg --audit
08:52:28.930 - error: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
08:52:28.930 - info: Event: undefined - error is: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
08:52:28.930 - warn: Failed to get component from group data map for undefined
08:52:28.963 - info: 
08:52:28.963 - info: command finished successfully

Are you using standalone Ubuntu18.04 or 20.04 as your host PC?

No, I don’t have a PC that is running native Ubuntu. I was using Windows 11 with WSL2 running Ubuntu 20.04 and following the instructions here for using the SDKManager with WSL2. I may be able to switch one of my old laptops, if necessary, but that could take some time.

How do you flash the board? (the exact command you run)
Please provide the flash log for further check.

I’m using the GUI, not the CLI so I assume that sdkm_replay.txt has what you’re asking for. The sdkm_replay.txt is:

=== SDK Manager Replay at 2023-02-14 08:44:06.467 ===

2023-02-14 08:45:16.415 - 
cd '/home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs/' ; \
'/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter' \
-a='install' \
-c=<key1> \
-i='NV_L4T_FILE_SYSTEM_AND_OS_COMP' \
-v='35.2' \
-l='/home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs/' \
-L='/home/rsmith/.nvsdkm/logs/JetPack_5.1_Linux' \
-p='1751' \
-t='JETSON_XAVIER_NX_TARGETS' \
-e='/home/rsmith/Downloads/nvidia/sdkm_downloads/Tegra_Linux_Sample-Root-Filesystem_R35.2.1_aarch64.tbz2'

2023-02-14 08:52:30.043 - 
cd '/home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/' ; \
'/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter' \
-a='install' \
-c=<key2> \
-i='NV_L4T_DRIVERS' \
-v='35.2' \
-l='/home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/' \
-L='/home/rsmith/.nvsdkm/logs/JetPack_5.1_Linux' \
-p='1751' \
-t='JETSON_XAVIER_NX_TARGETS' \
-e='/home/rsmith/Downloads/nvidia/sdkm_downloads/Jetson_Linux_R35.2.1_aarch64.tbz2'

2023-02-14 08:53:11.695 - 
cd '/home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs/' ; \
'/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter' \
-a='install' \
-c=<key3> \
-i='NV_L4T_FILE_SYSTEM_AND_OS_COMP' \
-v='35.2' \
-l='/home/rsmith/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs/' \
-L='/home/rsmith/.nvsdkm/logs/JetPack_5.1_Linux' \
-p='1751' \
-t='JETSON_XAVIER_NX_TARGETS' \
-e='/home/rsmith/Downloads/nvidia/sdkm_downloads/Tegra_Linux_Sample-Root-Filesystem_R35.2.1_aarch64.tbz2'

For readability key1, key2, and key3 represent what appear to be API keys that I have removed. I have also put the line breaks in where I though made sense, those were not there in the logs.

5

Here is a zipfile of the logs exported after that failed run: SDKM_logs_JetPack_5.1_Linux_for_Jetson_Xavier_NX_modules_2023-02-14_08-52-22.zip (56.6 KB)

Here is also a zipfile of all SDKM logs using the Export Debug Logs button: SDKM_logs_2023-02-14_11-12-22.zip (125.1 KB)

6

Sorry, could you help to get a standalone Ubuntu and create dual boot on your host PC for SDK Manager?
VM/docker/WSL for Ubuntu may cause unstable connection from host PC to the board because there are several reboot at flashing process.

From your log, it seems dpkg issue in WSL.
I would suggest you to get a native Ubuntu as your host for SDK Manager.

7

I will add that unless your knowledge is sufficient to add loopback support to WSL2, then even if you solved the USB issues with a VM, that it would still fail.

8

Kevin, thank you. I don’t know why flashing the microSD card wasn’t working anymore but SDKM on native Ubuntu worked and now I’ll have a PC with Ubuntu for the future.

linuxdev, that’s an interesting point. Yeah I would never have known about loopback support but it makes sense that WSL2 wouldn’t have worked anyway. I was skeptical about using WSL2 but thought I’d give it a try.

10

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