<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>U-Boot on Saeed</title><link>https://saeedvft.github.io/tags/u-boot/</link><description>Recent content in U-Boot on Saeed</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Saeed</copyright><lastBuildDate>Wed, 14 Oct 2026 09:58:08 +0330</lastBuildDate><atom:link href="https://saeedvft.github.io/tags/u-boot/index.xml" rel="self" type="application/rss+xml"/><item><title>The 64-Byte Difference Between uImage and zImage</title><link>https://saeedvft.github.io/posts/14-10-2026-uimage-vs-zimage/</link><pubDate>Wed, 14 Oct 2026 09:58:08 +0330</pubDate><guid>https://saeedvft.github.io/posts/14-10-2026-uimage-vs-zimage/</guid><description>If you&amp;rsquo;ve spent any time in embedded Linux, you&amp;rsquo;ve run into zImage and uImage. You&amp;rsquo;ve probably also seen u-boot.bin sitting right next to them in the same directory, which leads to a very common question:
Are these kernel images or U-Boot images?
Short answer: They&amp;rsquo;re both kernel images. The &amp;ldquo;u&amp;rdquo; in uImage is misleading — it refers to the format, not the contents. Let&amp;rsquo;s break it down properly.
The Two Files at a Glance File What it actually is zImage A compressed, self-extracting Linux kernel uImage That same kernel, plus a 64-byte U-Boot header u-boot.</description></item></channel></rss>