Can’t find matching TN Spec in OTA Blob!

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

After a full flash of 5.0.2 through “sudo nvsdkmanager_flash.sh --storage nvme0n1p1”, and apt update/upgrade, everything looked successful

Then i want to install allied vision csi camera driver (Problem with compiling kernel 34.1.1 and where to find precompiled one · Issue #55 · alliedvision/linux_nvidia_jetson · GitHub)

which seems to call ota mechanism as seen in /opt/ota_package/kernel.log

``
Start running: /opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh -c
3668-100—1–jetson-xavier-nx-devkit-qspi-
Got individual part name: kernel
Got update payload: /opt/ota_package/bl_update_payload
Tegra User Block Device: /dev/disk/by-partlabel
Tegra Boot Block Device: /dev/mtdblock0
Tegra GPT Block Device: /dev/mtdblock0
HEADER: MAGIC NVIDIA__BLOB__V3
HEX_VALUE 16975394
BLOB_SIZE 50132230
HEADER_SIZE 48
NUMBER_OF_ELEMENTS 19
HEADER_TYPE 0
UNCOMP_SIZE 50132230
MB1_RATCHET_LV 0
MTS_RATCHET_LV 0
ROLLBACK_FUSE_LV 0
Device TN Spec: 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-qspi-
Device Compatible Spec: 3668-100—1–jetson-xavier-nx-devkit-qspi-
Can’t find matching TN Spec in OTA Blob!
GPT update failed. Status: 3
/usr/sbin/nv_bootloader_payload_updater --forced-part Failed.
`
issue look ota related cause i found this post on nvidia forum OTA fails on Nx-devkit when system is installed on nvme

What could I do ?

thx

3

hello xnodrk,

do you have allied vision csi camera driver with r35.1 release?
since you already install r35.1 to your target, you cannot install r34.1.1 due to fallback protection.

the other approach is looking for kernel release sources package, and you may integrate the code and rebuilt kernel image for r35.1

4

I have new allied vision csi camera driver that work with r35.1 release

I reflashed with 35.1 with sudo nvsdkmanager_flash.sh --storage nvme0n1p1
then got this error on ota update

reading the post on OTA fails on Nx-devkit when system is installed on nvme] i tried reflashing with changing num sector in flash-l4t-nvme.xml with :
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme.xml -S 10GiB --showlogs jetson-xavier-nx-devkit nvme0n1p1

and i have following error :

Reach the end of the SPI device
[ 189]: l4t_flash_from_kernel: Successfully flash the qspi
[ 189]: l4t_flash_from_kernel: Flashing success
Error flashing non-qspi storage

Cleaning up…

5

I reflashed with adding secureboot package with : sudo ./nvsdkmanager_flash.sh --storage nvme0n1p1

flash successful.

when launching alliedvision install.sh same error on target :

  GNU nano 4.8                        kernel.log                                   
Start running: /opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh -c
3668-100---1--jetson-xavier-nx-devkit-qspi-
Got individual part name: kernel
Got update payload: /opt/ota_package/bl_update_payload
Tegra User Block Device: /dev/disk/by-partlabel
Tegra Boot Block Device: /dev/mtdblock0
Tegra GPT Block Device: /dev/mtdblock0
HEADER: MAGIC NVIDIA__BLOB__V3
HEX_VALUE 16975394
BLOB_SIZE 50132230
HEADER_SIZE 48
NUMBER_OF_ELEMENTS 19
HEADER_TYPE 0
UNCOMP_SIZE 50132230
MB1_RATCHET_LV 0
MTS_RATCHET_LV 0
ROLLBACK_FUSE_LV 0
Device TN Spec: 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-qspi-
Device Compatible Spec: 3668-100---1--jetson-xavier-nx-devkit-qspi-
Can't find matching TN Spec in OTA Blob!
GPT update failed. Status: 3
/usr/sbin/nv_bootloader_payload_updater --forced-part Failed.

on target, /etc/nv_boot_control.conf :

3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-qspi-
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

should it be different since i flashed on nvme with sudo ./nvsdkmanager_flash.sh --storage nvme0n1p1` ?

6

Up

7

hello xnodrk,

there’re some partitions on QSPI, is this Xavier NX DevKit ever flashed before?
you may also refer to developer guide, External Storage Device Partition to create a partition configuration file for flashing to an external storage device; please note that, num_sectors * sector_size must be equal to, or smaller the size of your external storage device, and the device “type” needs to be “nvme”.

8

Yes it has been sent to some scientific laboratory then i flashed on sd , then i put nvme , did many flash with different jetpack

now its working with sudo ./nvsdkmanager_flash.sh --storage nvme0n1p1and adding security package

then in /etc/nv_boot_control.conf :

`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

I might have a mess in my partition or anything but now its working , booting on nvme my alliedvision camera detected

I will look into partitions at a later time

Thank you

10

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