-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kirkstone device tree and wifi/bl issue #51
Comments
Which branch of meta-coral did you use? Have you tried with master? @kraj has been doing some updates recently, including updates of kernel. |
Hi, |
Master works great and that’s what I test regularly with yoe distro I am not sure about kirkstone maybe you can change which kernel to use etc might help |
Thanks @kraj. I need kernel 5.15 at least due to some gstreamer-imx dependencies. That's why i was using kirkstone. Can I get newer kernel with yoe or yocto zeus/warrior and the master branch? |
we currently use linux-fslc 6.1 kernel with master. If you want to stick to 5.15 you can change diff --git a/conf/machine/coral-dev.conf b/conf/machine/coral-dev.conf
index e7ad7cb..6e33bbb 100644
--- a/conf/machine/coral-dev.conf
+++ b/conf/machine/coral-dev.conf
@@ -14,7 +14,7 @@ require conf/machine/include/arm/armv8a/tune-cortexa53.inc
# inline NEON and FPU code generation
DEFAULTTUNE:use-mainline-bsp = "cortexa53-crypto"
-PREFERRED_PROVIDER_virtual/kernel:use-mainline-bsp = "linux-fslc"
+PREFERRED_PROVIDER_virtual/kernel:use-mainline-bsp = "linux-fslc-lts"
PREFERRED_PROVIDER_virtual/kernel:use-nxp-bsp = "linux-coral"
MACHINE_FEATURES += "pci wifi bluetooth bcm43455 bcm4356" |
hi @kraj
|
My needs are ethernet only, infact so I have not tested wifi/bluetooth. |
can you help me please, I'm really stuck with that. I has a look at the device tree and both pci (pcie@33800000, pcie@33c00000) were disabled. I enabled them and now I have the following:
|
I tried to use the device tree from mendel but the kernel is not loading at all. The output from the kernel is not readable as well. do you have any ideas what could be the problem? |
can you post your changes to device tree to enable this ? |
I only changed |
I just realise the TPU is attached to the PCI as well so even if I acces the device via ethernet its not really useful. |
The Coral Dev Board is largely based on https://github.com/Freescale/meta-freescale/blob/master/conf/machine/imx8mq-evk.conf. The WiFI part I believe is identical to that board. So would start with comparing the dtbs of these two. |
I have only tested WiFi when I did the initial integration which was based on "zeus". This was still using the downstream Google Coral Linux kernel. |
just had a look at i.MX 8MDQLQ EVK Board Hardware User's Guide https://cache.nxp.com/secured/assets/documents/en/user-guide/IMX8MDQLQEVKHUG.pdf?fileExt=.pdfand I can confirm the wifi setup is with the same. |
Hm, I did not close this :P. It was most likely the comment in #52 that did it in the merge. @NIKovachev , can you try out the new changes and report back? |
Hi @NIKovachev, |
hi @mirzak,
thanks for sharing your work.
With kirkstone there is no PCI reported:
I assume there is a problem with the device tree as we are using one from a different board. i tried to use the old device tree provided with the mendel release but this didn't work due to a bus clock error. As of that I'm unable to enable the wifi aand that makes the device in my case useless. Can you support me please with the pci and the device tree issue?
The text was updated successfully, but these errors were encountered: