Is it possible to directly update BUP built from L4T 32.7.3 based on L4T 32.5.1?

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
,
1

Previously, we produced our products with L4T 32.5.1 and they were all deployed in field. Recently, we accomplished the L4T upgrade to latest L4T 32.7.3. So, we just would like these deployed devices to be updated to L4T v32.7.3 through BUP update. We built a BUP based on v32.7.3 and got failure after ran update command on device which was installed v32.5.1:
####################################################################
~$ sudo l4t_payload_updater_t210 -v
[sudo] password for scala:
SPEC: 3448-300-0002–1-0-jetson-nano-devkit-emmc-smpsq-mmcblk0p1
Compatible SPEC: 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1

Version:
NV3
#R32 , REVISION: 5.2
BOARDID=3448 BOARDSKU=0002 FAB=300
20221125095113

~$ sudo l4t_payload_updater_t210 bl_update.img
BLOB PATH:
/home/scala/bl_update.img

SPEC: 3448-300-0002–1-0-jetson-nano-devkit-emmc-smpsq-mmcblk0p1
Compatible SPEC: 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1

Error. Invalid input blob file.
Input magic: NVIDIA__BLOB__V2
Expected magic: NVIDIA__BLOB__V2
Input version: 0x01020621
Expected version: 0x00020000
Input type: 0
Expected type: 0 (type 1 BMP blobs are not currently supported)
No changes have been made. Exiting…
####################################################################

Seems version was not expected, thus the process was terminated.
My question is if it is a limitation in different L4T version. If the main version is changed, is it viable to perfrom BUP update between these two different versons ?

3

Hi 18502109920,

Are you using the custom board?
If yes, have you confirmed L4T 32.7.3 could work as normal on your board?

Do you refer to the following instruction for bootloader update?
Jetson Nano/TX1 Update and Redundancy - Bootloader Update

4

Yes, we are using custom board. We can do BUP update to v32.7.3 if the device is deployed with L4T v32.7.3.

Yes, we did take reference from that guide

5

It seems there’s bug in r32.5.1.
Please refer to the following thread to check if it could help.
Bootloader Update Error - #17 by WayneWWW

7

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