You can buy from Mouser, I see if you select china it says limited availability, so I selected Honk Kong and that seems to have it on stock.
And there is a driver needed to install which I managed to compile install and loaded manually ok with ‘modprobe’.
Are you able to recognize the device using ‘modprobe’?
if so can you elaborate how?
No, just me testing the kernel modules for coral are loading successfully, after testing with mod probe I added them to /etc/modules. However the device is not sensed detected at boot as I am getting the same logs as you, even regardless if the device is plugged in the M2 socket or not.
However It does seem to get power as it gets a little bit warm, and I am sure is not malfunctioning as I got two of them and none works, so my guess will be that has something to do with pcie kernel driver not detecting it. Could it be because it’s an M.2 M+B key?
lsmod
Module Size Used by
apex 28672 0
gasket 106496 1 apex
Hello, For what it is worth, I have an NVMe SSD(Patriot PS128GPM280SSDR) with M+B key, it works in the VIM3’s M.2 socket(also works with M2X ext board).
Thanks for that, and yes you do need to install some drivers:
Edit: I don’t believe the driver is the issue since lspci couldn’t detect the m2 key
Hi guys, one other thing that I like to share (we are working on documenting this):
If you are running a system with kernel version 4.19+ you’ll need to first disable built-in kernel module driver for apex device. It has a known bug which might prevent proper driver update.
Create a blacklist-apex.conf file in /etc/modprobe.d/ with two lines in there:
blacklist gasket
blacklist apex
Reboot system
Verify that apex/gasket modules aren’t loaded by doing:
lsmod|grep apex
Follow steps to install gasket-dkms package from
delete file /etc/modprobe.d/blacklist-apex.conf
reboot system
Then follow other steps from instruction.
Although I’m not sure if this is related to the issue with khadas devices because if lscpi not showing our devices, then it looks like a configuring issue.
@namvu I just tried that and made no difference. Based on the specs it should work from the interface point of view. https://coral.withgoogle.com/docs/m2/datasheet/
I had a quick look around and based on the logs it seems to be failing here at func amlogic_pcie_link_up https://github.com/khadas/linux/blob/khadas-vims-4.9.y/drivers/amlogic/pci/pcie-amlogic-v2.c
I tough for a second that coral was not gen 1 or 2 as in the driver but that is not the case. I notices some patches from sept/2019 which haven’t not been applied to pcie-amlogic-v2 (8 month old now) . I am not sure if any of these are relevant but maybe one of them could fix the problem.
https://lore.kernel.org/linux-amlogic/20190916125022.10754-7-narmstrong@baylibre.com/T/
I figured it’s not the same issue, if the wrong module were loaded, I’d imagine a runtime issue rather than not being able to detect at all.
So from the source code (thanks for pointing out the)
I believe this is an amlogic phy not linking to the PCIe module. I have no idea if that patch you mentioned would fix this.
Maybe move this to the amlogic forum? 
Edit: Although that code is on the khadas-vims-4.9.y branch, is this the right build for the vim3 board?
Does this different to the NVMe SSD ?
Yes, it the branch used for VIM3.
AFAIK: NVMe is just a protocols for communicating via the PCIe interface. I believe this is an issue to the actual phy chip.
No idea yet. If everything is OK, I will get a coral in the end of this month, I hope I can debug with it at that time.
Have did you received the coral?
Not yet…I can only get USB version for current stage, M.2 version still need to wait more time…
I tried to connect a PCI-e sound card through an adapter. Kernel 4.9 produces a similar error in the logs. But on the mainline kernel (5.5 rc2), the sound card was determined. Apparently, you still need to backport the latest changes related to PCI-e.
I just checked, I will try to buy one and feedback here.
I made ubuntu 20.04 image with fenix with mainline linux
uname -a
Linux Khadas 5.6.0
cat /sys/class/mcu/usb_pcie_switch_mode
1
so it looks like I have pci-e mode
but
lspci -vvv
is empty and I don’t see any host bridge
and no sign of meson pci-e in dmesg
any idea?
I would like to connect pci-e dvb-t tunner
btw
http://lists.infradead.org/pipermail/linux-amlogic/2020-May/016641.html
Any progress on connecting coral M2 card to VIM3/L pcie slot?
Any updates on VIM3x and the Coral module? @numbqq
I just bought your VIM3L and tried on VIM3L_Ubuntu-server-focal_Linux-5.7-rc7_arm64_SD-USB_V0.9-20200530 : after installing the B+M module and the Coral driver lspci reports nothing, nothing relevant in dmesg.