AGX Xavier problem : Bootloader is not running on device

Hello,
I bought this board as a 2nd hand, I did not know the password so I’m trying to reinstall OS in Jetson AGX Xavier from recovery mode.

I’ve got this error: The target is in a bad mode, then I’m going to boot it in rcm

I tried with JetPack 5.1.2 and JetPack 4.6.x but still got this error
BootRoom is not running
tegrarcm_v2 --isapplet

I made sure that did not unplug USB cable while flashing.

Please help me.

Hi,

can you please dump the full log here?
Don’t just give a screenshot.
It’d be better if you can also capture the serial console log.

Sorry, my bad. This is SDK logs when I installed JetPack 5.1.2. It said that boot runner was not running.
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_AGX_Xavier_modules_2023-08-28_20-22-18.zip (114.0 KB)

Then I searched for that error and tried this command on sdk folder :

sudo SKIP_EEPROM_CHECK="-n" ./flash.sh jetson-agx-xavier-devkit mmcblk0p1 

Then I got this log on terminal
terminal_log.txt (50.0 KB)
The log made sure that I connected AGX Xavier by rcm and there is no bootloader on that device, event I still can boot it to ubuntu login screen

Hi,

If you don’t know how to dump uart log, please check this page.

Uart log is device side log.
What you shared are all host logs but not uart log/serial log.

Hi, I did what you said and this is what I’ve got. Sorry I don’t know what does it said.

uart_log (46.8 KB)

I don’t know why but that xavier became so hot when run uart log.

  1. Each line in your log file got truncated. Please resize your terminal and dump the log again.

  2. We want your log during flash failure, but it seems you only shared us a log which is from boot up case.

Hope you really understand what you need to do here. We need the log when error happens, but not something unrelated.

Thank you for guiding me.
I saved this log from minicom after flash in recovery mode. Please check this out.
minicom_flash (2.6 KB)

Hi,

So how is the host side log ? What is your command to flash the board?

Flash is both side (host +jetson) work, uart log is the jetson side log. I always need your host side log as a pair to check.

Also, your command here could be wrong. Please do not add that SKIP_EEPROM_CHECK… only let pure flash.sh run…

sudo SKIP_EEPROM_CHECK=“-n” ./flash.sh jetson-agx-xavier-devkit mmcblk0p1

1 Like

Your jetpack5 sdkmanager log says it has problem in detecting board in recovery mode.

>jetson-agx-xavier-devkit found.
*** Finding boot device ... Boot device mmcblk0p1 found.
"/home/minh/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/flash.sh"  jetson-agx-xavier-devkit mmcblk0p1
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 4.1
# User release: 0.0
###############################################################################
Error: probing the target board failed.
       Make sure the target board is connected through 
       USB port and is in recovery mode.
20:23:37.702 - Info: [ Component Install Finished with Error ]
20:23:37.702 - Info: [host] [ 150.41 MB used. Disk Avail: 54.83 GB ]
20:23:37.702 - Info: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 22s ]

Your jetpack4 sdkm log is not included. I wonder, are you using a VM as host?

Yes, I’m using VM host

please find a native ubuntu host.

Thank you so much, it solved my problem, but why must be the real host instead of a VM ?

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