No known UDC device found in massflash

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

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#
3

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.

4

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

5

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

6

hello!
massflash cmd:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --showlogs

log:
flash_1-1.1.3.4_0_20230529-175049.log (7.3 KB)

7

initrd flash depends on usb device mode. But it looks like your board has problem in usb device mode on usb0.

[15:07:34:646] [ 8.835940] tegra-xudc 3550000.xudc: failed to get usbphy-0: -517␍␊

8

This print was also available on the previous Jetpack 5.0.2, but it will not affect the flash

9

Because it is a custom board, is it related to our UDC related kernel code? We use NVIDIA source code for this part.

10

You need to make sure the usb device mode can work fine between your host and your board when you boot from emmc with flash.sh

還有接下來的說明可能會比較複雜. 如果怕聽不懂的話我可以也用中文說明一次.

11

你好，谢谢，更改了批量刷机的超时时间，可以避免这个问题出现，但是现在出现了刷写QSPI错误
同时我使用NVIDIA的原始硬件和代码做了测试对比
软件环境 JetPack5.1.1
硬件使用Orin Devkit板载和jetson-agx-orin-devkit-as-jao-32gb模组,该模组是8核CPU型号Orin

出现了QSPI问题，如下是log

tar: Read checkpoint 510000
tar: Read checkpoint 520000
tar: Read checkpoint 530000
tar: Read checkpoint 540000
tar: Read checkpoint 550000
tar: Read checkpoint 560000
tar: Read checkpoint 570000
tar: Read checkpoint 580000
tar: Read checkpoint 590000
tar: Read checkpoint 600000
tar: Read checkpoint 610000
tar: Read checkpoint 620000
tar: Read checkpoint 630000
tar: Read checkpoint 640000
tar: Read checkpoint 650000
writing item=74, 1:3:secondary_gpt, 63652740608, 16896, gpt_secondary_1_3.bin, 16896, fixed-<reserved>-0, ab29075c3ee23243a6de9d9e772d6f091b9994cb
[ 137]: l4t_flash_from_kernel: Successfully flash the emmc
[ 137]: l4t_flash_from_kernel: Error flashing qspi
Flash failure
Cleaning up...

制作批量刷机包的命令如下
BOARDID=3701 FAB=500 BOARDSKU=0004 BOARDREV=G.0 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --network usb0 --massflash 5 jetson-agx-orin-devkit-as-jao-32gb mmcblk0p1
刷机的命令如下
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --showlogs

12

請問一下為何要用 jetson-agx-orin-devkit-as-jao-32gb? 這個比較像是performance測試時使用的

如果用 jetson-agx-orin-devkit請問還有碰上問題嗎？

13

你好， jetson-agx-orin-devkit是没有问题的，但是我们有一部分的产品是使用的
jetson-agx-orin-devkit-as-jao-32gb，所以现在这个是一个很棘手的问题，谢谢

14

你好，我的同事也在论坛中提了问题，里面有更详细的log日志，麻烦您看一下，谢谢

15

但是我们有一部分的产品是使用的
jetson-agx-orin-devkit-as-jao-32gb

我已經回應在那條上面了. 但我不太能理解你們怎麼會有一部分產品會是用這個config.
這個用法感覺不太合理… 還麻煩你們說明一下 …

16

好的，谢谢您，我们使用jetson-agx-orin-devkit-as-jao-32gb配置的产品的硬件是使用的Orin module 而不是 Orin Kit，我理解这是两种不同型号，所以不能都使用jetson-agx-orin-devkit配置。
正如下面文档所说

image
image1040×717 82.3 KB

17

Hi

你對於這個blog的理解好像有些錯誤. 這個blog在表達的東西是當你使用"orin devkit module"的狀況下, 如果你要"模擬" 其他款module的時候你該怎麼燒…

所有的Orin AGX 都可以透過jetson-agx-orin-devkit燒錄.
所謂的jetson-agx-orin-devkit-as-jao-32gb 這個config的用途是給 "devkit module"去模擬 "production module"用的.

然後因為你們的"產品"通常都是production module. 所以你們應該直接用jetson-agx-orin-devkit才對… 不用還跑去用etson-agx-orin-devkit-as-jao-32gb… 用模擬的config是多此一舉…

如果還是聽不懂的話, 我可以多說明一點…

18

您好，也就是说
Orin 32G kit
Orin 32G module
Orin 64G module
都是使用 jetson-agx-orin-devkit这个配置吗

19

對…

所謂的jetson-agx-orin-devkit-as-jao-32gb使用的時機是在你只有Orin 32GB devkit的狀況下… 你希望能模擬一下Orin 32G module的performance, 才會用到

如果你本來就在使用Orin 32G module, 那麼你根本不需要模擬任何東西. 直接正常燒錄就好了…

會需要模擬是因為Devkit module跟32GB module在各個處理器的core/freq有所不同… 所以我們才提供一個模擬用的config使用.

image
image832×362 23.7 KB

1 Like
21

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