• DepthAI-v2

  • Using Luxonis preped RPI OS images (V10)

Hi all,

I am having some problems with the RPI OS images prepared by Luxonis for my OAK-D CM4 PoE.

I had some troubles with the communcations from the internal CM4 module to the RCV2.

When I execute python3 -c "import depthai; print(depthai.Device.getAllAvailableDevices())" it returns nothing [] . But I expected the something related to the RCV2 device.

I tried a few things but ended up flashing the CM4 with a fresh image found in this documentation: https://docs.luxonis.com/hardware/platform/deploy/to-rpi/ I downloaded V10 from the drives link: https://drive.google.com/drive/folders/1O50jPpGj_82jkAokdrsG--k9OBQfMXK5?usp=sharing .

With the fresh image communication worked again. But when I did an sudo apt update and sudo apt upgrade a reboot followed by an sudo apt autoremove which suggested to remove the following components. The following packages were automatically installed and are no longer required: chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra libcamera-apps libcamera0.1 libpisp0.0.1 libssl1.1 libwpe-1.0-1 libwpebackend-fdo-1.0-1 linux-headers-6.1.0-13-arm64 linux-headers-6.1.0-13-common qml-module-qtgraphicaleffects Use 'sudo apt autoremove' to remove them. The following packages have been kept back: arandr lxinput raspberrypi-ui-mods raspi-utils wf-panel-pi

a full power cycle later the connection to the RCV2 was again broken. Now my question is did the autoremove delete some components that are needed by the DepthAI library or am I not supposed to use the apt update and upgrade commands on this image?

    legow00
    What does lsusb out give you? Make sure jumper for USBBOOT is set to DIS.

    Thanks,
    Jaka

      5 days later

      Hi @jakaskerl,

      lsusb gives me Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The jumper is in the DIS position. Sorry for my late response.

      When I do lsusb with a fresh image I get:

      Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

      Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

      Bus 001 Device 002: ID 03e7:2485 Intel Movidius MyriadX

      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

        legow00

        legow00 Bus 001 Device 002: ID 03e7:2485 Intel Movidius MyriadX

        Good, the OAK-SOM is discoverable physically. Try python3 -c "import depthai; print(depthai.Device.getAllConnectedDevices())"

        Thanks
        Jaka

            @jakaskerl

            python3 -c "import depthai; print(depthai.Device.getAllConnectedDevices())"returns the following: []

              legow00
              Hmm. What do you get if you try to open a device using dai.Device()? Like running a simple rgb_preview example? I'm interested in the dmesg output when you run the script. Perhaps a if you run it using XLINK_LEVEL=debug and post the results. This is very strange, can't remember seeing it before.

              Thanks,
              Jaka

                @jakaskerl

                I tried to run the RGB Preview (https://docs.luxonis.com/software/depthai/examples/rgb_preview/) and the Python script retured:

                Traceback (most recent call last):

                File "/home/pi/Desktop/rgb_preview.py", line 24, in <module>

                with dai.Device(pipeline) as device:

                ^^^^^^^^^^^^^^^^^^^^

                RuntimeError: No available devices

                The output of dmesg can be found here: https://pastebin.com/6kYZ7QXp

                Setting XLINK_LEVEL=debug flag results in the same output as above

                I just checked my DepthAI Python version and I am at version 2.22.0.0, should I update to the most recent package in pip? Version 2.30.0.0.

                  legow00
                  Dmesg shows no indication that the HW detects the USB device.

                  Let me check what's broken upon update & I'll get back to you.

                  Thanks,
                  Jaka

                    legow00 legow00
                    Tried on a CM4 POE with x64 image (V10 I think).

                       12  sudo apt update && sudo apt -y upgrade
   13  lsusb
   14  cat /etc/os-release
   15  sudo apt autoremove
   16  sudo reboot
   17  lsusb
   18  sudo apt autoremove

                    "lsusb" still shows the device is connected.

                    Can you try running systemctl status cm4-rvc2-usb-prepare? Enable if disabled.

                    Thanks,
                    Jaka

                        @jakaskerl

                        I checked systemctl status cm4-rvc2-usb-prepare but this systemd service is enabled and active.

                        I also tried the same commands as you mentioned:

                        12 sudo apt update && sudo apt -y upgrade
                        13 lsusb
                        14 cat /etc/os-release
                        15 sudo apt autoremove
                        16 sudo reboot
                        17 lsusb
                        18 sudo apt autoremove

                        Nothing changed lsusb still returns:

                        Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

                          legow00
                          Hmm, does it work if you try to reflash a fresh POE v10 image? Can you try re-seating the SOM:

                          also check:

                          pi@luxonis:~ $ ls /lib/firmware/renesas/
K2026.mem

pi@luxonis:~ $ ls /usr/sbin | grep upd72020x
rvc2-upd72020x-check-and-init
upd72020x-load

                          Thanks,
                          Jaka

                            @jakaskerl

                            I executed the following commands on a fresh V10 image install:

                            12 sudo apt update && sudo apt -y upgrade
                            13 lsusb
                            14 cat /etc/os-release
                            15 sudo apt autoremove
                            16 sudo reboot
                            17 lsusb
                            18 sudo apt autoremove

                            Still same result as before, lsusb still returns:

                            Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

                            What would be the best practice to remove the SOM while minimizing the risk of damaging the connectors?

                            @jakaskerl

                            I re-seated the SOM and started again with a fresh install of th V10 image.

                            I did multiple sudo apt update && sudo apt -y upgrade, sudo apt autoremove and reboot.

                            The Intel Movidius MyriadX USB device is still detected. RGB example scripts also works!

                            Thanks for your help @jakaskerl ! It was probably a loose or bad connections somewhere in the SOM connectors.

                            @jakaskerl

                            Oops seems like I celebrated to early… after some reboots a pop up in the top right part of the screen showed which notified me of few updates. After these updates the Movidius device was gone again… grrrrr. Is there a way to look at a log file of the last updates executed on this system?