Failed to change USB3 to compliance test mode

HuiW · January 19, 2022, 3:32am

Hi

We still have problem to change USB3 to compliance mode by following the tuning guide.

We have a customized carrier board and the USB 3 port w/o hub.

Due to the previous created topic as below is closed, we create a new topic.

Update more information below.
The USB3 could be changed to compliance test mode by the command, as the USB3 with a device.

The USB3 could not be entered to compliance test mode by command, as the USB3 without a device. (Doing SI test, without a device connected.)

Also, we have to test SI now and Jp4.6.1 is not ready yet.

Thank you for any advice,

WayneWWW · January 19, 2022, 3:55am

Hi,

Which jetpack version is in use now?

HuiW · January 19, 2022, 5:42am

It’s JetPack_4.5.1.

WayneWWW · January 19, 2022, 6:45am

HI HuiW,

Jetpack4.5.1 usb firmware has problem so that it cannot run compliance mode.

HuiW · January 19, 2022, 6:57am

Hi WayneWWW,

When is Jp4.6.1 ready?
Is it possible to use another usb firmware of different JP version？
Which version?

Thank you,

WayneWWW · January 19, 2022, 7:07am

Hi,

There is no jetpack4.6.1. I mean rel-32.6.1 which is jetpack4.6.

HuiW · January 19, 2022, 7:14am

Hi WayneWWW,

Thank you for your prompt support.
Due to it takes time to modify BSP for customized carried board, is it possible to use jp4.6 USB firmware on Jp 4.5.1 for testing?

Thank you,

WayneWWW · January 19, 2022, 7:15am

Yes, you need to replace the firmware in initrd and reflash the board.

 mkdir initrd; cd initrd;
   sudo gunzip -c ../l4t_initrd.img.orig | sudo  cpio -i
   sudo cp ../xusb_sil_prod_fw-new lib/firmware/tegra19x_xusb_firmware 
   sudo find . | sudo cpio --quiet -H newc -o | sudo gzip -9 -n > ../l4t_initrd.img

HuiW · January 19, 2022, 7:22am

Thank you so much.
We will test it.

system · February 9, 2022, 5:45am

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