No known UDC device found in massflash

hello!
I encountered a massflash failure issue

My hardware is Orin 64G

The software environment is JetPack5.1.1

Using self-developed onboard

The command is as follows,

I encountered a massflash failure issue

My hardware is Orin 64G

The software environment is JetPack5.1.1

Using self-developed onboard

The command is as follows

But it ultimately failed, the terminal printed as follows!

Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Timeout
Cleaning up...

Connect to the serial port and view the print log as follows!

[15:07:34:634] [    8.835296] Creating 1 MTD partitions on "spi6.0":␍␊
[15:07:34:640] [    8.835419] 0x000000000000-0x000004000000 : "Whole_flash0"␍␊
[15:07:34:646] [    8.835940] tegra-xudc 3550000.xudc: failed to get usbphy-0: -517␍␊
[15:07:34:651] insmod /lib/modules/5.10.104-tegra/kernel/drivers/spi/spi-tegra210-qspi.ko ␍␍␊
[15:07:34:656] insmod /lib/modules/5.10.104-tegra/kernel/drivers/hwmon/pwm-fan.ko ␍␍␊
[15:07:34:661] [    8.843174] tegra-xudc 3550000.xudc: failed to get usbphy-0: -517␍␊
[15:07:34:808] [    9.051580] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit␍␊
[15:08:05:662] [   39.905517] vdd-12v-sys: disabling␍␊
[15:08:05:662] [   39.905622] vdd-1v8-sys: disabling␍␊
[15:08:05:670] [   39.905722] vdd-3v3-ftdi: disabling␍␊
[15:08:34:668] No known UDC device found␍␍␊
[15:08:34:682] bash: cannot set terminal process group (-1): Inappropriate ioctl for device␍␍␊
[15:08:34:687] bash: no job control in this shell␍␍␊
[15:08:34:687] bash-5.0# 

Hi jiangyinghao,

It seems you are using the custom board designed by you.

Have you verified the workflow for massflash on the devkit w/o issue on JP5.1.1?

It seems your board are in recovery boot state, which might be caused from several times boot failed. You may need to check the serial console log earlier than you post currently.

Using the “./flash” method instead of massflash can burn the image and start it normally.

Could you help to provide the exact command you use for massflash and also the related flash and serial console log for further check?