<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yocto-MX93 on Embedded Linux Blog</title><link>https://embeddedlinux.blog/en/series/yocto-mx93/</link><description>Recent content in Yocto-MX93 on Embedded Linux Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 09 Feb 2026 22:20:20 +0700</lastBuildDate><atom:link href="https://embeddedlinux.blog/en/series/yocto-mx93/index.xml" rel="self" type="application/rss+xml"/><item><title>[Yocto-MX93] 2. Connecting to wifi, trying Chromium</title><link>https://embeddedlinux.blog/en/2026/02/07/yocto-mx93-2-ket-noi-wifi-test-thu-chromium/</link><pubDate>Sat, 07 Feb 2026 07:34:09 +0700</pubDate><guid>https://embeddedlinux.blog/en/2026/02/07/yocto-mx93-2-ket-noi-wifi-test-thu-chromium/</guid><description>&lt;p&gt;One nice thing about using the vendor's full-featured image is that adding things is quite simple, and there is plenty of documentation from the vendor too&lt;/p&gt;&#10;&lt;h2 id="1-adding-chromium-to-the-build"&gt;1. Adding Chromium to the build&lt;/h2&gt;&#10;&lt;p&gt;First, as I said in the previous post, to avoid editing local.conf and bblayers and then having those 2 files reset when you run source, we first run the following command to initialise the build environment&lt;/p&gt;</description></item><item><title>[Yocto-MX93] 1. Building imx-image-full for the FRDM-i.MX93</title><link>https://embeddedlinux.blog/en/2026/01/31/yocto-mx93-1-build-imx-image-full-cho-frdm-i-mx93/</link><pubDate>Sat, 31 Jan 2026 22:07:48 +0700</pubDate><guid>https://embeddedlinux.blog/en/2026/01/31/yocto-mx93-1-build-imx-image-full-cho-frdm-i-mx93/</guid><description>&lt;p&gt;In the Yocto series for the Beaglebone Black and STM32MP157 I did a lot of basic features, how to use yocto, working up from core-image-minimal. This time I build the features for the FRDM i.MX93 board starting straight from the vendor's full image.&lt;/p&gt;</description></item></channel></rss>