Hi KevinFFF
Thank you for the fast reply.
We are using JetPack 6.0. With older JetPacks, we never had such an issue. Should the backup_restore tool not also flash the QSPI? At least it is part of the image files:
$> ls tools/backup_restore/images/
gptbackup.img nvme0n1p10_bak.img nvme0n1p12_bak.img nvme0n1p14_bak.img nvme0n1p1.tar.gz nvme0n1p3_bak.img nvme0n1p5_bak.img nvme0n1p7_bak.img nvme0n1p9_bak.img QSPI0.img
gptmbr.img nvme0n1p11_bak.img nvme0n1p13_bak.img nvme0n1p15_bak.img nvme0n1p2_bak.img nvme0n1p4_bak.img nvme0n1p6_bak.img nvme0n1p8_bak.img nvpartitionmap.txt tmp
Also we flash new Orin NX modules (factory state) only with the backup restore tool and QSPI seems to be programmed, as the system is able to boot into the efi shell.
Let us know if you need further information.