Skip to content

Instantly share code, notes, and snippets.

@dataslayermedia
Last active November 27, 2024 03:33
Show Gist options
  • Save dataslayermedia/714ec5a9601249d9ee754919dea49c7e to your computer and use it in GitHub Desktop.
Save dataslayermedia/714ec5a9601249d9ee754919dea49c7e to your computer and use it in GitHub Desktop.
Install Coral AI PCIe Edge TPU on Raspberry Pi 5
#!/bin/bash
cd /
sudo apt update
echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
sudo apt-get update
sudo apt-get install libedgetpu1-std
sudo apt install -y devscripts debhelper
sudo apt install dkms
sudo apt-get install dh-dkms
# Clone the Gasket driver repository
sudo git clone https://github.com/google/gasket-driver.git
# Change directory to the cloned repository
cd gasket-driver
# Build the Gasket driver package
sudo debuild -us -uc -tc -b
# Go back to the parent directory
cd ..
# Install the built Gasket driver package
sudo dpkg -i gasket-dkms_1.0-18_all.deb
sudo sh -c "echo 'SUBSYSTEM==\"apex\", MODE=\"0660\", GROUP=\"apex\"' >> /etc/udev/rules.d/65-apex.rules"
sudo groupadd apex
sudo adduser $USER apex
# Update the boot configuration for Raspberry Pi
echo "kernel=kernel8.img" | sudo tee -a /boot/firmware/config.txt
# Back up the Device Tree Blob (DTB)
sudo cp /boot/firmware/bcm2712-rpi-5-b.dtb /boot/firmware/bcm2712-rpi-5-b.dtb.bak
# Decompile the DTB into a DTS file
sudo dtc -I dtb -O dts /boot/firmware/bcm2712-rpi-5-b.dtb -o ~/test.dts
# Modify the Device Tree Source (DTS)
sudo sed -i '/pcie@110000 {/,/};/{/msi-parent = <[^>]*>;/{s/msi-parent = <[^>]*>;/msi-parent = <0x67>;/}}' ~/test.dts
# Recompile the DTS back into a DTB
sudo dtc -I dts -O dtb ~/test.dts -o ~/test.dtb
# Replace the old DTB with the new one
sudo mv ~/test.dtb /boot/firmware/bcm2712-rpi-5-b.dtb
sudo reboot now
@19leva89
Copy link

19leva89 commented Jul 5, 2024

When I use this instruction https://pineboards.io/blogs/tutorials/how-to-configure-the-google-coral-edge-tpu-on-the-raspberry-pi-5 I also get an warning when Import the repository GPG key:

 curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
100  2659  100  2659    0     0   9308      0 --:--:-- --:--:-- --:--:--  9297
OK

@19leva89
Copy link

19leva89 commented Jul 6, 2024

In the morning, with a fresh head and new thoughts, I installed a new clean Linux raspberrypi 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux and did everything as written in https://pineboards.io/blogs/tutorials/how-to-configure-the-google-coral-edge-tpu-on-the-raspberry-pi-5 and wow, everything worked!

pi@raspberrypi:~ $ ls /dev/apex_*
/dev/apex_0  /dev/apex_1

@alloydas
Copy link

alloydas commented Jul 6, 2024

In the morning, with a fresh head and new thoughts, I installed a new clean Linux raspberrypi 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux and did everything as written in https://pineboards.io/blogs/tutorials/how-to-configure-the-google-coral-edge-tpu-on-the-raspberry-pi-5 and wow, everything worked!

pi@raspberrypi:~ $ ls /dev/apex_*
/dev/apex_0  /dev/apex_1

Hello, @19leva89 I have completed that step and now when I am going to install Pycoral I cannot install it have you tried this one? I want to run Ultralytics YOLO v8.

Thanks in advance

@19leva89
Copy link

19leva89 commented Jul 6, 2024

