ota orin nx from r35.3.1 to r35.4.1 failed
root@tegra:/home/nvidia# ./nv_bootloader_payload_updater --part kernel
Start running: /opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh -c
3767--0001--1--jetson-orin-nano-devkit-
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
Skip querying the boot device parameters
HEADER: MAGIC NVIDIA__BLOB__V3
HEX_VALUE 16975394
BLOB_SIZE 43028106
HEADER_SIZE 48
NUMBER_OF_ELEMENTS 2
HEADER_TYPE 0
UNCOMP_SIZE 43028106
MB1_RATCHET_LV 0
MTS_RATCHET_LV 0
ROLLBACK_FUSE_LV 0
Device TN Spec: 3767-300-0001-N.2-1-0-jetson-orin-nano-devkit-nvme-
Device Compatible Spec: 3767--0001--1--jetson-orin-nano-devkit-
Device TN Spec: 3767-300-0001-N.2-1-0-jetson-orin-nano-devkit-nvme-
Device Compatible Spec: 3767--0001--1--jetson-orin-nano-devkit-
Device is fused board.
ENTRY_TABLE:
PART POS LEN VER TNSPEC TYPE UPDATABLE
A_kernel 416 42672128 13617 1 1
A_kernel-dtb 42672544 355562 13617 3767-300-0001-N.2-1-0-jetson-orin-nano-devkit-nvme- 1 1
Can't find kernel in /opt/ota_package/bl_update_payload
Writing to partitions failed.
OTA Blob update failed. Status: 3
./nv_bootloader_payload_updater --part Failed.
Why is “A_kernel” present in the ENTRY_TABLE?
Actually, the label should be “kernel.”
Where is the ENTRY_TABLE dumped from?
FYI
root@tegra:/home/nvidia# blkid
/dev/nvme0n1p1: UUID="fcf35a4a-6fdf-4296-a143-fcb869ed7322" TYPE="ext4" PARTLABEL="APP" PARTUUID="dc4830b6-ee59-4e3f-9ccb-60979dcf2e64"
/dev/nvme0n1p2: PARTLABEL="kernel" PARTUUID="40a9b3ad-da4b-42c5-a96b-f125003fef69"
/dev/nvme0n1p3: PARTLABEL="kernel-dtb" PARTUUID="2142a009-3c73-42a8-bfdb-a25c4d7bc20b"
/dev/nvme0n1p4: PARTLABEL="reserved_for_chain_A_user" PARTUUID="6df77e18-d079-4966-be7d-3c73f00fdc40"
/dev/nvme0n1p5: PARTLABEL="kernel_b" PARTUUID="113ced6e-4bc0-4359-ac6b-8705924baa61"
/dev/nvme0n1p6: PARTLABEL="kernel-dtb_b" PARTUUID="7372402e-b7b1-4110-9d88-9e5a38df8d79"
/dev/nvme0n1p7: PARTLABEL="reserved_for_chain_B_user" PARTUUID="2cef8321-47b3-4f5b-b5ba-1346f508285e"
/dev/nvme0n1p8: PARTLABEL="recovery" PARTUUID="628b2cce-8845-4a4a-83de-741aa246472a"
/dev/nvme0n1p9: PARTLABEL="recovery-dtb" PARTUUID="10ccd49d-9da3-438a-9db4-68684a887651"
/dev/nvme0n1p10: PARTLABEL="RECROOTFS" PARTUUID="265077ee-2046-4e5a-8bc7-653bf8179347"
/dev/nvme0n1p11: UUID="7508-4A48" TYPE="vfat" PARTLABEL="esp" PARTUUID="01025cb9-a30a-4808-8593-5553d1daf96e"
/dev/nvme0n1p12: PARTLABEL="recovery_alt" PARTUUID="516f7383-1083-4692-82ea-d52ff260ac62"
/dev/nvme0n1p13: PARTLABEL="recovery-dtb_alt" PARTUUID="09eb5c44-55ee-455d-84ac-5644729c5d7d"
/dev/nvme0n1p14: PARTLABEL="esp_alt" PARTUUID="466e0da0-3561-4ef5-aa7b-eb76c1905d73"
/dev/nvme0n1p15: LABEL="testdata" UUID="3d0febce-6b89-4098-9ae5-3f50c835d696" TYPE="ext4" PARTUUID="de2d7ac5-6910-9e43-a3a3-a746b0e70eba"
/dev/loop0: SEC_TYPE="msdos" LABEL_FATBOOT="L4T-README" LABEL="L4T-README" UUID="1234-ABCD" TYPE="vfat"
/dev/zram0: UUID="579ab92c-3736-4a1a-bd91-f97cb7e59aa8" TYPE="swap"
/dev/zram1: UUID="46c81f19-aded-4608-8496-969da3699796" TYPE="swap"
/dev/zram2: UUID="7585a738-decf-4b76-9de8-0c8da99ee9c6" TYPE="swap"
/dev/zram3: UUID="dfe7d6c5-9c54-4867-9317-fbf03743eb8e" TYPE="swap"
/dev/zram4: UUID="4a6782e4-f06a-47fd-9e37-2b8b52876acc" TYPE="swap"
/dev/zram5: UUID="3402f134-30d6-4858-892b-b13edc8f1847" TYPE="swap"
root@tegra:/home/nvidia# cat /etc/nv_boot_control.conf
TNSPEC 3767-300-0001-N.2-1-0-jetson-orin-nano-devkit-nvme-
COMPATIBLE_SPEC 3767--0001--1--jetson-orin-nano-devkit-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
root@tegra:/home/nvidia# ls -ahl /dev/disk/by-partlabel/
total 0
drwxr-xr-x 2 root root 320 Mar 15 2023 .
drwxr-xr-x 8 root root 160 Mar 15 2023 ..
lrwxrwxrwx 1 root root 15 Mar 15 2023 APP -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 16 Mar 15 2023 esp -> ../../nvme0n1p11
lrwxrwxrwx 1 root root 16 Mar 15 2023 esp_alt -> ../../nvme0n1p14
lrwxrwxrwx 1 root root 15 Mar 15 2023 kernel -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Mar 15 2023 kernel_b -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 Mar 15 2023 kernel-dtb -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Mar 15 2023 kernel-dtb_b -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 15 Mar 15 2023 recovery -> ../../nvme0n1p8
lrwxrwxrwx 1 root root 16 Mar 15 2023 recovery_alt -> ../../nvme0n1p12
lrwxrwxrwx 1 root root 15 Mar 15 2023 recovery-dtb -> ../../nvme0n1p9
lrwxrwxrwx 1 root root 16 Mar 15 2023 recovery-dtb_alt -> ../../nvme0n1p13
lrwxrwxrwx 1 root root 16 Mar 15 2023 RECROOTFS -> ../../nvme0n1p10
lrwxrwxrwx 1 root root 15 Mar 15 2023 reserved_for_chain_A_user -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 Mar 15 2023 reserved_for_chain_B_user -> ../../nvme0n1p7
hello Henry.Lou,
did you meant you would like to update kernel partition only?
please refer to developer guide, Updating Jetson Linux with Image-Based Over-the-Air Update.
hi @JerryChang
We are not beginners.
Your previous response was not helpful at all.
Could you provide a proper answer to the question?
we mean answer questions directly first.
it’s because there’re changes in the latest release vesion,
for instance,
$ ls -al /dev/disk/by-partlabel/
lrwxrwxrwx 1 root root 15 Nov 21 2023 A_kernel -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Nov 21 2023 B_kernel -> ../../nvme0n1p5
hi @JerryChang
do you mean that partiton table in r35.4.1 change to A_kernel B_kernel?
but in r35.3.1 kernel kernel_b?
hello Henry.Lou,
I don’t recall which release version has such change. but we’ve test OTA update moving forward successfully.
hi @JerryChang
can you post the upgrade log here.
hello Henry.Lou,
here’s UART log to OTA update from r35.3.1 to r35.4.1 on Orin-Nano.
for instance, OTA-upgrade_Orin-Nano_Uart.log (209.0 KB)
system
Closed
13
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
