Help getting USB Coral TPU working on docker/unraid?

[shadow7412]

I'm having trouble getting frigate to detect my TPU.

Attempting to load TPU as usb
NoEdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.

The full error is exactly the same as here.

So I did some investigation.

Here is an lsusb on the host before plugging it in.

root@Lime:/mnt/user/steven/coral_example# lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 003: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 007 Device 002: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0463:ffff MGE UPS Systems UPS
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
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 003: ID 048d:8295 Integrated Technology Express, Inc. ITE Device(8595)
Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And after (emphasis added to bring attention to the change);

root@Lime:/mnt/user/steven/coral_example# lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 003: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 007 Device 002: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 006: ID 1a6e:089a Global Unichip Corp.  <-----------------
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0463:ffff MGE UPS Systems UPS
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
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 003: ID 048d:8295 Integrated Technology Express, Inc. ITE Device(8595)
Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It coming up as that is apparently expected behaviour (according to google-coral/edgetpu#536) and it's supposed to change vendor id after the first inference.

So, with that done, let's fire up a docker container so I can have a debian environment to run the examples. I'll just install some helpful stuff too.

root@Lime:/mnt/user/steven/coral_example# docker run --rm -itv /dev/bus/usb:/dev/bus/usb debian
root@f3024df7d7a6:/# apt-get update && apt-get install git curl usbutils gpg

[OUTPUT TRUNCATED]

done.
root@f3024df7d7a6:/# lsusb

root@f3024df7d7a6:/# lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller
Bus 007 Device 003: ID 0781:5571 SanDisk Cruzer Fit
Bus 007 Device 002: ID 1d6b:0104 PiKVM Composite KVM Device
Bus 007 Device 001: ID 1d6b:0002 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller
Bus 006 Device 006: ID 1a6e:089a  <-----------------
Bus 006 Device 001: ID 1d6b:0003 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller
Bus 005 Device 002: ID 0463:ffff EATON Eaton 5P
Bus 005 Device 001: ID 1d6b:0002 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller
Bus 004 Device 001: ID 1d6b:0003 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller
Bus 003 Device 001: ID 1d6b:0002 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller
Bus 002 Device 001: ID 1d6b:0003 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller
Bus 001 Device 003: ID 048d:8295 ITE Tech. Inc. ITE Device(8595)
Bus 001 Device 002: ID 8087:0a2b   
Bus 001 Device 001: ID 1d6b:0002 Linux 6.1.106-Unraid xhci-hcd xHCI Host Controller

As you can see, the device is still there. It is interesting that the name has disappeared. I'm pretty sure this is the reason frigate can't detect the dongle. Has anyone else seen this?

Thanks.

[mimainka]

Usually the name of the coral changes after its been touched the first time.
So that your ID is staying 1a6e:089a indicates, it hasnt initialised yet.
I think I followed the following steps (but Im on a proxmox server) on the server itself and then it was initialised:
https://coral.ai/docs/accelerator/get-started/#runtime-on-linux

[NickM-27]

Your understanding is incorrect, Frigate does initialize the USB coral on first inference, just like the examples

[mimainka]

Then my only guess would be a bad cable or not enough power from the usb port.

[shadow7412]

Your understanding is incorrect, Frigate does initialize the USB coral on first inference, just like the examples

Good to hear. What about the differences between lsusb inside and outside of docket? Do you see the same thing on a working setup?

[NickM-27]

Should be Google Inc as the name, not sure why you don't see a name

[mimainka]

It should also have
ID 18d1:9302

in the mentioned setup, the ID stays like the uninitialized one.

[towingie]

mine perfectly work with following compose options enabled:

services:
  figate:
      privileged: true
      ...
      - type: bind
        source: /dev/bus/usb
        target: /dev/bus/usb

not worked for me w/o them

[shadow7412]

I was under the impression that either the privileged flag or binding the usb directory should both have worked in isolation. It would seem I didn't try using both at the same time.

Thanks for your succinct example :)