<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Embedded Linux Notes]]></title><description><![CDATA[Embedded Linux Notes]]></description><link>https://embedded-linux.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 18:03:15 GMT</lastBuildDate><atom:link href="https://embedded-linux.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Yocto in 10 Minutes: Layers, Recipes and Images Without the Jargon]]></title><description><![CDATA[New to Yocto? Learn what layers, recipes, BitBake and images are, with a real example of building an image for a car infotainment system.]]></description><link>https://embedded-linux.hashnode.dev/yocto-in-10-minutes-layers-recipes-and-images-without-the-jargon</link><guid isPermaLink="true">https://embedded-linux.hashnode.dev/yocto-in-10-minutes-layers-recipes-and-images-without-the-jargon</guid><category><![CDATA[embedded systems]]></category><category><![CDATA[#yocto]]></category><category><![CDATA[openembedded]]></category><category><![CDATA[embedded linux]]></category><category><![CDATA[, bitbake]]></category><category><![CDATA[embedded system course]]></category><dc:creator><![CDATA[Shrushti Parikh]]></dc:creator><pubDate>Tue, 17 Nov 2026 15:33:46 GMT</pubDate><content:encoded><![CDATA[<p>In the second week of my job as an Embedded Software Engineer , my mentor handed me the Yocto User Guide and asked me to create a Board Support Package for an <a href="http://i.MX">i.MX</a> device.</p>
<p>I had no idea what Yocto was or how anyone worked in it. This is a summary of my understanding since then , written for people just starting out in the Embedded software domain.</p>
<h1>What Yocto actually is?</h1>
<p>Yocto is <strong>not a Linux Distribution</strong>. It's a toolkit for building your own Linux system for a specific device: exactly the kernel , bootloader , libraries and apps you need , and nothing else. Think of it as customized Linux made for only your device(SoC).</p>
<p>When we talk about Yocto it is very important to understand that it revolves around terminologies of cooking. (Quite fascinating right? I am yet to find the reason!)</p>
<p>Very plainly when we map the terminologies of yocto and cooking it looks like following :</p>
<ul>
<li>Recipes say how to make a single piece of software (a package to build a single product).</li>
<li>Layers are cookbooks , a collection of recipes grouped by purpose - like meta-wifi is collection of recipes grouped by purpose.</li>
<li>Bitbake is the chef that reads the recipes and does the work.</li>
<li>The image is the finished meal: the full system you flash onto your board.</li>
</ul>
<h1>The basic terminologies for getting started</h1>
<ol>
<li><strong>Bitbake :</strong> The build engine . It reads metadata , works out what depends on what , then fetches , configures , compiles and packages everything.</li>
<li><strong>Recipe(.bb file)</strong> : Describes how to build one piece of software: where the source comes from , how to configure and compile it and where to install it.</li>
<li><strong>Layer(meta-*folder)</strong> : A folder of recipes and configuration with one theme, such as meta-&lt;vendor&gt; , is a set of apps , or customizations for vendor's own hardware. Layers are stacked on top of each other.</li>
<li><strong>Image recipe</strong> : A special recipe that says which packages goes into final root file system deployed on board.</li>
</ol>
<h3>How the pieces connect</h3>
<p>When you run a build , bitbake performs following actions</p>
<ul>
<li>looks through the layers.</li>
<li>looks through the settings mentioned in local.conf</li>
<li>prepares Image recipe mentioned.</li>
</ul>
<h1><strong>Let's make it real : building an image for an car</strong></h1>
<p>Say you’re preparing the final image for an automotive infotainment system. The car needs a display, Bluetooth, sound and so on. Here’s how Yocto’s pieces map onto it.</p>
<p><strong>Recipes: one piece each.</strong><br />Every software component has its own recipe. The kernel has one, the bootloader (U-Boot) has one, the Bluetooth stack has one, the audio server has one. A recipe also carries what that component needs, such as patches, configuration files and init scripts.</p>
<p><strong>Layers: grouped by purpose.</strong><br />Recipes for one subsystem sit together in a layer. For example (names are illustrative):</p>
<table>
<thead>
<tr>
<th>Subsystem</th>
<th>Layer</th>
<th>What it holds</th>
</tr>
</thead>
<tbody><tr>
<td>Board support</td>
<td><code>meta-&lt;vendor&gt;</code></td>
<td>Kernel, U-Boot, drivers for the SoC</td>
</tr>
<tr>
<td>Display</td>
<td><code>meta-display</code></td>
<td>Graphics and UI recipes</td>
</tr>
<tr>
<td>Bluetooth</td>
<td><code>meta-bluetooth</code></td>
<td>Bluetooth stack and tools</td>
</tr>
<tr>
<td>Sound</td>
<td><code>meta-audio</code></td>
<td>Audio server and codecs</td>
</tr>
<tr>
<td>Your product</td>
<td><code>meta-&lt;yourproduct&gt;</code></td>
<td>Your own apps and customisations</td>
</tr>
</tbody></table>
<p><code>bblayers.conf</code><strong>: the list of layers.</strong><br />This file tells BitBake which layers to use. If a layer isn’t listed here, BitBake doesn’t see its recipes.</p>
<p><strong>The image recipe: what goes in the final system.</strong><br />It says which packages to include, such as the Bluetooth stack, the display server and the audio tools. You can add more with <code>IMAGE_INSTALL</code>.</p>
<p><code>bitbake &lt;image&gt;</code><strong>: bake it.</strong><br />BitBake reads all of the above, builds every recipe in the right order, and produces the image you flash onto the board.</p>
<p>The nice thing about this design is that each team can own a layer. The display team works in the display layer, the connectivity team in the Bluetooth layer, and nobody edits each other’s files, yet BitBake combines everything into one image.</p>
]]></content:encoded></item></channel></rss>