my local.conf:
MACHINE ??= “beagleplay”
I have not done any customizations to the layers in meta-ti, and I build:
bitbake core-image-minimal
The kernel is linux-bb.org (5.10.168)
I will try to have the syslog written to the SD card nonvolatile folder and see if I can find out whats going on.
I notice the image is written to this folder:
tmp/work/beagleplay-poky-linux/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete
but not to tmp/deploy/beagleplay
kinda odd…
$bitbake core-image-base
or
$bitbake core-image-weston
Do the tree -d -L 3 in your build, you should see deploy / images, that is where your image should be. This is for a different BSP however it is similar to what you should have.
fred@eng-dev2:~/build1/imx93-yocto/var-fsl-yocto/build_imx93_wayland$ tree -d -L 3
.
├── cache
├── conf
└── tmp
├── buildstats
│ ├── 20231030110649
│ ├── 20231030113712
│ └── 20231030115652
├── cache
├── deploy
│ ├── deb
│ ├── images
│ └── licenses
├── hosttools
├── log
Also, you might need to view all files, you want the .wic.zst or what ever one has .wic in it.
Use the raspberry pi imager, go to custom and select your image. Burn and let pi-imager verifiy the image.
I tried core-image-base, also no tty access. I found that my core-image-minimal seemed to not get past the “ifup -a” in the networking setup script…
Btw, my output ends up in this folder deploy-ti/images/beagleplay rather than under tmp… gotta check the DEPLOY_DIR_IMAGE variable.
Are you using poky or the ti package?
I am using poky, actually i followed this guide:
My BeaglePlay runs ok with the image on the eMMC, but thats a completely different dist.
I notice the guide uses:
NATIVELSBSTRING = “ubuntu-20.04”
TARGET_SYS = “arm-poky-linux-gnueabi”
Whereas I have:
NATIVELSBSTRING = “universal”
TARGET_SYS = “arm-poky-eabi”
When I change to “arm-poky-linux-gnueabi”, I get python3_3.10.13.bb do_configure failed:
“configure: error: internal configure error for the platform triplet, please file a bug report”
What to do here?
Might ask whomever wrote that guide.
Ok here is an update. I wanted to build a poky image for beagleplay and have the uart5 working. I did get the image build and booted using the (default) arm-poky-eabi. The serial console was up, but not networking. The uart5 was occupied by the mikrobus.
I removed the uart5 from the mikrobus node in the dts, and configured it similiar to uart0. When booting from the SD, the new dtb was not picked up for some reason!, the one on the eMMC was loaded. So I had to add a /extlinux/extlinux.conf on my SD boot partition and also place the new dtb there.
LABEL beagleplay-SD
kernel /Image
fdt /k3-am625-beagleplay.dtb
APPEND root=/dev/mmcblk1p2 rootwait rw rootfstype=ext4 console=tty1 console=ttyS2,115200n8
Now this extlinux.conf is correctly loaded during boot. The uart5 gets linked to ttyS0 and works. The eth0 now also works as a bonus! And, I can boot from the SD card without pressing the USR button.
Glad you got it going. I tried to build a image too see what is actually going on and mine does not boot using a fresh build. Just could not get it to boot from SD. What lead up to this is I ran out of space and to delete several builds from a while back and the BP was one of them. I know it worked back then because we were testing it, now…
If someone is interested I did something here:
The built image boots in my board flashed on SD card. This is minimal image and everyone can put whatever on top. I have not checked the entire hardware but eth, wifi and hdmi work.
Keep in mind it uses a meta layer which I created here:
Some changes in the software were needed to boot the image without problems. I am open to suggestions or improvements of that.
That is an interesting patch. A while back I could not get it too boot and gave up on it after a few minutes. Thank you very much for posting that, I did not have the patience to fix it.
I do yocto without the yml script or the containers.
Have you had any blow outs running yocto in the VM?
Storage is very cheap now. Why do you still bother installing Yocto?
Whenever you change something, you have to recompile again and again. It wears out your PC and spend electricity. 
What is a better option than yocto?
Not sure if anything else exists that allows me to have parallel code from a BBB upto Intel x86 (exempting the hardware + and -).
No problems for me during the build in the docker container. I am using ubuntu 22.04 and docker uses image from siemens or at least looks like that - Package kas/kas · GitHub.
but for hardware drivers, mainstream Linux can provide you the most.
If you do not need GUI, simply set systemd to start without desktop, disable any service, for instance, Nginx, which you do not need.
Or, install a minimal image of BBPlay official OS without desktop.
Last time when I developed on a tiny NXP processor, it asked me to compile and build again and again. It piled up my electricity bills! 
Friend,
This may be the closest to what you need:
TI AM6254
If you take a closer look, you will see those SDKs are generated with Yocto. Actually I have built already such a SDK.
but the official TI SDK does not have BeaglePlay board support package, does it?