In the morning, with a fresh head and new thoughts, I installed a new clean Linux raspberrypi 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux and did everything as written in https://pineboards.io/blogs/tutorials/how-to-configure-the-google-coral-edge-tpu-on-the-raspberry-pi-5 and wow, everything worked!

pi@raspberrypi:~ $ ls /dev/apex_*
/dev/apex_0  /dev/apex_1

Hello, @19leva89 I have completed that step and now when I am going to install Pycoral I cannot install it have you tried this one? I want to run Ultralytics YOLO v8.

Thanks in advance

No I haven't tried that, I use Home Assistant with Frigate

@mikegapinski
Copy link

mikegapinski commented Jul 6, 2024 via email

@alloydas
Copy link

alloydas commented Jul 9, 2024

Jeff Geerling has a great article for PyCoral with Docker, very easy setup: https://www.jeffgeerling.com/blog/2023/testing-coral-tpu-accelerator-m2-or-pcie-docker Wysyłane z aplikacji Outlook dla systemu iOShttps://aka.ms/o0ukef

________________________________ Od: 19leva89 @.> Wysłane: Saturday, July 6, 2024 9:52:46 AM Do: 19leva89 @.> DW: Comment @.> Temat: Re: dataslayermedia/coral-ai-pcie-edge-tpu-raspberrypi-5-setup @19leva89 commented on this gist.
________________________________ In the morning, with a fresh head and new thoughts, I installed a new clean Linux raspberrypi 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux and did everything as written in https://pineboards.io/blogs/tutorials/how-to-configure-the-google-coral-edge-tpu-on-the-raspberry-pi-5 and wow, everything worked! @.
:~ $ ls /dev/apex_* /dev/apex_0 /dev/apex_1 Hello, @19leva89https://github.com/19leva89 I have completed that step and now when I am going to install Pycoral I cannot install it have you tried this one? I want to run Ultralytics YOLO v8. Thanks in advance No I haven't tried that, I use Home Assistant with Frigate — Reply to this email directly, view it on GitHubhttps://gist.github.com/dataslayermedia/714ec5a9601249d9ee754919dea49c7e#gistcomment-5112804 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAHDCBYOEBG3IHFHCKJLCR3ZK6O47BFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVEYTENZVGYZDEMJUU52HE2LHM5SXFJTDOJSWC5DF. You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you @mikegapinski that solution works for me.

Thanks a lot

@marcoscunha
Copy link

Hi all,

I have the Dual Coral TPU with Pineberry board and a raspberry pi 5.
The kernel version is 6.6.31+rpt-rpi-v8 and the distro is the Debian Bookworm Lite.

Changing the DTS of msi-parent of pcie@11000 from 0x027 to 0x66 or 0x67 did not work for me.
I need indeed to change it to 0x6e, which is the value on phandle, to make it works.

Thanks for this discussion!

@marcoscunha
Copy link

Hello,

I rollback the modifications made on my own to DTS to keep raspberry pi's original version.

I want to test device tree overlay proposed by the supplier.

I just add the line dtoverlay=pineboards-hat-ai on /boot/firmware/config.txt,

If you have a kernel greater then 6.6.30 I recommend to use this method instead of modifying the DTS yourself.

Thanks @mikegapinski for the link to the tutorial.

@mikegapinski
Copy link

mikegapinski commented Jul 18, 2024 via email

@lukaszraczylo
Copy link

I can confirm it works with overlays.

      sudo apt-get install vim curl wget -y

      echo "deb [signed-by=/usr/share/keyrings/coral-edgetpu-archive-keyring.gpg] https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list

      curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo gpg --dearmor -o /usr/share/keyrings/coral-edgetpu-archive-keyring.gpg

      sudo apt update

      sudo apt-get install gasket-dkms -y
      sudo apt-get install libedgetpu1-std -y

      echo -e "\nkernel=kernel8.img" | sudo tee -a /boot/firmware/config.txt
      echo -e "\ndtoverlay=pineboards-hat-ai" | sudo tee -a /boot/firmware/config.txt
      reboot

