Hi Jerry. Unfortunately, I’ve been having a few problems with flashing my Xavier manually.
The flashing process consistently gets stuck at
CPU Bootloader is not running on device.
[ 7.6626 ] Applet version 01.00.0000
[ 8.7760 ] Sending blob
[ 8.7762 ] [................................................] 100%
[ 9.5566 ] tegrarcm_v2 --boot recovery
[ 9.5580 ] Applet version 01.00.0000
[ 11.6817 ] tegrarcm_v2 --isapplet
[ 1016.0394 ] tegrarcm_v2 --ismb2
[ 2031.8470 ] tegradevflash_v2 --iscpubl
[ 2031.8505 ] CPU Bootloader is not running on device.
I’ve also attached the entire log to help with debugging: cpu-bootloader-not-running-on-device.txt (62.9 KB)
For context, I am flashing via an x86 laptop (not a VM) running Ubuntu 20.04. I have been able to flash my Xavier several times to Jetson 35.1 using Nvidia’s official SDKManager GUI application on the same laptop without any issues or errors. This is my first time attempting to flash manually via the official command-line tools.
The Xavier device I am using is this one. As per this device’s official documentation, it supports manual flashing via the terminal in addition to automatic flashing via SDKManager.
I downloaded both the Driver Package and Sample Root File System from this link: Jetson Linux 35.1 | NVIDIA Developer
I decided to flash Jetson Linux v35.1 because I’ve been able to successfully flash 35.1 to my device via SDKManager several times already and this is the version of Jetson Linux we’ve been discussing lately.
And I ran all the required terminal commands for a manual flash:
$ tar xf <L4T_RELEASE_PACKAGE>
$ cd Linux_for_Tegra/rootfs/
$ sudo tar xpf ../../<SAMPLE_FS_PACKAGE>
$ cd ..
$ sudo ./apply_binaries.sh
$ sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1
However, the manual flash consistently is stuck at
CPU Bootloader is not running on device..
I’ve also made the changes you referenced to disable OP-TEE; however, I have reason to believe this issue is unrelated to those changes I’ve made since I’ve been able to consistently generate a valid
system.img file as you should be able to see in the logs I attached earlier. The issue seems to arise during the flashing process.
I’ve searched around on this forum for this particular error message already but many posts don’t really have a definitive solution so I was hoping you might be able to lend a hand with debugging? Thank you in advance.