Great content. My favorite part was how the content was presented. Not only are the slides shown, but the camera is doing a good job of tracking the presenter. So regardless of what I need to focus on, I can get what I need. This sounds obvious, but it's not. I cannot tell you how many presentations I've watched where the presenter says "study this piece of code for a few minutes" and the cameraman spends 2 minutes watching the presenter drink water (whereas I spend those two minutes insulting the cameraman's parentage). Well done!
00:12 Introducing Yocto Project for embedded systems 02:34 Designing custom computer boards for volume and economic benefits 07:34 Yocto Project is widely used in various open source projects and popular devices. 10:09 Evolution of Yocto Project from OpenEmbedded and Poky Linux 15:10 Yocto Project setup involves initializing the shell and configuring variables. 17:33 Understanding Yocto Project layers and configuration 22:09 Yocto Project images are specified by recipes and can be customized for specific needs. 24:16 Configuring Yocto Project for QEMU Arm 32-bit machine 28:43 Creating and using disk images in Yocto Project 30:53 Setting up variables and paths for pre-loaded Shared State cache and downloads 35:39 Yocto Project supports various components and tools beyond BSP and distros. 38:04 Adding software to Yocto Project 43:02 Demonstration of creating and editing text files using Nano in Yocto Project 46:01 A recipe in Yocto Project contains instructions to fetch, configure, compile, and install a software component. 50:25 Adding packages to the Yocto Project Target 53:09 Yocto Project is an industry standard for embedded Linux systems. 58:33 Board Support Packages and Kernel Replacement 1:00:55 Licensing in Yocto Project overview
I'm really enjoyed this, but I don't understand the statement that LG (WebOS) TVs etc are "running yocto", minute ~8 - 10)? Does that really mean that they are running distributions that have been built using yocto?
I've used buildroot in the past (because I was working with OpenWRT) but the people at my old job were always on about Yokto, Poke-ey (they used the wrong pronunciation) and Bit-Bake. I'd love to see a side-by-side comparison of the two from somebody who's used both and doesn't have any allegiance to either. I get the feeling that Yokto is the way to go but devs love shiny things.
One thing is bsp availability. Often CPU vendors like nxp offer official yocto layers for their cpus, socs, soms and eval boards. There are very good reasons for this. The layer architecture specifically. Basically you can use one layer that has all the patchsets for the kernel and libraries (like hardware encryption) etc. It is really neat for that. For the normal user and dev it is a really odd way, orthogonal to packages. For the BSP vendor it is pure heaven. Make a layer, throw all patches into recipes, say what you are basing things on, done.
The comment regarding BSP kernels is incorrect. One of the great things about Yocto is that you can override pretty much anything. That includes `PREFERRED_PROVIDER_virtual/linux`, `PREFERRED_VERSION_virtual/linux` and the BSP kernel recipe's `DEFAULT_PREFERENCE`. Using various combinations of these you can select any kernel you want. You will of course want to select a kernel that supports your board. Great talk otherwise!
Great content. My favorite part was how the content was presented. Not only are the slides shown, but the camera is doing a good job of tracking the presenter. So regardless of what I need to focus on, I can get what I need. This sounds obvious, but it's not. I cannot tell you how many presentations I've watched where the presenter says "study this piece of code for a few minutes" and the cameraman spends 2 minutes watching the presenter drink water (whereas I spend those two minutes insulting the cameraman's parentage). Well done!
00:12 Introducing Yocto Project for embedded systems
02:34 Designing custom computer boards for volume and economic benefits
07:34 Yocto Project is widely used in various open source projects and popular devices.
10:09 Evolution of Yocto Project from OpenEmbedded and Poky Linux
15:10 Yocto Project setup involves initializing the shell and configuring variables.
17:33 Understanding Yocto Project layers and configuration
22:09 Yocto Project images are specified by recipes and can be customized for specific needs.
24:16 Configuring Yocto Project for QEMU Arm 32-bit machine
28:43 Creating and using disk images in Yocto Project
30:53 Setting up variables and paths for pre-loaded Shared State cache and downloads
35:39 Yocto Project supports various components and tools beyond BSP and distros.
38:04 Adding software to Yocto Project
43:02 Demonstration of creating and editing text files using Nano in Yocto Project
46:01 A recipe in Yocto Project contains instructions to fetch, configure, compile, and install a software component.
50:25 Adding packages to the Yocto Project Target
53:09 Yocto Project is an industry standard for embedded Linux systems.
58:33 Board Support Packages and Kernel Replacement
1:00:55 Licensing in Yocto Project overview
Pretty amazing lecture! Helped immensely for a beginner like me to grasp all the technicality and terms and put it together into a working build.
Your Embedded Linux lecture and this lecture helped me immensely understand the development enviroment for Cortex-A MPUs.
Amazing introduction, thank you very much !
Very helpful
Great stuff right here
Really liked it
Mr. Simmonds, can you also make Advanced Yocto videos instead of always Introduction videos (thanks for that btw)
For example "How to debug rare Yocto failures?"
I'm really enjoyed this, but I don't understand the statement that LG (WebOS) TVs etc are "running yocto", minute ~8 - 10)? Does that really mean that they are running distributions that have been built using yocto?
I've used buildroot in the past (because I was working with OpenWRT) but the people at my old job were always on about Yokto, Poke-ey (they used the wrong pronunciation) and Bit-Bake.
I'd love to see a side-by-side comparison of the two from somebody who's used both and doesn't have any allegiance to either. I get the feeling that Yokto is the way to go but devs love shiny things.
The guy explains it's poh-key, cuz it comes from the Pocky japanese snack.
One thing is bsp availability. Often CPU vendors like nxp offer official yocto layers for their cpus, socs, soms and eval boards. There are very good reasons for this. The layer architecture specifically. Basically you can use one layer that has all the patchsets for the kernel and libraries (like hardware encryption) etc. It is really neat for that. For the normal user and dev it is a really odd way, orthogonal to packages. For the BSP vendor it is pure heaven. Make a layer, throw all patches into recipes, say what you are basing things on, done.
The comment regarding BSP kernels is incorrect. One of the great things about Yocto is that you can override pretty much anything. That includes `PREFERRED_PROVIDER_virtual/linux`, `PREFERRED_VERSION_virtual/linux` and the BSP kernel recipe's `DEFAULT_PREFERENCE`. Using various combinations of these you can select any kernel you want. You will of course want to select a kernel that supports your board.
Great talk otherwise!
You're cute
Gosh ! This is extremely dry. I know I will not follow this one as a step-by-step guide ever.
it works . as a newbie i did not watch any other tutorial .. only followed this to build one