[Detector Support]: Google Coral TPU Enabled but not detected in Docker container (tried both PCIe m.2 / USB) #13489
Unanswered
luckylinux
asked this question in
Detector Support
Replies: 2 comments 4 replies
-
I'd suggest getting a shell in the container and running lspci and see what it shows lsusb from inside the container shows that the full IDs don't seem to be getting passed through |
Beta Was this translation helpful? Give feedback.
4 replies
-
Did you manage to resolve your issue? I noticed in the log that it says, "bInterfaceSubClass 1 Device Firmware Update." I'm experiencing the same problem after a brief power interruption from my electricity supplier. I believe this indicates that the Coral needs a firmware update, but I'm not entirely sure. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Unfortunately I could (and still cannot) get the Google Coral TPU Working Correctly on my Rock 5B SBC (aarch64 / arm64).
I tried both PCIe (m.2 A+E Key) as well as USB.
There might be something to do with Kernel Version and/or Things that are aarch64/arm64 Specific.
Running in Podman Container (Podman 4.9.4) on top of Debian Bookworm 12 aarch64/arm64. I also tried with
privileged: true
, but that didn't make a difference.Power Supply for this SBC is UNDERSIZED. I had to use a Raspberry Pi 3 AC Power Adapter which is only like 15W ... this Rock 5B might take around 30W if used fully. I never had an Issue, but I cannot exclude that it's not causing Issues now with the Coral ... Unfortunately the Rock 5B USB-C PD is very sensitive and I don't have a PSU that works well otherwise (I tried a Lenovo Notebook Adapter and it just causes the Rock 5B to continuously reboot 😞).
Version
0.14.1-f4f3cfa
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Debian
Install method
Docker Compose
Object Detector
Coral
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Kernel: (patched for RockChip RK3588 Support)
Linux rock5b-01 6.6.41-1-arm64 #1 SMP PREEMPT Debian 6.6.41-1 (2024-07-18) aarch64 GNU/Linux
modinfo gasket
:modinfo apex
:Gasket installed by building from Source https://github.com/KyleGospo/gasket-dkms.git (this includes a few Changes needed to make it work with the latest Kernel).
libedgetpu
Installed:(also tried
libedgetpu1-max_16.0tf2.16.1-1_arm64.deb
on another Rock 5B System - Same Issue)Is there a specific Version of
libedgetpu
that needs to be installed, so that it's compatible with the one in the Frigate Docker Container ???cat /etc/udev/rules.d/60-coral-tpu.rules
:HOST:
ls -l /dev/apex*
:HOST:
ls -l /dev/bus/usb/*
:lspci -nn -vvv
(only relevant Section shown):lsusb -vvv
(only relevant Section shown):Groups of the
podman
User (the one running Podman Containers including Frigate):Info as seen from INSIDE the Container:
Beta Was this translation helpful? Give feedback.
All reactions