XavierNX with 5.0.2 stuck in boot with blinky cursor and debug USB not listed

I was using the Jetson 5.0.2 with the seed but today I installed

CUDA-x, Computer Vision, Nvidia Container Runtime and Multimedia components from Nvidia SDK Manager too, but after a reboot it goes

to just display a cursor from bootloader, Linux boot log or desktop is not running.!! I ran before I used the SDK Manager and the board goes like this, any Idea how to recover, The board usb is also not showing in lsusb now.

Its Exactly this issue

7bb34debdb1c8bccbb744cd11a167b1c6e1ebbc3_2_666x500

and gives a blinky cursor in the display tried more than 7 reboots still I am facing the issue. and its not coming out of the blinky cursor after UEFI screen.

Could you point me or help resolve the issue, thanks in advance.

Use serial console to check status first.

1 Like

I went to the recovery image I believe how to enable the usb to reflash or boot to the ubuntu now?

below It booted to

[ 5.341224] usb 2-3: new SuperSpeed Gen 1 USB device number 2 using tegra-xusb
[ 5.344604] tegradc 15200000.display: unblank
[ 5.345873] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 5.346067] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 5.352467] tegradc 15200000.display: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
[ 5.354391] tegradc 15200000.display: hdmi: get YCC quant from EDID.
[ 5.358428] extcon-disp-state external-connection:disp-state: cable 47 state 1
[ 5.358431] Extcon AUX1(HDMI) enable
[ 5.361820] usb 2-3: New USB device found, idVendor=0424, idProduct=5744, bcdDevice= 2.02
[ 5.361827] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[ 5.361848] usb 2-3: Product: USB5744
[ 5.361853] usb 2-3: Manufacturer: Microchip Tech
[ 5.364558] hub 2-3:1.0: USB hub found
[ 5.364994] hub 2-3:1.0: 5 ports detected
[ 5.371155] tegradc 15200000.display: sync windows ret = 247
[ 5.390470] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
[ 5.424982] extcon-diOTArk dirsp-ectstaoryte /mextnt/ernal-nec_wotiork is n:disp foateund on: cabl /de 5ev/3 state0ne 11p1

[ .436204] Extcon HDMI: HPD enabled
[ 5.439612] tegradc 15200000.display: hdmi: plugged
[ 5.452949] usb 1-2.2: new low-speed USB device number 4 using tegra-xusb
Finding OTA work dir on internal storage device
[ 5.491945] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
OTA work directory /mnt/ota_work is not found on /dev/mmcblk0p1
OTA work directory is not found on internal and external storage devices
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-5.0# [ 5.563661] usb 1-2.2: New USB device found, idVendor=413c, idProduct=2113, bcdDevice= 1.08
[ 5.563891] usb 1-2.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 5.564053] usb 1-2.2: Product: Dell KB216 Wired Keyboard
[ 5.570318] input: Dell KB216 Wired Keyboard as /devices/platform/3610000.xhci/usb1/1-2/1-2.2/1-2.2:1.0/0003:413C:2113.0001/input/input1
[ 5.629240] hid-generic 0003:413C:2113.0001: input,hidraw0: USB HID v1.11 Keyboard [Dell KB216 Wired Keyboard] on usb-3610000.xhci-2.2/input0
[ 5.634331] input: Dell KB216 Wired Keyboard System Control as /devices/platform/3610000.xhci/usb1/1-2/1-2.2/1-2.2:1.1/0003:413C:2113.0002/input/input2
[ 5.693183] input: Dell KB216 Wired Keyboard Consumer Control as /devices/platform/3610000.xhci/usb1/1-2/1-2.2/1-2.2:1.1/0003:413C:2113.0002/input/input3
[ 5.693738] hid-generic 0003:413C:2113.0002: input,hidraw1: USB HID v1.11 Device [Dell KB216 Wired Keyboard] on usb-3610000.xhci-2.2/input1
[ 5.772911] usb 1-2.5: new high-speed USB device number 5 using tegra-xusb
[ 5.874128] usb 1-2.5: New USB device found, idVendor=0424, idProduct=2740, bcdDevice= 2.00
[ 5.874314] usb 1-2.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5.874466] usb 1-2.5: Product: Hub Controller
[ 5.874559] usb 1-2.5: Manufacturer: Microchip Tech

bash-5.0#

Thanks,
Karthikeyan Mitran

I got the magic wire and it indeed seems to have to have booted to recovery linux

** WARNING: Test Key is used. **