@Zen3515
Copy link

Zen3515 commented Aug 4, 2024

I've been using coral for 2 years now, today my apt update command suddenly failed with

Err:7 https://packages.cloud.google.com/apt coral-edgetpu-stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05

Is it also happend to anyone else?

@zoldaten
Copy link

zoldaten commented Aug 5, 2024

Hi all,

I have the Dual Coral TPU with Pineberry board and a raspberry pi 5. The kernel version is 6.6.31+rpt-rpi-v8 and the distro is the Debian Bookworm Lite.

Changing the DTS of msi-parent of pcie@11000 from 0x027 to 0x66 or 0x67 did not work for me. I need indeed to change it to 0x6e, which is the value on phandle, to make it works.

Thanks for this discussion!

thanks! that only worked for me.
i put my coral tpu m.2 here -
2024-08-05_15h43_32

and was sceptical to start it working but did:
2024-08-05_15h41_28

i also followed steps:

sudo apt-get install devscripts
sudo apt install dh-dkms

*https://github.com/google/gasket-driver/issues/27
git clone https://github.com/google/gasket-driver.git
cd gasket-driver/
debuild -us -uc -tc -b
cd ..
sudo dpkg -i gasket-dkms_1.0-18_all.deb (package u built)


/boot/firmware/cmdline.txt
add:
pcie_aspm=off

and use feranick to work it on python3.11.
have to downgrade numpy==1.26.4

before that i could see device /dev/apex_0 but inference gave me 'Failed to load delegate from libedgetpu.so.1'

@astrizhkin
Copy link

Confirming that the MPW7 hat does not work. The TPU appears at first but after installing the driver it disappears. The Pineberry Pi AI hat works.

MPW7 adapter works with TPU but (at least in my case) only at PCIe Gen1 speed

@mateuszdrab
Copy link

mateuszdrab commented Oct 30, 2024

Just adding a comment to share that modifying the device tree (DTS of msi-parent of pcie@11000 set to 0x67) was the missing bit to make the dual TPU module to work.

My Coral Dual Edge TPU module is inserted into the Magic Smoke M.2 Dual Edge TPU adapter which sits inside the Pineboards Dual M.2 HAT (from the Hailo kit) leaving the smaller 30mm slot where the Hailo was empty, ready for the Raspberry Pi SSD.

I have 2 instances of Frigate running each using one TPU, this is on Ubuntu so I didn't seem to need to add the dtoverlay or kernel entries into the boot config as the page file is already on 4k and the external PCIe port and switch were detected out of box after updating the Pi's firmware.

Thanks for your effort guys.

@lukaszraczylo
Copy link

@mateuszdrab there's no need to modify anything anymore :)
For Pi5's running Coral TPU add following to /boot/firmware/config.txt:

dtparam=pciex1
dtparam=pciex1_gen=3
kernel=kernel8.img
dtoverlay=pineboards-hat-ai

then run:

curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -

echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list


apt-get install -y gasket-dkms libedgetpu1-std

Restart the pi and it magically works 🥳

@mateuszdrab
Copy link

@mateuszdrab there's no need to modify anything anymore :) For Pi5's running Coral TPU add following to /boot/firmware/config.txt:

dtparam=pciex1
dtparam=pciex1_gen=3
kernel=kernel8.img
dtoverlay=pineboards-hat-ai

then run:

curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -

echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list


apt-get install -y gasket-dkms libedgetpu1-std

Restart the pi and it magically works 🥳

That could potentially be the case on Raspberry Pi OS but on Ubuntu it's not or at least was not for me.

Gasket would not install from apt due to some error so had to be compiled from source.

Kernel8 seems not needed since Ubuntu is on 4k page size anyway, dtoverlay did not work since the file is not found but the device is found in lspci anyway

Without changing the device tree msi-parent option the card would be detected by lspci but Frigate was not able to initialize it and I saw interrupt errors in dmesg.

Guessing that Ubuntu is behind a bit with the fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment