Backup script failed

Hi NVIDIA,
The firmware was flashed using a command:sudo bash ./flash.sh jetson-agx-orin-devkit mmcblk0p1

But the backup script failed to run:

Linux_for_Tegra$ sudo ./tools/backup_restore/l4t_backup_restore.sh -b -c jetson-agx-orin-devkit

This is flash log:
flash_log.txt (113.0 KB)
This is uart log:
uart_log.txt (60.5 KB)

insmod /lib/modules/5.15.148-rt-tegra/kernel/drivers/usb/typec/stusb160x.ko 
insmod /lib/modules/5.15.148-rt-tegra/updates/drivers/platform/tegra/mce/tegra-mce.ko 
insmod /lib/modules/5.15.148-rt-tegra/updates/drivers/spi/spi-tegra210-quad.ko 
[   10.385549] tegra-qspi 3270000.spi: Adding to iommu group 7
[   10.395689] spi-nor spi0.0: mx25u51279g (65536 Kbytes)
No known UDC device found
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-5.1# 
bash-5.1# 

version is :

$ cat rootfs/etc/nv_tegra_release 
# R36 (release), REVISION: 4.3, GCID: 38968081, BOARD: generic, EABI: aarch64, DATE: Wed Jan  8 01:49:37 UTC 2025
# KERNEL_VARIANT: oot
TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia

The custom board used by jetson runs the rt kernel.

How to solve it?

bash-5.1# lsmod
Module Size Used by
spi_tegra210_quad 32768 0
tegra_mce 28672 0
stusb160x 20480 0
nvethernet 1171456 0
nvpps 32768 1 nvethernet
ipv6 503808 34
tegra_xudc 45056 0
ucsi_ccg 28672 0
typec_ucsi 36864 1 ucsi_ccg
typec 61440 2 stusb160x,typec_ucsi
libcomposite 65536 0
pwm_fan 20480 0
pwm_tegra 20480 1
tegra_bpmp_thermal 16384 0
nvme 49152 0
nvme_core 110592 1 nvme
pcie_tegra194 40960 0
phy_tegra194_p2u 16384 4
r8168 520192 0
bash-5.1#

Are there any missing drivers?

Hi,

Since you are using a custom carrier board, I found a related NVIDIA forum thread that may be relevant to this issue:

No Known UDC device found in massflash

This looks similar to your case because the backup process boots the Jetson into an initrd recovery environment and relies on USB device mode to create the usb0 network interface. If the USB Device Controller is not registered correctly, the process can stop with:

No known UDC device found

Regards,

Manuel Leiva
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

Hi ManuelLeiva, thank you for your reminder. It’s true that there was an error in the USB dts configuration.