Explore the ideas, systems and connections that shape technology — choose any node to begin your journey.
Embedded Systems Tree
Sort by:
Edge AI Demonstrations
Deploying neural networks and intelligent decision loops on raw silicon targets.
Sort:
Operating Systems
Remembering the Moment
How the Kernel preserves a Process between interruptions.
KernelProcessPCBMemoryOperating Systems
1. The Bookmark Analogy
Imagine reading a large, complex textbook. Suddenly, the phone rings.
You cannot simply close the book and walk away. If you do, you will lose your place and have to search through hundreds of pages to find where you left off. Instead, you perform a simple action: you place a bookmark on the page.
The bookmark doesn't contain the story of the book. It is simply a tiny record that preserves your exact place, allowing you to close the book, take the call, and later open the textbook to continue reading as if you had never been interrupted.
The Kernel needs a bookmark for every process.
2. The dedicated Record: PCB
To solve this problem, the Kernel creates a dedicated tracking record for every process the moment it is born.
Whenever a process is interrupted, the Kernel does not simply wipe the CPU core's state. Instead, it copies the process's current execution status into this tracking record. When the process is selected to run again, the Kernel reads this record, restores the state, and points the CPU back to the exact instruction where it was paused.
This dedicated record is called the Process Control Block (PCB).
3. The Preservation Loop
The lifecycle of preemption and state preservation operates in a continuous loop:
4. Inside the PCB
What information must a "bookmark" store to preserve a process? Rather than capturing the entire memory footprint of the program, the PCB holds key metadata fields:
Process ID (PID)
A unique integer assigned by the OS to identify the process across the entire system.
Process State
Tracks where the process sits in its lifecycle: Running, Ready to execute, or Waiting on hardware resources.
Program Counter (PC)
The memory address pointer indicating exactly which machine instruction the process must execute next.
Registers
Temporary numeric slots inside the CPU holding scratch variables and arithmetic offsets at the split-second of preemption.
Stack Pointer
Locates the current nested layer of function calls and local variables stored in transient RAM.
Memory Management Info
Maps the boundaries of the process's private memory range (pages, segment tables) to protect it from other tasks.
System Resources
Tracks active resources allocated to the task, including open file descriptors, network sockets, or active peripheral channels.
5. Where Does the PCB Live?
A running user process executes instructions within its own memory bounds. But a process is not permitted to touch or modify its own "bookmark." If it could, a bug inside a program could overwrite its own state or access the bookmarks of other programs, compromising security.
Therefore, PCBs live entirely inside Kernel Memory.
When a process executes, it sits in User Space. But the moment an interrupt triggers, control swaps to Supervisor Mode, and the Kernel saves the state into its own protected region of RAM:
PHYSICAL RAM LAYOUT
6. The Limit of Memory
The Process Control Block ensures that no task is lost. Because of these bookmarks, the Kernel has the power to capture the exact state of any execution line.
But memory alone does not bring a process back to life. Having a bookmark inside a book does not open the page or begin the reading.
Engineering concepts you don't just read — you experience.
Founded in 2026.
PrajnaEdge is a technology company exploring the space between understanding technology, experimenting with ideas, and turning them into things that can be experienced.
Our Mission
To make technology easier to explore, deeper to understand, and more exciting to experience.
Our Vision
To build a technology ecosystem where curiosity, experimentation and creation continuously lead to one another.
Where it began
Embedded Systems
PrajnaEdge began with Embedded Systems — exploring the foundations that connect hardware, software and intelligent computation.
The first technology universe is built around that foundation. The journey will expand as new ideas, experiments and products emerge.
I am the engineer behind the design, development, and content of PrajnaEdge. I build low-level systems where code directly controls hardware, bridging the gap between register-level silicon behavior and intelligent edge decision loops.
I am an Embedded Firmware Engineer focused on developing software for resource-constrained systems. My experience spans bare-metal firmware, device drivers, microcontroller peripherals, and communication protocols, working across the boundary between hardware and software.
My work has involved microcontroller-based systems, real-time behaviour, hardware interfaces, and communication technologies such as CAN, CAN FD, UART, SPI, and I²C. I am particularly interested in understanding systems from the lowest level upward—from registers and peripherals to intelligent edge systems.
ENGINEERING PHILOSOPHY
Engineering is not just about writing code; it is about managing constraints, timings, and physical hardware characteristics. True mastery of complex systems comes from understanding the interactions across different layers of the stack.
This conviction is why I built PrajnaEdge—to bridge the gap between conceptual theory and direct, register-level physical reality.
Open to collaborations, research, and interesting engineering conversations.
Help Improve PrajnaEdge
Found something to improve? I'd love to hear your thoughts.
Bare Metal
Software that runs directly on hardware without an operating system.
Applications
↑
Operating Systems
YOU ARE HERE
Bare Metal
Processor
↑
Hardware
"Every embedded application begins long before main()."
Operating Systems
An Operating System manages hardware and software resources so complex applications can work efficiently.
Applications
↑
YOU ARE HERE
Operating Systems
Bare Metal
↑
Processor
↑
Hardware
"When one loop is no longer enough to carry the burden."
Support PrajnaEdge
PrajnaEdge is an independent education platform built to make knowledge freely accessible.
If you find PrajnaEdge useful, you can support its continued development.
Your support helps fund the time, tools, infrastructure, and experimentation that go into building and maintaining PrajnaEdge.
Select Region
Select Amount
₹
Select an amount to support PrajnaEdge.
Legal Information
Product Terms & Licensing
1. Terms of Use
PrajnaEdge is an interactive learning platform designed for systems engineers, developers, and technology enthusiasts. The educational materials, simulation blocks, and visual code tracers are provided for instruction and concept validation. We make no warranty regarding their completeness or applicability to real-world industrial systems.
PrajnaEdge is committed to learning privacy. We do not sell user data. Analytical event tracking is used solely to study click telemetry and help improve visual guides.
