I’m trying to get yocto/poky kirkstone to run on a beagleplay. I got a system that allows me to work with a serial console. But then any attempt at loading modules fails spectacularly with something like this:
Now what I haven’t mentioned explicitly: I was using linux-ti-staging. Because my customer had used those via Debian/ti-linux-kernel-dev. However this morning I decided to try & revert to linux-bb.org (5.10.162+) and that’s working. Still interested in understanding why the staging kernel works on Debian but not yocto.
Big difference when you are on the top looking down versus on the bottom looking up and guessing what is going on.
Is your MACHINE=“beagleplay” or did you use a custom?
I found our board and built an image after reading your post and used beagleplay with systemd and could not get the weston compositor up. Pretty sure we had it running on that board before, it might be something simple. Maybe when the snow flies this winter…
I am using busybox (just because that was the poky default it appeared), if that makes a difference. And yes, I used beagleplay as machine. It is to be honest a bit confusing to me, the build process prints out the usual prefix twice, once for beagleplay, and then for beagleplay-k3r5
The meta-bela doesn’t really contain anything significant beyond adding a custom image with some installed packages. So it shouldn’t have any significant impact, or so I thought…
Turns out I need to build core-image-base, and then I get modules, and I can load them. I’ll have to pour over the contents of meta-bela to see what’s causing the issue here.
So I can now load modules. I can’t use eth0 unfortunately, even though it is plugged in, ethtool will say
Settings for eth0:
Supported ports: [ TP AUI MII FIBRE BNC Backplane ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
1000baseKX/Full
1000baseX/Full
100baseT1/Full
1000baseT1/Full
100baseFX/Half 100baseFX/Full
10baseT1L/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Half
Auto-negotiation: off
Port: MII
PHYAD: 0
Transceiver: internal
Supports Wake-on: d
Wake-on: d
Current message level: 0x000020f7 (8439)
drv probe link ifdown ifup rx_err tx_err hw
Link detected: no
In dmesg I find
[ 3.066655] davinci_mdio 8000000.ethernet:mdio@f00: Configuring MDIO in manual mode
[ 3.074376] davinci_mdio: probe of 8000000.ethernet:mdio@f00 failed with error -22
Might be some config file is missing, sometimes this gets so involved. That meta-bela might have your missing config files, just a guess.
Also, might add in some networking tools so you can poke around and see what is up and running.
Another thought, might look at building the AM62 evm out of ti-bsp. Believe the networking was up on that one. If it does work that might have some additional clues.