L4TLauncher: Attempting Recovery Boot
EFI stub: Booting Linux Kernel…
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services and installing virtual address map…
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x4e0f0040]
[ 0.000000] Linux version 5.10.104-tegra (buildbrain@mobile-u64-5273-d7000) (aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot 2020.08) 9.3.0, GNU ld (GNU Binutils) 2.33.1) #1 SMP PREEMPT Wed Aug 10 20:17:07 PDT 2022
[ 0.000000] Machine model: NVIDIA Jetson Xavier NX Developer Kit
[ 0.000000] earlycon: tegra_comb_uart0 at MMIO32 0x000000000c168000 (options ‘’)
[ 0.000000] printk: bootconsole [tegra_comb_uart0] enabled
[ 0.000000] efi: EFI v2.70 by EDK II
[ 0.000000] efi: RTPROP=0x477587698 SMBIOS=0xc7db0000 SMBIOS 3.0=0x458a40000 MEMATTR=0x459430018 ESRT=0x45943fb98 RNG=0x47c595918 MEMRESERVE=0x459433f18
[ 0.000000] efi: seeding entropy pool
[ 0.000000] esrt: Reserving ESRT space from 0x000000045943fb98 to 0x000000045943fbd0.
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘fb1_carveout’: base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘fb1_carveout’: base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘fb2_carveout’: base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘fb2_carveout’: base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘fb3_carveout’: base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘fb3_carveout’: base 0x0000000000000000, size 0 MiB
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal [mem 0x0000000100000000-0x000000047fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000080000000-0x00000000a0973fff]
[ 0.000000] node 0: [mem 0x00000000a0974000-0x00000000a0975fff]
[ 0.000000] node 0: [mem 0x00000000a0977000-0x00000000aeffffff]
[ 0.000000] node 0: [mem 0x00000000af010000-0x00000000c7bfffff]
[ 0.000000] node 0: [mem 0x00000000c7d00000-0x00000000c7d9ffff]
[ 0.000000] node 0: [mem 0x00000000c7da0000-0x00000000c7dbffff]
[ 0.000000] node 0: [mem 0x00000000ca000000-0x00000000ca5fffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x0000000457c7ffff]
[ 0.000000] node 0: [mem 0x0000000457c80000-0x0000000457caffff]
[ 0.000000] node 0: [mem 0x0000000457cb0000-0x0000000457d7ffff]
[ 0.000000] node 0: [mem 0x0000000457d80000-0x00000004585effff]
[ 0.000000] node 0: [mem 0x00000004585f0000-0x0000000458645fff]
[ 0.000000] node 0: [mem 0x0000000458646000-0x000000045880cfff]
[ 0.000000] node 0: [mem 0x000000045880d000-0x0000000458a0ffff]
[ 0.000000] node 0: [mem 0x0000000458a10000-0x0000000458a1ffff]
[ 0.000000] node 0: [mem 0x0000000458a20000-0x0000000458a3ffff]
[ 0.000000] node 0: [mem 0x0000000458a40000-0x0000000458a4ffff]
[ 0.000000] node 0: [mem 0x0000000458a50000-0x00000004591fffff]
[ 0.000000] node 0: [mem 0x0000000459200000-0x000000045938ffff]
[ 0.000000] node 0: [mem 0x0000000459390000-0x000000045943ffff]

Please reflash your board. There is no method to recover under such situation.

The USB is not listed its an emmc board, how to reflash could you please help pointing to any article to helpout with instructions,
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
Bus 001 Device 016: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Should i force any GPIO lines to get the USB again to flash

Hi [WayneWWW]
From
(Jetson Xavier NX unable to boot after flashing - #10 by WayneWWW)
"Hi,

Please clarify whether your board is really getting into recovery mode.

There are some methods to check.

  1. If your board is truly in recovery mode, then running flash.sh to flash your board will directly start the flash process, you don’t need to use any jumper or software command to trigger it. The flash.sh script will not give any warning like “this board is in not recovery mode” Please do not use sdkmanager in this step because sdkm will access to the board and use software command to trigger the board into recovery mode. This is not precise to tell whether the board was in recovery mode or not.
  2. Connect the UART console as my previous comment said. If your board is really in recovery mode, UART log will not print anything on it. If you can at least see something on your HDMI as your previous screen, then UART will definitely print something. This could be method to validate whether your uart connection is correct or not.

I think you can firstly clarify above rather than worry about how to flash to NVMe at this moment. Check things step by step.

If the board will go to recovery mode automatically and you didn’t have anything on the FRC pin. Then it is hardware defect. You shouldn’t try anything further if this is broken hardware "

I did recompile with this
sudo ./flash.sh --no-flash jetson-xavier-nx-devkit-emmc mmcblk0p1
and
tried
sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1
###############################################################################

L4T BSP Information:

R35 , REVISION: 1.0

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.

Hi WAYNE,
Could you please help us debug to recover from this state.

Read the developer kit user guide first to make sure you know how to put the board into recovery mode…

1 Like

With FC Rec and GND Connected [9/10 pins] the board enters force recovery and debug USB is listed, Use SDK manager to update again.

1 Like

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