Hey, I’ve created the bootloader update package with the following command: sudo BOARDID=3668 FAB=100 ./build_l4t_bup.sh jetson-xavier-nx-devkit mmcblk0p1 Trying to install it with the following command: nv_update_engine --install bl --payload /bl_update_payload This yields the following error: …

5.0.2 to 5.1 Apt update is not an option as we customized the kernel and other stuff. Anyway. It does not seem like we will have any 5.0.2 system we can not update with reflash. So we can leave it as it is. You might just want to find out what’s wrong for other customers. Updating the bootloader …

Okay I’ve found out whats going wrong here. From 5.0.2 to 5.0.2 or 5.0.2 to 5.1 I need to use the old method generated with build_l4t_bup.sh and apply it with nv_update_engine --payload /bl_update_payload -i When I try to update without -f i get the following message: Error: unable to find ker…

Hi seeky15, [image] seeky15: With -f it seems to work, but that updates to the current slot, I need it to be applied to the active slot due to A/B rootfs being updated after the bootloader. Do you mean that you could update bootloader to current slot successfully? It seems “install bootload…

The issue was that the nv_update_engine still exists in 5.1 despite it not working anymore, as you guys locked the access to the QSPI Flash from userland. Thats why my initial try did not work. When I am coming from 5.0.2 to 5.1 the nv_update_engine still works while in the old userland. I have ma…

So I’ve updated from 5.0.2 to 5.1 now with the build_l4t_bup.sh and nv_update_engine. The update worked, it boots with the new bootloader now. Unfortunately nvbootctrl -t rootfs now tells me that A/B is not enabled anymore. RootFS A/B is not enabled. How do I need to generate the bup so that the …

Hey, I am updating from 5.0.2 to 5.1. The capsule update is only implemented in 5.1, 5.0.2 does not have the required efivars. I need the tools from 5.0.2 to update to 5.1 When you update the userland to 5.1 while keeping the old bootloader it won’t work properly anymore. So the bootloader update…

So, any idea how to keep A/B rootfs enabled after updating?

Please check Rootfs A/B redundancy fail-over mechanism in Jetpack5.1 - Jetson & Embedded Systems / Jetson Xavier NX - NVIDIA Developer Forums

Hey @kayccc unfortunately that has nothing to do with my issue. I updated from 5.0.2 to 5.1 as described in the manual, but afterwards the system will not have the A/B enabled anymore…

Have you tried to update from JP5.0.2 or JP5.1 to JP5.1.1? Or just use apt to update Jetpack release? Software Packages and the Update Mechanism — Updating from the NVIDIA APT Server

Jetpack 5.1 Bootloader update

Robotics & Edge Computing Jetson Systems Jetson Xavier NX

KevinFFF March 9, 2023, 7:32am 7

Have you referred to the following thread for the instruction of bootloader update with r35.2.1?
Mark bootloader bootable - #7 by carolyuu
Please replace t234 with t194 for Xavier NX

Topic		Replies	Views
Nv update engine runs failed on JP5.0.2 Jetson Xavier NX ota	8	871	August 23, 2022
Redundant A/B rootfs does not switch automatically after OTA Jetson AGX Xavier boot , security	24	516	September 18, 2025
Jetpack 5.1 needs clarification from NVIDIA! Jetson Xavier NX boot , nvbugs	4	1202	March 29, 2023
JetPack 4 to JetPack 5 update with A/B rootfs enabled without booting into recovery partition and/or without layout change Jetson AGX Xavier security	18	1118	February 26, 2024
Update Bootloader with nv_update_engine for JetPack-5.1.1 (L4T-35.3.1) Jetson Orin NX reflash	5	401	July 8, 2024
L4T 35.6.2 Bootloader Update Jetson Xavier NX nvbugs	85	1489	October 20, 2025
Procedure for A_kernel update FAILED - 5.1 to 5.1.1 Jetson Orin NX reflash	15	2047	April 28, 2023
nv_update_engine not updating from R32.2 to R32.2.1 Jetson TX2	9	1133	January 30, 2020
JetPack 5.1 with Jetson Linux 35.2.1 Released Jetson Xavier NX	14	4538	March 28, 2023
Setting bootable and unbootable AB rootFS slots for L4T r35.1 Jetson AGX Xavier security	36	4525	March 29, 2023

Jetpack 5.1 Bootloader update

Related topics