Yocto Tutorial - 01 Flashing Yocto Built Custom Linux OS onto BeagleBone Black (STEP-BY-STEP!!)
Вставка
- Опубліковано 10 вер 2024
- In this video, we will learn step-by-step how to flash a custom-built Yocto OS onto your BeagleBone Black board.
We will start by identifying the image file we need to use and the required hardware, including a BeagleBone Black, micro-SD card, an SD card reader, an FTDI cable, and a 5V power supply. Next, we will discuss the different flash tools available, including dd and Etcher.
We will then walk through the steps to flash the BeagleBone Black with Etcher, including downloading and installing Etcher, flashing the Yocto-Image on SD card using Etcher.
After flashing the BeagleBone Black, we will discuss how to connect it to the serial console using an FTDI cable and verify the connection. We will then walk through the steps to boot the BeagleBone Black and check the image, including checking the kernel version, seeing the partitions, and checking the rootfs folders.
github.com/Mun...
Beaglebone Black: grabcad.com/li...
FTDI Cable (Serial to USB): raw.githubuser... microcontrolle...
Etcher: www.balena.io/...
hello. I succesfull boot from sd card with yocto-linux but if i remove sd card from beagle bone and reboot system - its boot old debian image from emmc. how fix it?
thanks for video!
It will obviously not work, because you have flashed the Image in SD card. So if you remove it then the Image is gone.
Is there any other way to connect to the BBB other than FDTI cable. I got one from market but it does not have same pin configuration as users. Mine has red and blue wires at extreme left and right. The minicom is printing garbage and I am unable to see if my BBB is actually booting or not. can I connect using some other way?
Have you set the correct baud rate in Minicom? It should be 115200. Additionally, if your FTDI cable has a different pin configuration, try using jumper cables between the FTDI and the BeagleBone Black (BBB) to ensure the correct pin connections.
@@techabyte8 Thanks, I tried your suggestion. I am already using the 115200 baudrate. I swaped my cable wires (though two of the wires had different colors than the standard) but in one configuration its giving out and it seems like the BBB is booting up as the output printed follows the boot sequence but the output is still garbage printed on console. Is there any other settings that I should look for like patrity, number of bits, stop bits etc?
Have you also connected the GND pin of FTDI and BBB?
Can you guide to solve this type error ;
SoC type;; sama5d4_xplained
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 0:0, read 64 bytes
Could you please explain the context?
What are you building, at what point are you getting this error?
Hello, I don't have a successful boot. It seams as though my Boot goes into a loop. What could cause this? I used the .wic file with etcher as per instructions.
May be the .wic file got corrupted. Try once again.
@@techabyte8 I tried many times. I even followed instructions to manully move files into a bootable partition. It just started printing letter "c" repeatedly. I am running fedora 40. Maybe this is why?
It could be the Problem.
Here is the list of supported Distributions that you can use to build in Yocto:
docs.yoctoproject.org/4.0.19/ref-manual/system-requirements.html#supported-linux-distributions
@@techabyte8 I think I may be better off waiting for support for Ubuntu 24.04 LTS. I'm a little confused on the Yocto release cycle. Should I expect support for Ubuntu 24.04 in 6 months?
I do not know about it. I will suggest you to use a Docker container of one of Supported Distribution and build in it.
Thanks. Can you show how to setup a development environment where we can cross compile and deploy to beaglebone pls ? I am able to get the yocto beaglebone up and running. But I need to have the same Linux kernel version environment with cross toolchain to build kernel modules and deploy to bbb.
Hi Prateek,
Your Welcome.
I will cover this topic in future videos.
But let me quickly explain some steps that will help you.
First of all check the below link:
docs.yoctoproject.org/4.0.9/sdk-manual/appendix-obtain.html#building-an-sdk-installer
Go to step number 6, and and execute the first command:
bitbake -c populate_sdk IMAGE-NAME,
Let say that, you are building core-image-full-cmdline. Then the command will be.
bitbake -c populate_sdk core-image-full-cmdline
It will generate a ".sh" file, that will be inside tmp/deploy/sdk
Then execute that ".sh" file. It will ask you some parameters, if you keep every thing default, then it will place the whole toolchain including, sysroot, cross-compiler, debuggers and other utilities inside /opt folder in your host PC.
Hope this solves your problem.
Come back to me if you encounter any problem.
@@techabyte8 Thanks for your reply and attention. I will try and then get back
@@techabyte8 but I dont need sato I think because I am not doing mobile development. I made a beaglebone image using yocto kirkstone and it works fine, after making an SD card from the wic file that got generated. However I cant execute a hello world binary on it and run it, because toolchains are different and hence the .so files in the lib folder. I need to build a qemu image with the same Linux version, with header files/source code, so that I can cross compile kernel modules to de deployed on bbb
@@prateeksin Hi there,
Sorry I do not understand what do you want to achieve?
Which image did you build if not sato?
@@techabyte8 I made the core-image-full-cmdline for BBB, and have an nfs root setup, so that BBB can get the rootfs via nfs. Plan is to deploy new kernel modules on nfs folders, which BBB can acceess, directly on my 22.04 Ubuntu host. I need to build drivers and kernel modules on a host with a toolchain. Thanks once again.