Mine was definitely bricked, and my boss sent me one I’m keeping virgin in case I think I horked it up again, so I do currently have 2 of them and can try running an SD on it once I get one that boots correctly. I understand more now about the BBB, but still don’t have anything I can build that runs a desktop on the HDMI.
Alan
I just discovered another one to watch out for, this one was my fault. The VM was configured to run 15 of the 16 cores. Bitbake is smoking fast doing that, then, out of the blue, a fresh desktop. It was instant fresh desktop, everything was closed down, so odd. This is using a Ubuntu 22.04 host for VMware Workstation 17. Everything was fine after the restart, never have had that happen on amd64 machine.
What works good is several NVMe drives and leave your host’s NVMe alone. Spread you VM’s over several drives. Also, keep a Tb or better enterprise grade hard (spinning disk type) drive in the system. Just map each one so if one dies you can work on damage control.
No, I had to turn that stuff off and run headless. Not sure if trying to run x11 is even practical because Ubuntu and Debian have gone exclusive Wayland.
If you need to run a headless server using AI64 this will turn off the desktop manager.
Temporary off >
$ sudo systemctl isolate multi-user.target
to turn it back on >
$ sudo systemctl isolate graphical.target
to make it permanent after reboot
off permanently >
$ sudo systemctl set-default multi-user.target
on permanently >
$ sudo systemctl set-default graphical.target
Yeah, I believe that is an issue also, and this is the theory I’m coming up with…I think due to a new kernel or a new glibc, something like that, it is no longer possible for the video interface to work.
My boss has a theory that we still need the same video glue layer, even if we use a different display, but that I’m not sure of yet. I do know that I have not been able to get any UI on the HDMI except for older builds. There is also no source trees AFAIK, IOW, no buildable sources.
I seem to be missing a lot of stuff on this build. Although I have bash, I can’t load it and stuck on the sh without a login…that part should work it seems.
I do notice that when I flashed my eMMC, it flashed from a GUI SD and what is in the eMMC is console, and all older SDs seem to boot the UI just fine. Kinda frustrating…
Alan
Some of that is because it has all gone 64 bit. No point in spending time on 32 bit history. The ai64 might be a better fit depending on what your needs are. Just ordered the new beagle board it looks promising, I did not notice any comments about having NVMe, hopefully that board will support it.
The other issue is ARM, it is on the back burner with many. Tried doing some stuff with gstreamer and opengl family and it does not light up on ARM.
Also make sure you have the HDMI overlay in your uEnv.txt file.
I hate to disagree, but was just about ready to give up with yocto, thinking I might be better with buildroot as it was easy to get a booting image with no gui, but has a login.
The reason I disagree, you can see for yourself. I have replaced my client’s name with xxxxxx
bblayers.conf
-------- start of bblayers.conf -------
POKY_BBLAYERS_CONF_VERSION = “2”
BBPATH = “${TOPDIR}”
BBFILES ?= “”
BBLAYERS ?= " \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-poky \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-yocto-bsp \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-qt5 \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-openembedded/meta-oe \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-openembedded/meta-xfce \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-openembedded/meta-gnome \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-openembedded/meta-python \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-openembedded/meta-multimedia \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-openembedded/meta-networking \
/home/aland/src/xxxxxx/meta_xxxxxx_bb/meta-xxxxxx \
"
---------- eof bblayers.conf ----------
---------- start of local.conf ----------
MACHINE ?= “beaglebone-yocto”
MACHINE ??= “qemux86-64”
IMAGE_ROOTFS_SIZE = “3006650”
IMAGE_INSTALL += " \
bash \
inetutils \
init-ifupdown \
procps \
xfdesktop \
xinit \
init-ifupdown \
netbase \
udev \
os-release \
dhcpcd \
connman \
resolvconf \
net-tools \
zeromq \
qt5ledscreen \
packagegroup-qt5-toolchain-target \
"
DISTRO ?= “poky”
PACKAGE_CLASSES ?= “package_deb”
EXTRA_IMAGE_FEATURES ?= " debug-tweaks tools-sdk dev-pkgs"
USER_CLASSES ?= “buildstats”
PATCHRESOLVE = “noop”
BB_DISKMON_DIRS ??= “\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
HALT,${TMPDIR},100M,1K \
HALT,${DL_DIR},100M,1K \
HALT,${SSTATE_DIR},100M,1K \
HALT,/tmp,10M,1K”
PACKAGECONFIG:append:pn-qemu-system-native = " sdl"
CONF_VERSION = “2”
------------ eof local.conf -------------
Cheers,
Alan - live free or die
Software Orchestration
@silver2row that should get you up and running for CERTAIN! 
Hello @softorchestra ,
I am working on core-image-sato now instead of core-image-minimal-dev and I will try the updates you have given here. Updates on the way!
Seth
I think sato is for mobile devices like phones and tablets. That will build but not give a Xorg server, AFAIK. Maybe you can school me on the sato?
Alan
Oh…now I know! Thank you…
Seth
P.S. I know nothing about sato for now. I am trying everything and all things until stuff works the way I want.
I don’t know too much either…but phones and tablets allow orientation change and requires more logic.
There are all types of sizes and resolutions.
I think the BBB would serve well as a development for sato, providing you had the cape and had a display connected properly. In that case it wouldn’t run Xorg over the HDMI.
My current project doesn’t need to run on a desktop, as it’s possible to remove the GUI from the Qt config. But if I can provide the desktop I think that is preferable.
Alan
I’ve never used Yocto. I did see a discussion on ROS forum about GUIX as a possible alternative
Thank you very much for sharing that information. Watched some of the video and the developer actually has done embedded linux so that is a very positive impression. It appears to be worth looking into, getting a working image will be the real test. Then light it up on a couple other boards.
Hello Alan,
Seth here. I am building the machine you have listed but w/out Qt5…
I will report back when time is available. Thank you.
Seth
@softorchestra : I have python and other items in the entry I am building. So, this may just be awesome!
Nothing so far. The board does not boot w/ the core-image-minimal-dev image or the core-image-full-cmdline-beaglebone-yocto-20230315012810.rootfs.wic image.
I am not sure why just yet. I tried w/ the TTY to USB converter. Nothing.
I tried to sign in via the Ethernet IP Address w/ root but nothing…
Off to keep trying.
Boot! I had to add the group dialout to the machine and then reboot the dev. desktop. So, now I am in the machine Yocto-BBB but what next? I mean, I read over the boot log. There are many ideas floating around…
Hmm. Anyway, thank you. I need to try the newer boot of the full-cmdline distro!
Sorry to be slow, kinda busy wrapping things up as my contract is ending on Friday. Very unlikely I will be working on BBB again, so I hope my next project is a more modern design. I do still like the BBB and feel it’s a great board to prototype on.
Or build the core-image-minimal-xfce 
You ask “what next?”
I’m not sure, what do you want to do with it? Do you want to connect a breadboard and wire it up with some type of sensor, or what is your intention for running a system on a board, I think some even refer to the BBB as a SoC.
You can just build the system up once you have it built, but the proper way to use yocto is to create a recipe to start tailoring your image.
It works almost identical to an Ubuntu system, despite using BusyBox.
As an example:
or
What type of app do you plan to write? Web application? If so get Apache setup how you like. Node.js ??? If so get it installed and running so you can do your development.
Change the machine type and rebuild, it will build an entire system.
I know this is old, but did you all get beaglebone-yocto core-image-minimal to boot on BBB
seems yocto kirkstone is not working,
I have successfully loaded yocto onto beaglebone black with the custom graphics hardware accelerator.
It just must be done very specifically and methodolically
It is possible with dunfell only.
I am sorry I missed this idea until now. You asked, “What do you want to do with it?”
As usually standing here, I do not know. I just wanted to learn how to perform specific tasks around boards and with it all relative to Linux builds/building.
Seth
P.S. I got wrapped up in building many different ideas online and trying to keep up with the new boards. To tell you the truth, I lost track with mechanical builds and software. It is about a year later now and I got frustrated from what I remember and tried something “new.” Thank you. I totally forgot about how much help you were being at the time!
