Jetson Nano Stuck on NVIDIA logo screen when booting

I am using the Jetson Nano Developer Kit for a JetRacer project. The issue I am facing is that the Jetson Nano is stuck on the NVIDIA Logo screen when it boots. And when Im trying to flash using SDKManager on WSL2 I get an error.

The steps I took:

  • flashed * [Pre-Built image based on Jetpack4.5 (jetrace.zip - Google Drive) on 64Gb microSD using balenaEtcher.
  • Jetson Nano stuck on Logo Screen
  • Based on similar issues/topics decided to use SDKManager
  • Installed it on WSL, because I dont have an extra host pc with Linux/Ubuntu available.
    Update
  • Windows laptop does recognize Jetson via USB to micro-USB (I used a wrong cable)
  • I set up SDKManager and tried to install JetPack4.6.3 onto the Jetson Nano, but i get an error flash Jetson Nano - flash: Depends on failed component
  • Above error was related to chroot: failed to run command ‘dpkg’: Exec format error
  • Was able to fix that error by installing fresh WSL2 ubuntu-18.04 image and then running
sudo apt install qemu-user-static

wget https://github.com/qemu/qemu/raw/master/scripts/qemu-binfmt-conf.sh

chmod +x qemu-binfmt-conf.sh

sudo ./qemu-binfmt-conf.sh --qemu-path /usr/bin --qemu-suffix -static --debian

sudo update-binfmts --import qemu-aarch64
(update-binfmts: warning: qemu-aarch64 already enabled in kernel.)

sudo update-binfmts \
 --package qemu-user \
 --install qemu-aarch64 /usr/bin/qemu-aarch64-static \
 --magic '\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00' \
 --mask '\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff'
(update-binfmts: warning: current package is qemu-user, but binary format already installed by qemu-aarch64)

sudo update-binfmts --import qemu-aarch64

sudo update-binfmts --import qemu-arm

sudo update-binfmts --import qemu-armeb

  • But now when I use SDKManager to flash the Jetson Nano I get a notification showing
    Nvdia USB Device was removed (APX)
  • And error flash: --- Error: Reading board information failed
  • flashing logs below

17:25:38 DEBUG: Flash Jetson Nano - flash: using adapter to install NV_L4T_FLASH_NANO_WITH_OS_IMAGE_COMP@JETSON_NANO_TARGETS to /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS
17:25:39 INFO: Flash Jetson Nano - flash: [host] [ Disk Avail on Partition : 0.00 B ]
17:25:39 INFO: Flash Jetson Nano - flash: Installing component 'Flash Jetson Nano' (NV_L4T_FLASH_NANO_WITH_OS_IMAGE_COMP)
17:25:39 INFO: Flash Jetson Nano - flash: change working directory to /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra
17:25:39 INFO: Flash Jetson Nano - flash: [ Component Install Started ]
17:25:39 INFO: Flash Jetson Nano - flash: current working directory is /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra
17:25:39 INFO: Flash Jetson Nano - flash: exec_command [host]:
17:25:39 INFO: Flash Jetson Nano - flash: **********************
17:25:39 INFO: Flash Jetson Nano - flash: set -e
17:25:39 INFO: Flash Jetson Nano - flash: unset LC_ALL
17:25:39 INFO: Flash Jetson Nano - flash: echo sudo ./nvsdkmanager_flash.sh
17:25:39 INFO: Flash Jetson Nano - flash: sudo ./nvsdkmanager_flash.sh
17:25:39 INFO: Flash Jetson Nano - flash: sleep 20
17:25:39 INFO: Flash Jetson Nano - flash: **********************
17:25:39 INFO: Flash Jetson Nano - flash: exec_command: /tmp/tmp_NV_L4T_FLASH_NANO_WITH_OS_IMAGE_COMP.jetson.sh
17:25:39 INFO: Flash Jetson Nano - flash: sudo ./nvsdkmanager_flash.sh
17:25:39 INFO: Flash Jetson Nano - flash: Defaulting to autoflash
17:25:39 INFO: Flash Jetson Nano - flash: *** Checking ONLINE mode ... OK.
17:25:39 INFO: Flash Jetson Nano - flash: *** Checking target board connection ... 1 connections found.
17:25:39 INFO: Flash Jetson Nano - flash: *** Reading ECID ... FUSELEVEL=fuselevel_production hwchipid=0x21 bootauth=
17:25:39 INFO: Flash Jetson Nano - flash: *** Reading EEPROM ... "/home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py" --chip 0x21 --applet "/home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/nvtboot_recovery.bin" --skipuid --cmd "dump eeprom boardinfo cvm.bin; dump eeprom baseinfo bbd.bin"
17:25:39 INFO: Flash Jetson Nano - flash: Welcome to Tegra Flash
17:25:39 INFO: Flash Jetson Nano - flash: version 1.0.0
17:25:39 INFO: Flash Jetson Nano - flash: Type ? or help for help and q or quit to exit
17:25:39 INFO: Flash Jetson Nano - flash: Use ! to execute system commands
17:25:39 INFO: Flash Jetson Nano - flash:
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0087 ] Generating RCM messages
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0132 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0145 ] RCM 0 is saved as rcm_0.rcm
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0161 ] RCM 1 is saved as rcm_1.rcm
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0161 ] List of rcm files are saved in rcm_list.xml
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0161 ]
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0161 ] Signing RCM messages
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0204 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0215 ] Assuming zero filled SBK key
17:25:39 INFO: Flash Jetson Nano - flash: [ 0.0330 ]
17:25:40 INFO: Flash Jetson Nano - flash: [ 1.1302 ] dump EEPROM info
17:25:40 INFO: Flash Jetson Nano - flash: [ 1.1336 ] tegrarcm --oem platformdetails eeprom /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/cvm.bin
17:25:40 INFO: Flash Jetson Nano - flash: [ 1.1347 ] Applet version 00.01.0000
17:25:40 INFO: Flash Jetson Nano - flash: [ 1.1541 ] Saved platform info in /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/cvm.bin
17:25:40 INFO: Flash Jetson Nano - flash: [ 1.2504 ]
17:25:40 INFO: Flash Jetson Nano - flash: [ 1.2528 ] tegrarcm --reboot recovery
17:25:40 INFO: Flash Jetson Nano - flash: [ 1.2537 ] Applet version 00.01.0000
17:25:42 INFO: Flash Jetson Nano - flash: [ 1.2738 ]
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2767 ] Generating RCM messages
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2819 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2834 ] RCM 0 is saved as rcm_0.rcm
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2840 ] RCM 1 is saved as rcm_1.rcm
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2844 ] List of rcm files are saved in rcm_list.xml
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2844 ]
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2844 ] Signing RCM messages
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2868 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2878 ] Assuming zero filled SBK key
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2973 ]
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.2975 ] Copying signature to RCM mesages
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3006 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3023 ]
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3023 ] Boot Rom communication
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3034 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3042 ] BootRom is not running
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3045 ]
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3045 ] dump EEPROM info
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3067 ] tegrarcm --oem platformdetails eeprom /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3078 ] Cannot open usb device.Check if device is in recovery
17:25:42 INFO: Flash Jetson Nano - flash: [ 3.3081 ]
17:25:42 ERROR: Flash Jetson Nano - flash: Error: Return value 8
17:25:42 INFO: Flash Jetson Nano - flash: Command tegrarcm --oem platformdetails eeprom /home/jetson/nvidia/nvidia_sdk/JetPack_4.6.4_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
17:25:42 ERROR: Flash Jetson Nano - flash: --- Error: Reading board information failed.
17:25:42 ERROR: Flash Jetson Nano - flash: [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_NANO_WITH_OS_IMAGE_COMP.jetson.sh; [error]: --- Error: Reading board information failed.
17:25:42 INFO: Flash Jetson Nano - flash: [ Component Install Finished with Error ]
17:25:42 INFO: Flash Jetson Nano - flash: [host] [ Disk Avail on Partition : 0.00 B ]
17:25:42 INFO: Flash Jetson Nano - flash: [ NV_L4T_FLASH_NANO_WITH_OS_IMAGE_COMP Install took 4s ]
17:25:42 ERROR: Flash Jetson Nano - flash: command terminated with error
17:25:42 SUMMARY: Flash Jetson Nano - flash: First Error: Installation failed.

Linkes I used:

  1. https://docs.nvidia.com/sdk-manager/wsl-systems/
  2. Connect USB devices | Microsoft Learn
  3. Download and Run SDK Manager — sdk-manager 2.1.0 documentation

Hello @t.langendam,

Thanks for visiting the NVIDIA Developer forums! Someone from the Jetson team will respond as soon as they can.

Best,
Tom

In addition:

  • It looks like usbipd detaches the jetson from WSL during flashing
  • Before flashing, the usb device is shown to be connected with lsusb on WSL, but after flashing fails the usb device does not show when using lsusb on WSL
  • Device is still shown outside WSL when using usbipd list, but has to be attached again after flashing fails with usbipd attach --wsl --busid <busid>

After using the command usbipd attach --wsl -a -b <busid> SDKManager was able to flash the Jetson Nano.
The -a option made sure to constantly attach the usb device if it was detached during flashing.
The Jetson Nano booted correctly and I am able to log in to it and access it over ssh.

Problem solved

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