JP5-DP installed on NVME SSD - OTA upgrade failed (bl_only_payload)

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
,
1

I have a NX devkit that had been installed to NVME SSD (no SD card) with SDKM and it was working fine with r34.1.

Today, I’ve used apt update/upgrade and it updated to r34.1.1 but nvidia-l4t-bootloader package failed with:

Setting up nvidia-l4t-bootloader (34.1.1-20220516211757) ...
3668-301---1--jetson-xavier-nx-devkit-qspi-
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 returned error exit status 1

The kit boots and seems running a mixed version of R34.1 and r34.1.1.
I have not able to fix that.
Is there a fix for this without reflashing ?

Attached is the log of the update.
update.log (22.0 KB)

3

Hi HP,

Just checked your log here.

  1. 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”.

4

Hi Wayne,

Thanks for your help. Here are the log files found in /opt/ota_package :
kernel.log (827 Bytes)
bl_only_payload.log (990 Bytes)
xusb_only_payload.log (1.5 KB)

I also tried editing /etc/nv_boot_control.conf to:

TNSPEC 3668-301-0000-A.0-1-2-jetson-xavier-nx-devkit
COMPATIBLE_SPEC 3668-301---1--jetson-xavier-nx-devkit
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

but I didn’t improve:

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.
3668-301---1--jetson-xavier-nx-
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:

TNSPEC 3668-301-0000-A.0-1-2-jetson-xavier-nx-devkit
COMPATIBLE_SPEC 3668-301---1--jetson-xavier-nx-
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

(tried several times)

1 Like
5

Hi HP,

Please add “-” t to the nv_boot_control.conf.

As following:

TNSPEC 3668-301-0000-A.0-1-2-jetson-xavier-nx-devkit-
COMPATIBLE_SPEC 3668-301—1–jetson-xavier-nx-devkit-

6

It worked out.
Thank you so much, Wayne, you saved me days of extra work :-)

7

after accidental boot from sdcard with JP4.6.1 image my nvme ssd JP4.6 filesystem has the values as follows

root@nx:/# cat /etc/nv_boot_control.conf
TNSPEC 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-qspi-internal
COMPATIBLE_SPEC 3668-100---1--jetson-xavier-nx-devkit-qspi-
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
root@nx:/#

Is it likely that just by overriding them to the form below could work ?



TNSPEC 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-
COMPATIBLE_SPEC 3668-100---1--jetson-xavier-nx-devkit-
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

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)

8

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.

9

Hi @WayneWWW
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?

10

Yes, please share the exact steps to reproduce issue in a new topic in AGX forum.

11

but it is referenced already here in AGX section

so I shall post it again third time?
the only exact steps were to execute

sudo apt update
sudo apt upgrade

on AGX with JP 5.0DP running from nvme

12

Please just follow my instructions and file new topic. Attach the log and the method of how you set up your nvme.

13
14

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