Custom carrier board use USB0 flash error: Cannot Open USB

Hi,

We design a custom carrier board for AGX Xavier, and I cannot flash the xavier module on our board.
The error message on the host is as below. More detailed log is attached(1: host_flash_log_20220331.log, 2: xavier-device_flash_log_20220331.log).
host_flash_log_20220331.log (16.2 KB)
xavier-device_flash_log_20220331.log (4.1 KB)

[   2.3441 ] Sending mb2
[   2.3446 ] [................................................] 100%
[   2.3569 ] 
[   2.3595 ] tegrarcm_v2 --boot recovery
[   2.3618 ] Applet version 01.00.0000
[   2.4389 ] 
[   3.4430 ] tegrarcm_v2 --isapplet
[   3.4454 ] USB communication failed.Check if device is in recovery
[   3.4739 ] 
[   3.4765 ] tegrarcm_v2 --ismb2
[   3.4789 ] USB communication failed.Check if device is in recovery
[   3.5218 ] 
[   3.5245 ] tegradevflash_v2 --iscpubl
[   3.5269 ] Cannot Open USB
[   3.5698 ] 
[   4.5736 ] tegrarcm_v2 --isapplet
[   4.5760 ] USB communication failed.Check if device is in recovery
[   4.6018 ] 
[   4.6045 ] tegrarcm_v2 --ismb2
[   4.6069 ] USB communication failed.Check if device is in recovery
[   4.6498 ] 
[   4.6525 ] tegradevflash_v2 --iscpubl
[   4.6548 ] Cannot Open USB
[   4.6978 ] 
[   5.7016 ] tegrarcm_v2 --isapplet
[   5.7040 ] USB communication failed.Check if device is in recovery
[   5.7298 ] 
[   5.7325 ] tegrarcm_v2 --ismb2
[   5.7349 ] USB communication failed.Check if device is in recovery
[   5.7778 ] 
[   5.7805 ] tegradevflash_v2 --iscpubl
[   5.7828 ] Cannot Open USB

Hardware:
The flash port (usb0) of our costom board is not use type-C, and designed forllowing the below diagram which from the <Jetson_AGX_Xavier_Series_OEM_Product_Design_Guide.pdf>.

DTB:
We worked on the L4T32.5.0, and has changed the dts part following this article.

Is your host machine a VM?

No, it’s a x86-64 physical machine

Is your host able to flash AGX devkit?

Yes, it can flash the devkit.

Have you compare your design to reference carrier P2822 schematic? What’s the difference between it and P2822 on USB part?

On USB part, the difference between our design and P2822 is the typc-C controller.
We remove the type-C part of P2822, and follow the guide of OEM Design Guide USB part, change it to USB Micro AB as the follow:
usb_micro_ab

Have you checked if it is in recovery mode? How do you enter recovery mode on your custom design?

Hi Trumany
Thanks for your reply.

My flash procedure is as below, and can also see in the host log:

  1. Get the device into rovery mode:
    Press recovery button and hold on, then press power or reset button, then release all button.
    Check it on the host side with command: “lsusb”, we can see the device is in recovery mode.
$ lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 064f:2af9 WIBU-Systems AG 
Bus 001 Device 011: ID 0955:7019 NVidia Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  1. Flash the device with the following command on the HOST:
sudo ./flash.sh jetson-agx-xavier-devkit mmcblk0p1
  1. Flash command run error: “Cannot Open USB”, I check the device whether in recovery mode on the host, but there is no device at all.
    Currently the device can not be operated, and there is no output on HDMI.
$ lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 064f:2af9 WIBU-Systems AG 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hi @WayneWWW @Trumany
Any suggestion?

Please dump the uart log and see what got show on device side when “cannot open usb” error happened.

Hi @WayneWWW
I have upload the host and device log of the entire flash process(reference 1#), the device log is named as: xavier-device_flash_log_20220331.log.
but I cannot get any valid infomation from it

I’m closing this topic due to there is no update from you for a period, assuming this issue was resolved.
If still need the support, please open a new topic. Thanks

Hi,

Can you use devkit to compare the flash uart log ?

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