bananapi

The aim is getting google coral M.2 working on banana pi M4

To install drivers for google coral M.2 ideally we can proceed in two ways: compiling the driver as module directly on banana pi through dkms or cross compiling the whole kernel configuring the driver as module. Actually both are not working, see ERRORS section below.

Get the ubuntu server 16.04 image to burn on SD:
https://drive.google.com/open?id=1G4915FPOU4pDzbI0TCFH8wWXUGmNdlkF to upload the image on SD card (at least 8GB) the bpi-tools can be used curl -sL https://github.com/BPI-SINOVOIP/bpi-tools/raw/master/bpi-tools | sudo -E bash - then the command is: sudo bpi-copy <xxxxx.img.zip> <device path ie /dev/sdb>

This image does not include kernel headers useful to compile the driver so is still required compiling the whole kernel from sources (or get headers from this git).

git clone https://github.com/BPI-SINOVOIP/BPI-M4-bsp.git (banana pi kernel sources and other stuff)

banana pi gives a docker with all dependecies installed to easly cross compile the kernel, so you can get the sinovoip docker running:
docker pull sinovoip/bpi-build-linux-4.4:ubuntu16.04

1. before compiling the kernel, coral driver can be added to drivers dir (to compile them as module):
   download and extract deb package (instructions below) or use the version on this git. The version here already includes Makefile and Kconfig I edited to correctly see the module on kernel config menu. Put gasket folder, Makefile e Kconfig in /BPI-M4-bsp/linux-rtk/drivers folder

2. run the docker:
   sudo docker run -v /media:/media -t -i sinovoip/bpi-build-linux-4.4:ubuntu16.04 /bin/bash I'm working on a secondary hdd I can reach mounting /media on the docker

3. build and run kernel configuration menu (I don't know if this is really required. I configured gasket as module by default so maybe building the configuration is still required to update default configuration). Move to /BPI-M4-bsp/ folder and run
   ./build.sh 4 and just exit

4. Build all bsp packages ./build.sh 1
   and exit from docker

5. Update SD card with new compiled packages using BPI-tools Problem: bsp seems to be unable to create a correct BPI-BOOT image,so I'm avoiding to upload that image, pkgs to upload can be selected in /SD/bpi-m4/BPI-m4.conf. Original file is here https://github.com/BPI-SINOVOIP/BPI-files/blob/69594603ab8ceb102d77818982897c00c86d6d15/others/for-bpi-tools/conf/board/bpi-m4.conf, edited file in this git)
   download BPI-tools if you didn't already, edit BPI-M4-bsp/scripts/mk_install_sd.sh, locate sudo bpi-update -d ${DEVICE} add -c bpi-m4.conf, save and move to /BPI-M4-bsp/ folder then:
   ./build.sh 7 SD device is likely to be in /dev/sdb

Download coral drivers (from google support):

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 update

1. apt download gasket-dkms (download the deb package)
2. Unpack and change dir: dpkg-deb -R gasket-dkms_1.0-9_all.deb gasket && cd gasket
3. Copy the src to the correct name/location: sudo cp -r usr/src/gasket-1.0 /usr/src/gasket-dkms-1.0
4. Finally, add and install the driver (here the $(uname -r) should be switched to your 4.9 header, we have tested with 4.19 and cannot commit if everything will work perfectly with 4.9): sudo dkms add gasket-dkms/1.0 --kernelsourcedir=/usr/src/linux-headers-$(uname -r) sudo dkms install gasket-dkms/1.0 --kernelsourcedir=/usr/src/linux-headers-$(uname -r)

ERRORS:

running point 4 from the procedure suggested by google support, raises the errors in make_shell.log and make.log

alternatively running sudo insmod /lib/modules/4.9.119-BPI-M4-Kernel/kernel/drivers/gasket/gasket.ko gives insmod: ERROR: could not insert module /lib/modules/4.9.119-BPI-M4-Kernel/kernel/drivers/gasket/gasket.ko: Invalid parameters with dmesg log in dmesg.log
update 09/01 using modprobe -f, modules are loaded but the device cannot be correctly initialized with this dmesg error:
[ 418.976141] gasket: module_layout: kernel tainted. [ 418.976170] Disabling lock debugging due to kernel taint
[ 423.373659] apex 0000:01:00.0: can’t enable device: BAR 0 [mem 0x00000000-0x00003fff 64bit pref] not claimed
[ 423.373699] apex 0000:01:00.0: BAR 2: no space for [mem size 0x00100000 64bit pref]
[ 423.373712] apex 0000:01:00.0: BAR 2: failed to assign [mem size 0x00100000 64bit pref]
[ 423.373730] apex 0000:01:00.0: BAR 0: assigned [mem 0x98064000-0x98067fff 64bit pref]
[ 423.374483] apex 0000:01:00.0: enabling device (0000 -> 0002)
[ 423.375621] apex 0000:01:00.0: Cannot get BAR2 base address
[ 423.375963] apex 0000:01:00.0: error adding gasket device
[ 423.376161] apex: probe of 0000:01:00.0 failed with error -12

This seems to be a problem with the kernel pci express support http://forum.banana-pi.org/t/bar-0-no-space-for-mem-size-0x200000000-64bit-pref/10418/39