I am using a Debian Distro now. A full Distro. Anyway, I am building around a BBB to start.
git clone git://git.yoctoproject.org/poky
git checkout -t origin/langdale -b Lang
git pull
cd poky && source oe-init-build-env
# I then change some particulars in /conf/local.conf to support the BBB
# I changed some items in the bblayers.conf but to no avail...
# The meta-(N) I picked were needing other meta-(N) items and they all just failed in the end
# Then...
bitbake core-image-minimal-dev
# Now what?
Their records are vast and full of info. Is there a particular site you know of currently that supports commands being done by Yocto for the BBB?
Seth
P.S. Here are some ideas but I do not know if they are going to work…
I read over their documentation (some of it). I see the input file needs to be of the build from bitbake, the file, and the suffix .wic. Where does the suffix of .wic come from currently? I looked in the proper file and I do not have the file w/ the suffix of .wic. Hmm…
Sorry, was busy and forgot to check here. Yeah, you have the image, that .wic has it all. There are various different styles you can build.
Make sure you have:
MACHINE ?= “beaglebone-yocto”
I recommend using balena Etcher to write the SDs, as dd tosses a lot of errors on many devices. Long timeout and such. balena validates the image after it is written also.
If built correctly you can take that SD and boot it in the BBB. However, it needs the correct am335x-boneblack.dtb, u-boot.img, zImage and uEnv.txt in the root partition. With a yocto build it should all be setup correctly in the wic which includes 2 partitions, the boot and the rootfs.
Do you have a TTL serial cable? There is a mini-USB->USB cable that comes with the BBB, you can access that over the network, but it needs to DHCP so it may take some fancy dancing to figure out what your IP is to ssh into. The TTL will allow you to preempt the boot and stop at the u-boot prompt but you need a keyboard and mouse on the USB of the BBB to type and/or HDMI to see the output when the device connects. You also might be able to use tshark or wireshark to watch the network traffic when it gets the DHCP to see what it is. If you can shell in, debian/temppwd should get you a login. It will be displayed on the screen. In some cases root with no passwd will work, but debian.temppwd should be the default.
It is imperative to get to the point that you can compile and run your image. Until you can do that, no use in going any farther.
Okay. I will use Etcher. The issue is that I have no .wic file.
In /tmp/deploy/, I only have other dirs. like /license and /rpm.
Seth
P.S. I have a TTL to USB cable for the BBB. I can access u-boot when necessary. For whatever reason, the build bitbake core-image-minimal-dev -c populate_sdk_ext produces no .wic file.
By default RPMs are produced, but the above will build debian pkgs. FYI, there is another option called package_ipk and those opkg are also debian style and you can use debian tools on them, such as dpkg and apt.
You should only need that .wic file because everything it builds a package for it should install to the image.
Hollar if you have any problems. Once you get the image built and have dev tools on there, you can at least test a simple compile of “hello world” should work. All pkgs installed must be arm binaries, so if you do that on an x86 host, use the yocto compiler, it should be located in the following directory. But if you have gcc and g++ on your image you should be able to compile one on the BBB itself.
Thank you for supporting the cause here. I appreciate you taking time out to solve issues.
Seth
P.S. I will get back to you. The build should be done in about two or three hours. I put package_deb for apt to be built for bitbake core-image-minimal-dev -c populate_sdk_ext and I will relay back no matter what happens. Thank you again…
I’m building a core-image-minimal right now as I can’t remember exactly what is on there, but I have additions in my local.conf that will effect it. I’m also including meta-qt5 from github in addition to the meta-openembedded which is needed for the u-boot/BSP.
Let me burn and boot it, it’s done already.
Ooops, that builds and boots for me but I can’t login, there is a root user per my rootfs when it built the .wic, but I don’t know what the passwd is. You should be at least able to boot it. We’ll figure that out for you. debian/temppwd is from the buildroot image, not the yocto. I have changes that will get it to boot. without a password. I’m trying a core-image-x11 now…I can’t remember what that one has.
I thought something was up when you told me about Yocto and debian/tmppwd for user name and passwd.
Anyway, I have the WIC file now! And would you not know it, the damn SD Card holder in the computer is broken for some reason. I need to reboot, i.e. as this may be the difference b/t booting the Yocto image and not knowing how to do it!
Seth
Update
One computer, Debian machine, shows this under /poky/build/tmp/deploy/images/beaglebone-yocto:
You should be ok, I just remembered that there’s a package that needs to be set called default-tweaks, it sets the password empty for root. You can also set a specific password using the following method as well I believe.
Yes, the debug-tweaks got me a login without using a passwd.
Look on your SD and see if /boot/uEnv.txt exists?
The image should be setup to boot correctly, mine just did.
Alan
root@beaglebone-yocto:~# uname -a
Linux beaglebone-yocto 6.1.3-yocto-standard #1 PREEMPT Wed Jan 4 21:27:07 UTC 2023 armv7l GNU/Linux
root@beaglebone-yocto:~#
Also, gcc and g++ are on my image.
PS - I need to go get some work done, so may not respond until tomorrow.
bash-5.2# ip addr
1: lo: mtu 65536 qdisc noop state DOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 1c:ba:8c:a2:11:48 brd ff:ff:ff:ff:ff:ff
bash-5.2#
I don’t have ifconfig or dhclient, those are needed to get the network up so you can ssh in. This is something I need to do for my image, so you’re in luck.
Actually dropbear is included with debug-tweaks, it does implement it just fine.
I am building things up and here’s where I am so far…still don’t have a network interface.
IMAGE_INSTALL += "
bash
xwayland
inetutils
procps
matchbox-desktop
matchbox-session
init-ifupdown
netbase
udev
os-release
dhcpcd
connman
resolvconf
net-tools
zeromq
qt5ledscreen
packagegroup-qt5-toolchain-target
" @foxsquirrel do you by chance know how to get some type of X desktop booting on the current yocto?? I’m still trying to figure out what is preventing it from starting, I only have the older builds that boot X reliably on my Rev. C.
They can’t really bust themselves, but they can be bricked. If you have a valid built SD and flash it, it should boot on the BBB. If something happens to the NAND (eMMC) and the SD (MMC) is invalid it won’t boot. However, AFAICT, as long as you have a valid SD it will boot. That goes for old vs. new u-boot/firmware and/or kernel. I still am not sure what happened along the way but it seems they broke some stuff to move the BBB forward. Anyone know?
At the very bottom of the page for the Angstrom images, that’s the middle image, for the eMMC flasher.
Burn that to an SD and that will flash your BBB.
I currently have the 2020-04-06 image for Debian Buster (10) in my eMMC, it boots a Debian console image if I don’t insert an SD or if the SD is invalid.
P.S. I am going to try to build those utils/tools you have listed. Who knows? I may brick another SSD? Oh and about the image, I flashed two SD Cards so far w/ the builds I made before the great crash of 2023. Or as some call it, bricked!
