<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kernel-QEMU on Embedded Linux Blog</title><link>https://embeddedlinux.blog/en/tags/kernel-qemu/</link><description>Recent content in Kernel-QEMU on Embedded Linux Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 13 Apr 2026 10:09:13 +0700</lastBuildDate><atom:link href="https://embeddedlinux.blog/en/tags/kernel-qemu/index.xml" rel="self" type="application/rss+xml"/><item><title>[Kernel-QEMU] 1. KGDB debugging from start_kernel with a VS Code interface</title><link>https://embeddedlinux.blog/en/2026/05/02/kernel-qemu-1-kgdb-debug-tu-start_kernel-voi-giao-dien-tren-vs-code/</link><pubDate>Sat, 02 May 2026 06:27:00 +0700</pubDate><guid>https://embeddedlinux.blog/en/2026/05/02/kernel-qemu-1-kgdb-debug-tu-start_kernel-voi-giao-dien-tren-vs-code/</guid><description>&lt;p&gt;As I said in the Kernel-BBB 2 post, without JTAG on the BBB we probably cannot debug the kernel from the very first line. So I am turning to QEMU to have full control over the code.&lt;/p&gt;&#10;&lt;p&gt;Oh, in this post I clone the sources and build the related components, no Yocto this time (If yocto is my strength, what am i without Yocto :vv Haha)&lt;/p&gt;</description></item></channel></rss>