HassOS, Frigate, Coral M-2 TPU

Hi,

Short problem :
I can’t get my Coral TPU to be recognized by Frigate.

Long Problem :
Hardware Config :
Raspberry Pi5 (8gb) with HassOS + dual NVME bottom. Booting from 1TB NVME SSD. Coral Google Mini PCIe M.2 Accelerator B/M

Software Config :

  • Core : 2024.11.0
  • Supervisor : 2024.11.2
  • Operating System : 13.2
  • Frontend : 20241106.0
  • Frigate (Full Access) 0.14.1 (Protection Mode disabled)

Constatations :

The TPU is visible by HassOS
image

The TPU is visible by the Frigate container
image

As soon as I enable Detectors config in frigate.yml


I get error in the log and Frigate does not start.

2024-11-08 09:12:49.751099533 [2024-11-08 10:12:49] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as pci
2024-11-08 09:12:49.752190551 [2024-11-08 10:12:49] frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.

What I did so far :
I read all I can find about the error on forums, blogs, etc.
I tried “device: pci:0” config
I basically tried all “possible solution” I found everywhere.

Obviously, I missed something :face_with_raised_eyebrow:

Any help or pointing in the right direction will be highly appreciated

Hi Jean-Christophe,

I thought I heard somewhere that a Coral does not work with arm devices. You may want to search that. I could be wrong, but it has come up in correlation with the HA yellow and HA green which have Pi based arch in them.

Han !!
Damned !!
It is not said in the Frigate documentation :-/
I will dig into that.
Thanks !

So, I didn’t find any information about an incompatibility with ARM device.
In fact, the Frigate documentation mentions Raspberry installation so I guess it should be OK.
I’m still in the same position with my issue :-/

Running HAOS?

Yes. I am.

BUT, I found a solution a few days ago. Not completely stable, for now, and don’t know if my “unstability” is related or not.
Any way, here is what I found.

The issue was due to a Kernel update in Raspberry Pi5.
The solution is here under.
https://forums.raspberrypi.com/viewtopic.php?t=363682&sid=cb59b026a412f0dc041595951273a9ca&start=25

Add

dtoverlay=pciex1-compat-pi5,no-mip
dtoverlay=pcie-32bit-dma-pi5

to config.txt file.

I also added

dtoverlay=pciex1_gen=3

to force gen3 speed on my NVMe SSD. Not sure it changes something here.

If you do an update of HAOS, this all might disappear…
Be prepared for that.

1 Like