<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Blog Articals on ankit_kdev</title><link>http://www.ankitkdev.com/blog/</link><description>Recent content in Blog Articals on ankit_kdev</description><generator>Hugo -- 0.148.2</generator><language>en-us</language><lastBuildDate>Wed, 22 Apr 2026 15:02:44 +0530</lastBuildDate><atom:link href="http://www.ankitkdev.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Configure U-boot For Beaglebone Black</title><link>http://www.ankitkdev.com/blog/configure-uboot-bbb/</link><pubDate>Wed, 22 Apr 2026 15:02:44 +0530</pubDate><guid>http://www.ankitkdev.com/blog/configure-uboot-bbb/</guid><description>&lt;h1 id="overview">Overview&lt;/h1>
&lt;p>U-Boot (Universal Boot Loader) is the go-to bootloader for embedded Linux systems. If you&amp;rsquo;re working with the BeagleBone Black (BBB), building U-Boot from source gives you full control over the boot process, from initializing hardware to loading your kernel. This guide walks you through cross-compiling and installing U-Boot on the BBB from scratch.&lt;/p>
&lt;p>This blog will explain how to compile and install U-Boot, and then either manually boot from the U-Boot prompt or use &lt;strong>&lt;code>uEnv.txt&lt;/code>&lt;/strong> to autoboot the kernel.
You can also use &lt;code>extlinux/extlinux.conf&lt;/code> to boot the kernel.&lt;/p></description></item><item><title>Build and Install Linux Kernel For Beaglebone Black</title><link>http://www.ankitkdev.com/blog/build-linux-kernel-bbb/</link><pubDate>Wed, 08 Apr 2026 22:31:16 +0530</pubDate><guid>http://www.ankitkdev.com/blog/build-linux-kernel-bbb/</guid><description>&lt;h1 id="overview">Overview&lt;/h1>
&lt;p>The BeagleBone Black (BBB) uses an ARM Cortex-A8 32 bit processor, so the kernel must be cross-compiled on an x86 machine and then deployed to the board. This blog will assume that you already have a os[debian/ubuntu] installed on your sd card.&lt;/p>
&lt;p>We’ll:&lt;/p>
&lt;ul>
&lt;li>set up toolchain&lt;/li>
&lt;li>fetch kernel source&lt;/li>
&lt;li>configure for BBB&lt;/li>
&lt;li>build kernel + modules&lt;/li>
&lt;li>deploy to SD card / board&lt;/li>
&lt;/ul>
&lt;h2 id="1-prerequisites">1. Prerequisites&lt;/h2>
&lt;p>Make sure you have:&lt;/p>
&lt;ul>
&lt;li>Ubuntu (or any Linux host)&lt;/li>
&lt;li>Cross compiler for ARM (arm)&lt;/li>
&lt;/ul>
&lt;p>Install required tools:&lt;/p></description></item><item><title>Basics of debugging slab memory corruption via SLUB debug</title><link>http://www.ankitkdev.com/blog/debug-slub-memory/</link><pubDate>Wed, 04 Feb 2026 16:45:19 +0530</pubDate><guid>http://www.ankitkdev.com/blog/debug-slub-memory/</guid><description>&lt;h1 id="introduction">Introduction&lt;/h1>
&lt;p>Memory corruption can occur due to various bugs or defects: Uninitialized Memory
Reads (UMR), Use After Free (UAF), Use After Return (UAR), double-free, memory
leakage, or illegal Out Of Bounds (OOB) accesses that attempt to work upon (read/write/
execute) illegal memory regions.&lt;/p>
&lt;p>Since memory is dynamically allocated and freed via the kernel&amp;rsquo;s engine – the
page allocator. This can lead to serious wastage (internal fragmentation) of memory.
To mitigate this, the slab allocator (or slab cache) is layered upon it, serving two
primary tasks – providing fragments of pages efficiently (within the kernel, allocation
requests for small pieces of memory, from a few bytes to a couple of kilobytes), and serving as a cache for commonly used data structures.&lt;/p></description></item><item><title>Linux Kernel Mentorship Program</title><link>http://www.ankitkdev.com/blog/linux-kernel-mentorship-program/</link><pubDate>Mon, 08 Dec 2025 10:35:09 +0530</pubDate><guid>http://www.ankitkdev.com/blog/linux-kernel-mentorship-program/</guid><description>&lt;h3 id="introduction">Introduction&lt;/h3>
&lt;p>I have been using Linux for the last two years and gradually developed an interest in systems programming and C. The mentorship prerequisites includes tasks like building and booting the Linux kernel, writing a basic kernel module, decoding stack traces, and modifying and booting a custom kernel build.&lt;/p>
&lt;p>Somehow, my application was accepted ;-).
&lt;img alt="alt text" loading="lazy" src="http://www.ankitkdev.com/lfx-acceptance.png">&lt;/p>
&lt;p>At first, the Linux Kernel seemed quite difficult to understand what was going on. We were initially told to choose two subsystems to work on.&lt;/p></description></item><item><title>Misc Kernel Driver</title><link>http://www.ankitkdev.com/blog/misc-kernel-driver/</link><pubDate>Mon, 01 Dec 2025 22:32:00 +0530</pubDate><guid>http://www.ankitkdev.com/blog/misc-kernel-driver/</guid><description>&lt;h1 id="how-to-write-your-first-linux-kernel-driver-using-the-misc-device-framework">How to Write Your First Linux Kernel Driver Using the Misc Device Framework&lt;/h1>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>This article explains how to write a simple Linux kernel driver using the misc device framework. The misc framework is a good starting point because it automatically creates the device node when the driver registers, reducing setup complexity. In this example driver, a PID written from user space is stored in the kernel, and reading from the device triggers the driver to look up and display information about the corresponding task.&lt;/p></description></item><item><title>Install Ubuntu Server on Qemu</title><link>http://www.ankitkdev.com/blog/install-ubuntu-server-on-qemu/</link><pubDate>Sat, 16 Aug 2025 14:30:04 +0530</pubDate><guid>http://www.ankitkdev.com/blog/install-ubuntu-server-on-qemu/</guid><description>&lt;h1 id="installation-of-ubuntu-server-on-qemu-x86_64">Installation of ubuntu server on qemu-x86_64&lt;/h1>
&lt;p>At First I want to run the custom modules on linux. But this is something that is not good to do on host machine. So i searched a lot of stuff. Tinkering with buildroot, after some days i was able to run the build on qemu.&lt;/p>
&lt;p>But i found out build actually didn’t have my basic tool like &lt;code>gnu make&lt;/code>. Everytime i try to do something i need to find particular tool on &lt;code>menuconfig&lt;/code> then make the build again. Learning was so slow.&lt;/p></description></item></channel></rss>