Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

mgagv

Hello,

I am using an OAK-D Pro camera with an Orange Pi 5 SBC. I have set the udev rules according to the Troubleshooting guide and verified that I am using a high speed USB 3 cable. I am getting the following error:

RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

Running lsusb | grep 03e7returns the correct output. This error occurs when I run any script that tries to access the camera using DepthAI. What can I do to solve it?

Edit: Here is a sample of the output of dmesg from when I run a python script with depthai:

[ 164.717801] usb 2-1: USB disconnect, device number 3

[ 169.199580] usb 2-1: new high-speed USB device number 4 using ehci-platform

[ 169.347277] usb 2-1: New USB device found, idVendor=03e7, idProduct=2485, bcdDevice= 0.01

[ 169.347284] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 169.347289] usb 2-1: Product: Movidius MyriadX

[ 169.347293] usb 2-1: Manufacturer: Movidius Ltd.

[ 169.347297] usb 2-1: SerialNumber: 03e72485

[ 184.065282] usb 2-1: USB disconnect, device number 4

[ 193.662907] usb 2-1: new high-speed USB device number 5 using ehci-platform

[ 193.810644] usb 2-1: New USB device found, idVendor=03e7, idProduct=2485, bcdDevice= 0.01

[ 193.810651] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 193.810656] usb 2-1: Product: Movidius MyriadX

[ 193.810660] usb 2-1: Manufacturer: Movidius Ltd.

[ 193.810663] usb 2-1: SerialNumber: 03e72485

It looks like it is getting disconnected and connected again every time I run the script.

jakaskerl

Hi mgagv
Can't find the exact numbers, but I think the OrangePi might not be capable to supply 5W+ via USB ports. You should use a Y-adapter and externally power the OAK-D pro.

mgagv It looks like it is getting disconnected and connected again every time I run the script.

The device reconnect under a different bus-id and different mode (booted). That is expected.

Thanks,
Jaka

mgagv

jakaskerl I am using a Y-adapter. The data end is plugged into the Orange Pi's USB 3 port while the power end is connected to a 5V/15 A buck converter which is also powering the Orange Pi. I have verified the converter's output is 5V as expected. Thus I am fairly certain it is not a power issue.

jakaskerl

Hi @mgagv
Which version of depthai are you using? Could you try setting USB2 mode to see if it fixes the problem?
https://docs.luxonis.com/en/latest/pages/troubleshooting/?highlight=maxUsbSpeed#forcing-usb2-communication

Thanks,
Jaka

mgagv

jakaskerl Thank you for your help. We found the issue was with a faulty Y-adapter, replacing it with the adapter from another camera made it work.

Since the Y-adapters are out of stock, do you have any recommendations for alternatives we could use? Preferably ones which are rated for stress/shock as we found the Luxonis Y-adapter to warp over time under static stresses?

jakaskerl

Hi @mgagv
I'd recommend a powered USB hub since the Y adapters (not from Luxonis) aren't really available on the market.
But the adapter is faulty so I see no reason why we wouldn't send you a replacement. We have some left in the office. Would be good if we could also take a look at the faulty one the check where the issue is.

Please write to support@luxonis.com and link this thread there.

Thanks,
Jaka

ShivamSharma

Hi @jakaskerl and @mgagv ,

I think I am facing a similar issue but I am not sure. I am using Oak FFC 3P with a compatible color camera. When I run cam_test.py to check if cameras are working I get the following output:

shivam157@ubuntu:~/.local/lib/python3.10/site-packages/depthai_cli$ DEPTHAI_DEBUG=1 python cam_test.py -cam rgb,c

[2024-06-03 20:53:34.945] [depthai] [info] DEPTHAI_DEBUG enabled, lowered DEPTHAI_LEVEL to 'debug'

[2024-06-03 20:53:34.945] [depthai] [debug] Python bindings - version: 2.26.0.0 from build: 2024-05-25 18:10:44 +0000

[2024-06-03 20:53:34.945] [depthai] [debug] Library information - version: 2.26.0, commit: from , build: 2024-05-25 16:34:58 +0000, libusb enabled: true

[2024-06-03 20:53:34.948] [depthai] [debug] Initialize - finished

[2024-06-03 20:53:35.080] [depthai] [debug] Resources - Archive 'depthai-bootloader-fwp-0.0.28.tar.xz' open: 3ms, archive read: 130ms

DepthAI version: 2.26.0.0

DepthAI path: /home/shivam157/.local/lib/python3.10/site-packages/depthai.cpython-310-aarch64-linux-gnu.so

[2024-06-03 20:53:35.272] [host] [debug] Device - OpenVINO version: universal

[14442C10E14FCBD600] [1.2.1] [1717462415.272] [host] [debug] Device - BoardConfig: {"camera":[],"emmc":null,"gpio":[],"imu":null,"logDevicePrints":true,"logPath":null,"logSizeMax":null,"logVerbosity":null,"network":{"mtu":0,"xlinkTcpNoDelay":true},"nonExclusiveMode":false,"pcieInternalClock":null,"sysctl":[],"uart":[],"usb":{"flashBootedPid":63037,"flashBootedVid":999,"manufacturer":"","maxSpeed":4,"pid":63035,"productName":"","vid":999},"usb3PhyInternalClock":null,"uvc":null,"watchdogInitialDelayMs":null,"watchdogTimeoutMs":null}

libnop:

0000: b9 12 b9 07 81 e7 03 81 3b f6 81 e7 03 81 3d f6 04 bd 00 bd 00 b9 02 00 01 ba 00 be be bb 00 bb

