Bootloader Update Error

[rd1]

We used “sudo BOARDID=3448 BOARDSKU=0002 FAB=400 FUSELEVEL=fuselevel_production ./build_l4t_bup.sh jetson-nano-devkit-emmc-smpsq mmcblk0p1” to generate bl_update_payload,
and then used “sudo l4t_payload_updater_t210 payloads_t21x/bl_update_payload” to update.
But it is error:
BLOB PATH:
/opt/ota_package/t21x/bl_update_payload

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

we are 3448-400-0002* ,but Compatible SPEC is 3448-300-0002*
Please help to analyze it.

[WayneWWW]

Then maybe write the FAB to 300?

[rd1]

what do you mean?
where is the SPEC? we don’t find it

[WayneWWW]

We used “sudo BOARDID=3448 BOARDSKU=0002 FAB=400 FUSELEVEL=fuselevel_production ./build_l4t_bup.sh jetson-nano-devkit-emmc-smpsq mmcblk0p1” to generate bl_update_payload,
and then used “sudo l4t_payload_updater_t210 payloads_t21x/bl_update_payload” to update.

You write FAB=400 here and the board tells you the FAB is 300. Why not just try with FAB=300 in your command?

[rd1]

we always used FAB=400 ,it is not just modify FAB=300,it had other modify .
Our problem is why to check the SPEC ,where is the SPEC?
we update from L4T R32.4.2 to R32.5.1, it is ok on L4T R32.4.2, the same command and the same usage.

[WayneWWW]

sudo [env={value}, …] ./build_l4t_bup.sh [options] board_config rootdev

The BOARDID, SKU and FAB are stored inside the EEPROM of the module. You can just put the device in recovery mode and let the script to read it. That is why these parameters are not necessary input. They are just optional.

[WayneWWW]

And I am not sure if you notice that you didn’t even share the full error log.

[rd1]

how to find the log? we change to FAB=300 to try, it also failed ,even if test the command:

scala@localhost:~$ sudo l4t_payload_updater_t210 -v
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 board config name 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1

It is not same .

[WayneWWW]

err… so the error log you saw when running command “sudo l4t_payload_updater_t210 payloads_t21x/bl_update_payload” is the

“Error. Invalid board config name 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1” ?

[rd1]

yes

[WayneWWW]

Can you share the result of this file?

cat /etc/nv_boot_control.conf

[rd1]

root@localhost:/home/scala# sudo l4t_payload_updater_t210 -v
SPEC: 3448-300-0002-0-1-0-jetson-nano-devkit-emmc-smpsq-mmcblk0p1
Compatible SPEC: 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1

Error. Invalid board config name 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1
root@localhost:/home/scala# cat /etc/nv_boot_control.conf
TNSPEC 3448-300-0002-0-1-0-jetson-nano-devkit-emmc-smpsq-mmcblk0p1
COMPATIBLE_SPEC 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1
TEGRA_CHIPID 0x21
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1
root@localhost:/home/scala#

[rd1]

what should we do?
TNSPEC 3448-300-0002-0-1-0-jetson-nano-devkit-emmc-smpsq-mmcblk0p1
COMPATIBLE_SPEC 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-mmcblk0p1

[WayneWWW]

Hi,

Are the driver package you are using on the host and software running on your jetson nano both from rel-32.5.1?

[rd1]

yes ,we are used command"sudo BOARDID=3448 BOARDSKU=0002 FAB=300 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-nano-devkit-emmc-smpsq mmcblk0p1" to generate Mass-flash image.

[WayneWWW]

Hi,

Per checked internally, this is a bug that will be fixed in rel-32.6.1.

If you want to stay on rel-32.5.1, the workaround is

download l4t_payload_updater_t210.py from the NVIDIA Developer web site’s L4T 32.5 Archive to the Linux_for_Tegra directory. Then copy the file to its final location and make it executable:

$ cd Linux_for_Tegra/
$ sudo cp <l4t_payload_updater_t210.py> rootfs/usr/sbin/l4t_payload_updater_t210
$ sudo chmod a+x rootfs/usr/sbin/l4t_payload_updater_t210

[linuxdev]

If you do find you want to create a log of a command line program (such as if the output is much longer than an easy copy and paste), then modify the command (I’ll pretend the command is “ls”) like this:
ls 2>&1 | tee log_command.txt
…then just attach the log_command.txt to your post. Most useful from serial console (if command is on the Jetson and not the PC) since it means the log is on the host PC right from the start.

[rd1]

ok ,thanks.