Thanks for your replies and keeping us updated, appreciate it!
1 Like
@Seeed_Seraphina I have just flashed JP6 and the USB A ports are not working again. Is this a known issue again?
I can ssh into the board, dmesg output below if it’s useful.
sudo dmesg | grep -i USB
[ 0.097660] usbcore: registered new interface driver usbfs
[ 0.097686] usbcore: registered new interface driver hub
[ 0.097703] usbcore: registered new device driver usb
[ 0.227343] usbcore: registered new interface driver asix
[ 0.227363] usbcore: registered new interface driver ax88179_178a
[ 0.227381] usbcore: registered new interface driver cdc_ether
[ 0.227404] usbcore: registered new interface driver net1080
[ 0.227420] usbcore: registered new interface driver cdc_subset
[ 0.227437] usbcore: registered new interface driver zaurus
[ 0.227462] usbcore: registered new interface driver cdc_ncm
[ 0.227484] usbcore: registered new interface driver qmi_wwan
[ 0.227502] usbcore: registered new interface driver cdc_mbim
[ 0.229275] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 0.229560] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 0.230147] usbcore: registered new interface driver cdc_wdm
[ 0.230181] usbcore: registered new interface driver usb-storage
[ 0.230275] usbcore: registered new interface driver option
[ 0.230291] usbserial: USB Serial support registered for GSM modem (1-port)
[ 1.568869] usbcore: registered new interface driver usbhid
[ 1.568875] usbhid: USB HID core driver
[ 1.635266] usbcore: registered new interface driver snd-usb-audio
[ 1.766452] tegra-xusb 3610000.usb: Adding to iommu group 2
[ 1.782063] tegra-xusb 3610000.usb: Firmware timestamp: 2023-02-10 03:48:10 UTC
[ 1.782073] tegra-xusb 3610000.usb: xHCI Host Controller
[ 1.782088] tegra-xusb 3610000.usb: new USB bus registered, assigned bus number 1
[ 1.782836] tegra-xusb 3610000.usb: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000010810
[ 1.782861] tegra-xusb 3610000.usb: irq 124, io mem 0x03610000
[ 1.782994] tegra-xusb 3610000.usb: xHCI Host Controller
[ 1.782998] tegra-xusb 3610000.usb: new USB bus registered, assigned bus number 2
[ 1.783002] tegra-xusb 3610000.usb: Host supports USB 3.1 Enhanced SuperSpeed
[ 1.783278] hub 1-0:1.0: USB hub found
[ 1.783594] hub 2-0:1.0: USB hub found
[ 2.121431] usb 1-3: new high-speed USB device number 2 using tegra-xusb
[ 2.274417] hub 1-3:1.0: USB hub found
[ 6.263663] tegra-xudc 3550000.usb: Adding to iommu group 5
[ 10.498098] usb0: HOST MAC ae:41:1a:0e:f4:8c
[ 10.498108] usb0: MAC ae:41:1a:0e:f4:8d
[ 10.498567] usb1: HOST MAC ae:41:1a:0e:f4:8e
[ 10.498571] usb1: MAC ae:41:1a:0e:f4:8f
[ 10.502224] tegra-xudc 3550000.usb: EP 0 (type: ctrl, dir: out) enabled
[ 10.522386] l4tbr0: port 1(usb0) entered blocking state
[ 10.522407] l4tbr0: port 1(usb0) entered disabled state
[ 10.548994] device usb0 entered promiscuous mode
[ 10.620056] l4tbr0: port 2(usb1) entered blocking state
[ 10.620075] l4tbr0: port 2(usb1) entered disabled state
[ 10.621984] device usb1 entered promiscuous mode
[ 11.059256] fusb301 1-0025: failed to read device id, err : 0xffffff87
[ 11.059265] fusb301 1-0025: fusb301 not support
[ 11.059271] fusb301: probe of 1-0025 failed with error -22
May I ask if you have confirmed that you have successfully replaced the driver? We have tested it and found that the USB is working fine.
I replace the JP5.1.2 BSP I provided on my A603 and install the intel 8265 network card. As soon as I turn on the system, not only was there a wifi logo, but also able to connect to wifi easily without having to install any additional driver for the intel 8265
It’s running fine
1 Like
Oh, no I haven’t. Are there instructions on how to do this? I must have missed it somewhere. Is it possible to do on a running system or do you have to do it pre-flashing?
Have you confirmed that you have replaced the BSP? We can make sure that the connected usbA is working properly
Hi Seraphina,
If you mean this step:
Yes.
To double-check if there was any corruption etc I re-did the entire procedure via the wiki, again, and the same result - no USB A functionality.
This is for a Orin Nano JetPack 6.0, L4T 36.3 using the link in the wiki (https://nv-jetson-images.oss-us-west-1.aliyuncs.com/A603/A603-JP6.0.zip?OSSAccessKeyId=LTAI5tKm7UD2hmuFW85cz42T&Expires=4869959719&Signature=1SFOkIWHlDIaZzCAR2af9%2F4DFj0%3D).
You can see the downloads were from today:
I will attach the initrd log as well.
I appreciate that you are saying it works on your end, but I have followed the wiki twice now and it does not work for me. Can this please be investigated?
Thanks,
Steven
logs.zip (51.9 KB)
The tutorial you are looking at is not for the JP6 version. We have confirmed that if you do not use sudo when replacing the driver, the replacement will not be successful. So we have deliberately used sudo for all the commands in the wiki for A603 JP6.0.
Hi Seraphina,
I have been using the correct tutorial just pasted that image as it’s more or less the same step each time. Apologies for the confusion.
From the logs I provided, you can see I did use sudo and typed ‘A’ to replace the files:
steven@acer-linux:~/Downloads/NVIDIA/JetsonOrinNano$ sudo unzip A603-JP6.0.zip
Archive: A603-JP6.0.zip
replace Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
inflating: Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi
inflating: Linux_for_Tegra/bootloader/tegra234-mb1-bct-gpio-p3767-dp-a03.dtsi
inflating: Linux_for_Tegra/kernel/dtb/tegra234-p3768-0000+p3767-0003-nv.dtb
inflating: Linux_for_Tegra/kernel/dtb/tegra234-p3768-0000+p3767-0004-nv.dtb
inflating: Linux_for_Tegra/kernel/dtb/tegra234-p3768-0000+p3767-0000-nv.dtb
inflating: Linux_for_Tegra/kernel/dtb/tegra234-p3768-0000+p3767-0001-nv.dtb
inflating: Linux_for_Tegra/kernel/dtb/tegra234-p3768-0000+p3767-0000-dynamic.dtbo
inflating: Linux_for_Tegra/kernel/Image
creating: Linux_for_Tegra/rootfs/usr/lib/modules/5.15.136-tegra/kernel/drivers/net/wireless/intel/
creating: Linux_for_Tegra/rootfs/usr/lib/modules/5.15.136-tegra/kernel/drivers/net/wireless/intel/iwlwifi/
inflating: Linux_for_Tegra/rootfs/usr/lib/modules/5.15.136-tegra/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
creating: Linux_for_Tegra/rootfs/usr/lib/modules/5.15.136-tegra/kernel/drivers/net/wireless/intel/iwlwifi/mvm/
inflating: Linux_for_Tegra/rootfs/usr/lib/modules/5.15.136-tegra/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko
creating: Linux_for_Tegra/rootfs/usr/lib/modules/5.15.136-tegra/kernel/drivers/net/wireless/intel/iwlwifi/dvm/
inflating: Linux_for_Tegra/rootfs/usr/lib/modules/5.15.136-tegra/kernel/drivers/net/wireless/intel/iwlwifi/dvm/iwldvm.ko
So from what I’m reading, I’m following the instructions exactly but the USBs are not working. The BSP on the previous wiki were incorrect, could this not be the case again? There’s nothing else I can do from my side.
Today we try again to flash JP6 using the exact steps as documented in the wiki . After flashing, we can still use USB normally. Please refer to the GIF I sent. I have a keyboard and mouse connected and both work fine
I suggest you use the following method to check if your driver program has been successfully replaced. Compare the files before and after the replacement to see if they are different (refer to the filenames that appeared during our replacement process).
1 Move the downloaded peripheral drivers from before into the same folder with NVIDIA drivers. Now you will see three compressed files in the same folder. Open a terminal in this folder
2 Run this command to check the filenames in the path before the replacement. See if they match the ones shown in the picture below.
$ sha1sum ./Linux_for_Tegra/kernel/Image
3 Following the step3 and step4 in wiki. Use sudo to replace the driver
4 Run the command again to check if the current filenames are different from the filenames before the replacement. If they are different, it indicates that the replacement was successful.
$ sha1sum ./Linux_for_Tegra/kernel/Image
Thanks Seraphina, really appreciate the effort in trying to resolve this.
So I did exactly what you described above, got the same sha outputs as yourself - i.e. initially before replacement:
sha1sum ./Linux_for_Tegra/kernel/Image
ff68c1a061ed75cee73afc4fd98f89efa01e287f ./Linux_for_Tegra/kernel/Image
and then after sudo unzip A603-JP6.0.zip:
sha1sum ./Linux_for_Tegra/kernel/Image
601d40816e99976ed84c55adb7e11b4d685c4909 ./Linux_for_Tegra/kernel/Image
Then created the default user, flashed board etc.
Booted device and still no USB. Tried my other A603 board as I have two, same result.
Is there any hardware differences in the recent PCB builds etc? I’m really struggling here, I need this to work and don’t have a lot of time to keep dedicating to it.
I know from your end it must be really frustrating for you because it works, but it doesn’t for me.
I can ssh into the board, enable VNC etc. HDMI works.
Is there any way to install the USB driver live on a running jetson, that may be the last thing to try.
Thanks for the image, I have the same version. Really strange.
I have contacted you via message and we can communicate in it
Hello –
Several months ago I was able to successfully flash my Orin NX on an A603 to JP 5.1.2 using the steps and files in the wiki.
This week I tried to follow the steps in the wiki (on the same computer, just a fresh download) and flashing fails. On the host side, it times out with “waiting for target to boot up” and the device side serial logs end with:
enable_remote_access
enable remote access
insmod /lib/modules/5.10.120-tegra/kernel/drivers/mtd/mtd.ko
insmod /lib/modules/5.10.120-tegra/kernel/drivers/mtd/devices/qspi_mtd.ko
[ 8.458762] qspi_mtd spi6.0: MX25U51279G (65536 Kbytes)
[ 8.461874] qspi_mtd spi6.0: mtd .name = spi6.0, .size = 0x4000000 (64MiB) .erasesize = 0x00010000 (64KiB) .numeraseregions = 0
[ 8.476432] 1 fixed-partitions partitions found on MTD device spi6.0
[ 8.479900] Creating 1 MTD partitions on "spi6.0":
[ 8.484876] 0x000000000000-0x000004000000 : "Whole_flash0"
insmod /lib/modules/5.10.120-tegra/kernel/drivers/spi/spi-tegra210-qspi.ko
insmod /lib/modules/5.10.120-tegra/kernel/drivers/hwmon/pwm-fan.ko
[ 8.513903] using random self ethernet address
[ 8.514029] using random host ethernet address
[ 8.516718] Mass Storage Function, version: 2009/09/11
[ 8.517339] LUN: removable file: (no medium)
[ 8.522899] LUN: removable file: (no medium)
[ 8.527189] LUN: removable file: (no medium)
[ 8.531671] LUN: removable file: (no medium)
Add /dev/nvme0n1
[ 8.538683] rndis0: HOST MAC ba:61:4d:39:d6:e1
[ 8.541411] rndis0: MAC 52:49:86:57:7b:b1
[ 8.545729] tegra-xudc 3550000.xudc: EP 0 (type: ctrl, dir: out) enabled
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-5.0# [ 10.550789] tegra-xusb 3610000.xhci: entering ELPG done
Can you help me figure out what is going on? For what its worth, I’m able to flash to jetpack 6 using the instructions in the wiki but I need jetpack 5.1.2 for my project.
Are there any successes here? I have the same problem
There are several reasons why you may encounter WAITING FOR BOOT, and it is recommended that you troubleshoot them:
- Check if you have entered the forced recovery mode.
- Check whether the cable you connect to the linux host is a data cable.
- check if there is a micro SD card slot on your module; if there is, it is not compatible with the carrier board.
- cross-test with other ssd to see if there is a possibility that the ssd is not installed properly, resulting in failure to boot.
Hi Andreas,
Unfortunately I was never able to resolve this and the project I needed it for paused, I RMA’d my carrier boards (without my Jetson module or SSD) with the help of Seeed_Seraphina and using their module and SSD they could demonstrate the USBs working no problem.
So it was either a module or SSD issue, my module was from the Dev Kit and Seraphina also linked a post on the Nvidia forums which could or could not be related: Different charge numbered jetson orin nano's behave differently when writing to QSPI on custom carrier boards - Jetson Orin Nano - NVIDIA Developer Forums but I had no success with that and could not find much else.
Due to other work commitments I did not get to the point of making a post on the Nvidia forums but if you have any success it would be appreciated if you could update this thread.
Sorry I can’t be of more help, hope you get it working.
Steven