0020: 00 be be be be be be 01 00 bb 00 be be

[2024-06-03 20:53:35.681] [depthai] [debug] Resources - Archive 'depthai-device-fwp-24a3b465b979de3f69410cd225914d8bd029f3ba.tar.xz' open: 3ms, archive read: 732ms

[2024-06-03 20:53:36.585] [depthai] [debug] Searching for booted device: DeviceInfo(name=1.2.1, mxid=14442C10E14FCBD600, X_LINK_BOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS), name used as hint only

Traceback (most recent call last):

File "/home/shivam157/.local/lib/python3.10/site-packages/depthai_cli/cam_test.py", line 252, in <module>

with dai.Device(*dai_device_args) as device:

RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

shivam157@ubuntu:~/.local/lib/python3.10/site-packages/depthai_cli$

sudo dmesg -w gives the following output which looks like that the Oak FFC 3P is connecting and disconnecting frequently:

[21030.026142] usb 1-2.4: USB disconnect, device number 40

[21035.338527] usb 2-1.4: new SuperSpeed USB device number 26 using tegra-xusb

[21064.925747] usb 2-1.4: Disable of device-initiated U1 failed.

[21064.928397] usb 2-1.4: Disable of device-initiated U2 failed.

[21065.633440] usb 2-1.4: USB disconnect, device number 26

[21065.709663] usb 1-2.4: new high-speed USB device number 41 using tegra-xusb

[21287.562145] usb 1-2.4: USB disconnect, device number 41

[21292.654777] usb 2-1.4: new SuperSpeed USB device number 27 using tegra-xusb

[21364.204297] usb 2-1.4: USB disconnect, device number 27

[21364.845038] usb 1-2.4: new high-speed USB device number 42 using tegra-xusb

[21423.754121] usb 1-2.4: USB disconnect, device number 42

[21428.812396] usb 2-1.4: new SuperSpeed USB device number 28 using tegra-xusb

[21477.454102] usb 2-1.4: Disable of device-initiated U1 failed.

[21477.456751] usb 2-1.4: Disable of device-initiated U2 failed.

[21478.162747] usb 2-1.4: USB disconnect, device number 28

[21478.239012] usb 1-2.4: new high-speed USB device number 43 using tegra-xusb

[21530.506233] usb 1-2.4: USB disconnect, device number 43

[21535.686397] usb 2-1.4: new SuperSpeed USB device number 29 using tegra-xusb

[21543.262726] usb 2-1.4: Disable of device-initiated U1 failed.

[21543.265615] usb 2-1.4: Disable of device-initiated U2 failed.

[21543.965698] usb 2-1.4: USB disconnect, device number 29

[21544.041770] usb 1-2.4: new high-speed USB device number 44 using tegra-xusb

[27252.874280] usb 1-2.4: USB disconnect, device number 44

[27262.311255] usb 1-2.4: new high-speed USB device number 45 using tegra-xusb

[28096.650123] usb 1-2.4: USB disconnect, device number 45

[28106.092378] usb 1-2.4: new high-speed USB device number 46 using tegra-xusb

[28663.946175] usb 1-2.4: USB disconnect, device number 46

[28674.442159] usb 1-2.1: USB disconnect, device number 4

[28681.834452] usb 1-2.4: new low-speed USB device number 47 using tegra-xusb

Can you please help me debug? I have set the Udev rules on Jetpack 6 according to the documentation. So I don't think that is the cause.

jakaskerl

Hi @ShivamSharma
I think it might be power related. If the udevs are set, the depthai should find the USB3 device. FFC3p eat more power so I think the jetson is unable to supply it. Can you externally power it via Y-adapter or something similar (powerd USB hub)?

Thanks,
Jaka

ShivamSharma

Thank you for your reply, @jakaskerl.

I have tried to power the FFC 3P with both Jetson Orin and the adapter that came with the Oak FFC 3P, but I still get this error. I have only connected one color camera to the 4-lane MIPI port of the Oak module. Other than the Oak module, only a mouse and keyboard are connected to the Jetson Orin developer kit.

I haven't tried powered USB hub. I will buy it and see if it works. Also, should I keep the Jetson Orin in 15V mode or change it?

jakaskerl

ShivamSharma
I think there are power saving modes running in the background U1/U2 (U3). Disable them as they might be interfering with device communication.

Thanks,
Jaka

ShivamSharma

@jakaskerl

I changed the brown flat wires to the blue ones and now the 4 lane MIPI port is working. Was the issue faulty wire?

Can you answer a few questions for me?
1. Are the right and left port on the Oak FFC 3P only used with mono cameras?

Are we supposed to use only the blue flat wires with the Oak module?

jakaskerl

ShivamSharma
I might have been a short-circuit then? That would explain why the device wouldn't boot up, but I'd assume you would get overcurrent warnings when powering the device with Jetson.

ShivamSharma 1. Are the right and left port on the Oak FFC 3P only used with mono cameras?

They can be used for color cameras. IIRC we use 2-lane MIPI most of the time even on color cameras. 4- lanes is used for high resolutions (12MP/32MP..).

ShivamSharma Are we supposed to use only the blue flat wires with the Oak module?

Shouldn't matter as long as the pin numbers are the same and all connections are proper.

Thanks,
Jaka

ShivamSharma

It may be that I installed DepthAi- python from source after encountering this error and it solved all the software related issue I was facing such as dependencies. I don't think it was faulty wire.

Again, thanks for your help.