Could you provide the log file in the /opt/nvidia/ota_package/
2 . Could you edit the /etc/nv_boot_control.conf, change the string “jetson-xavier-nx-devkit-qspi" to “jetson-xavier-nx-devkit”
I am not sure why your TNSPEC is “3668-301—1–jetson-xavier-nx-devkit-qspi-", but we don’t support this SPEC in the BUP, the nv_update_engine can’t find matched TN-SPEC. Normally we use the “jetson-xavier-nx-devkit” to flash the device, and the SPEC is the “jetson-xavier-nx-devkit".
sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
6 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up nvidia-l4t-bootloader (34.1.1-20220516211757) ...
Warning: Cannot get compatible board name.
Starting bootloader post-install procedure.
ERROR. Procedure for bl_only_payload update FAILED.
Cannot install package. Exiting...
dpkg: error processing package nvidia-l4t-bootloader (--configure):
installed nvidia-l4t-bootloader package post-installation script subprocess ret
urned error exit status 1
and after that nv_boot_control has the second line trucated:
the answer seems likely not;
However another issue is how to patch the situation of the similar kind as in the topic on AGX which was booted from nvme DP5.0 until upgrade to 5.0.1 afte rthat it won’t work? Will it likely be resolved by just editing the single file? serial.log (190.4 KB)
I checked your log, looks like it is not able to restore since it cannot boot into system anymore.
You can file a new topic for your own issue. If the case is different, then we need to check it separately.
I just executed sudo apt update && sudo apt upgrade on AGX which was booting from NVME with JP5.0_DP; Sio it kind of upgraded to 5.0.1 but got broken, right? You want me to post a separate issue in AGX section of the forum for the issue?