PrajnaEdge
A curiosphere for curious minds who want to understand, experiment with, and experience technology.

Technology is a system of connections.

Modern technology is built from layers that continuously interact with one another. At the physical level, electronic devices transform electrical signals into digital information. Digital logic turns that information into computation, while processors, memory and communication interfaces provide the machinery needed to execute instructions and move data. As these components become part of embedded systems, they begin to interact with the physical world through sensors, controllers, actuators and real-time software.

But computation does not exist in isolation. Operating systems coordinate hardware and software, firmware gives specialized machines their behaviour, and communication protocols allow independent systems to exchange information. At the same time, machine learning is moving beyond the cloud into edge and on-device systems, where models must operate within real constraints such as memory, processing power, latency and energy consumption.

PrajnaEdge explores these connections as one continuous technology landscape — and takes them beyond explanation. From computing foundations and embedded systems to intelligent machines and edge AI, ideas can be understood, experimented with, and eventually turned into technology that can be experienced in the real world.

To continue exploring
Products

Technology, made tangible.

PrajnaEdge products and technology experiences are currently in development.
In Development

Playground

Experiment with intelligence beyond the cloud.

AI inference performed closer to where data is generated — optimizing model representation to reduce latency, memory footprint, and bandwidth requirements.
Cloud AI Coming Soon

Model Training & Representation

Explore how neural networks learn representations from data before compression and deployment. Future experiments will allow adjusting learning parameters—such as learning rate, epoch counts, and batch sizes—to observe loss trajectories and decision boundaries.

Edge AI Computer Vision

Image Classification

Can this image classifier maintain its intelligence while becoming small enough for the edge?

On-device AI AI-Thinker ESP32-CAM

On-device Image Classification

Run a fully quantized INT8 image-classification model directly on embedded hardware.

Edge AI Playground

Image Classification

Can this image classifier maintain its intelligence while becoming small enough for the edge?

Choose an image

Upload an image
Supports JPG, JPEG, PNG
This classifier recognizes only Apple, Banana, and Orange. Other objects may be incorrectly classified as one of these classes.

Choose the model

Model size
4.91 MiB
Largest activation
~625 KiB
Test accuracy
99.11%
Measured model accuracy
Your image is processed locally in your browser.
On-device AI · Inference

On-device Image Classification

Run a fully quantized INT8 image-classification model directly on embedded hardware.

This experiment investigates preparing a compact INT8 TensorFlow Lite model for direct inference on resource-constrained embedded hardware. The model uses the same CNN architecture as the Edge AI exploration, converted to a full INT8 representation to classify three classes: Apple, Banana, and Orange.

Model size
1.23 MiB
INT8 quantized weights
Model accuracy
99.11%
Measured test accuracy
Target hardware
AI-Thinker ESP32-CAM
Embedded microcontroller target

Explore the ideas, systems and connections that shape technology — choose any node to begin your journey.

PrajnaEdge Navigation Tree
Embedded Systems Tree
View Books →
PrajnaEdge Library

PrajnaEdge Library

Practical guides to embedded systems and engineering.

CAN Bus Debugging: From Symptoms to Root Cause Book Cover
Automotive · Embedded Protocol Debugging

CAN Bus Debugging: From Symptoms to Root Cause

  • Select
  • United States
  • United Kingdom
  • Germany
  • France
  • Spain
  • Italy
  • Netherlands
  • Japan
  • Brazil
  • Canada
  • Mexico
  • Australia
  • India

Edge AI Demonstrations

Deploying neural networks and intelligent decision loops on raw silicon targets.

Sort:
Coordination

When Machines Learned to Speak Back

How numbers became reality.

DACR-2R LadderPWMReconstruction FilterWaveform Generation

1. The Need to Influence Reality

Sensing the world is a passive act. A microcontroller can read an ADC, clocking timing intervals and translating physical temperatures, light levels, or voltages into neat digital variables. But observation alone does not change the physical state of a system. A machine that can only observe is a brain trapped in a jar—fully aware of its environment but powerless to act.

To become purposeful, a machine must eventually influence its surroundings. It needs to drive a speaker cone to vibrate air and generate sound, adjust the speed of a high-torque motor in an industrial conveyor, produce a specific reference voltage to calibrate another sensor, or generate a precise high-frequency carrier wave for radio transmission. Every active control system, from a simple thermostat to a multi-axis surgical robot, requires the ability to write actions back into physical space. Observation must give way to influence.

2. The Reverse Journey

This requirement defines a symmetrical engineering challenge. In our earlier explorations, we watched the Analog-to-Digital Converter (ADC) carve physical reality into discrete digital states. The ADC took a continuous voltage, sampled it at discrete intervals in time, and rounded it to the nearest binary code on a grid. It was a journey from continuous physics to discrete numbers.

To speak back, the machine must take the reverse journey. It must start with a discrete binary code—a neat integer stored in a CPU register—and translate it back into a continuous physical voltage. This is the domain of the Digital-to-Analog Converter (DAC). Below is a conceptual representation of this symmetry:

The Symmetry of ADC and DAC pathways
The Symmetry of ADC and DAC pathways

Figure 1: While the ADC slices continuous signals into discrete digital numbers, the DAC maps numbers back into physical voltages.

3. How a DAC Works: The Resistor Divider Intuition

How does a chip translate an abstract binary number into a real physical voltage? At its heart, a DAC is a network of resistors and switches that divide a stable Reference Voltage (VREF) down to a specific fraction.

Consider a simple resistor divider ladder. A binary code represents a set of instructions for a switch matrix. For instance, in a classic R-2R ladder architecture, each bit of the digital input code controls a corresponding physical switch. If a bit is 1, its switch connects a node in the resistor ladder to the Reference Voltage (VREF). If a bit is 0, the switch connects that node to ground. The current splits symmetrically at each R-2R junction. By summing these scaled currents, the DAC generates an output current directly proportional to the digital code, which is then buffered by an operational amplifier to output a clean, stable voltage. The hardware block diagram below illustrates this pipeline:

DAC Pipeline Block Diagram
DAC Pipeline Block Diagram

Figure 2: The internal elements of a DAC: input register, switch matrix, resistor scaling network, and output buffer.

4. Resolution: Slicing the Staircase

Just as with ADCs, a DAC's precision is governed by its Resolution. Resolution defines the number of discrete steps the DAC can use to construct its output voltage.

- An 8-bit DAC yields 28 = 256 discrete voltage steps. - A 10-bit DAC provides 210 = 1024 steps. - A 12-bit DAC provides 212 = 4096 steps, which is standard for high-quality microcontroller peripherals. - A 16-bit DAC provides 216 = 65,536 steps, used in high-fidelity audio equipment where stepped jaggedness would introduce audible distortion.

The smallest voltage change the DAC can output is called the Least Significant Bit (LSB) size. As resolution increases, the step size shrinks, transforming a coarse, jagged staircase into a smooth line. Below is a comparison of output granularity across resolutions:

DAC Resolution Step Comparison
DAC Resolution Step Comparison

Figure 3: High resolution minimizes the quantization step size, allowing the DAC to reconstruct curves with minimal distortion.

5. Reference Voltage: The Boundary Ruler

A DAC cannot output a voltage larger than the Reference Voltage (VREF) supplied to its core. VREF acts as the physical ruler that calibrates the digital steps. The relationship between the output voltage (VOUT = VREF × Digital Code⁄2N - 1), the digital code, the resolution (N), and VREF is defined as:

VOUT = VREF × Digital Code⁄2N - 1

If VREF is 3.3V, a 12-bit code of 4095 outputs exactly 3.3V, while 2048 outputs 1.65V. If VREF drifts or contains high-frequency electrical noise, that noise couples directly into VOUT = VREF × Digital Code⁄2N - 1—if the ruler expands and contracts, the measurements scale with it. Therefore, a clean, stable, and decoupled reference voltage is vital for analog precision. Below is an illustration of how VREF defines the output scaling boundaries:

Reference Voltage Scaling
Reference Voltage Scaling

Figure 4: Reference voltage dictates both the maximum output range and the individual step size (LSB) of the converter.

6. Waveform Generation: Building Curves from Steps

To generate a dynamic waveform—such as a smooth audio tone, a linear motor ramp, or a calibration pulse—the CPU writes a continuous stream of digital values to the DAC register in a periodic loop driven by timer interrupts.

For example, to generate a Sine Wave, engineers compute a table of sine values beforehand and load them into memory. Every time a timer overflows, a DMA (Direct Memory Access) channel automatically copies the next value from the table directly into the DAC data register without CPU intervention. By updating the DAC at a high, constant frequency, the discrete steps approximate a continuous curve. The illustrations below depict how different waveforms are constructed by sequencing discrete values:

Waveform Generation
Waveform Generation

Figure 5: Building Sine, Triangle, Sawtooth, and Square waveforms by outputting timed sequences of digital codes.

7. The Illusion of Continuity: Filtering the Steps

If you look closely at a raw DAC output on an oscilloscope, you will see a stair-step pattern. If this raw voltage is fed directly to a high-frequency speaker, the sharp corners of the steps (which represent high-frequency harmonic distortion) will cause an audible hiss or crackle. How do we turn these steps into a truly smooth curve?

The solution is a Reconstruction Filter. This is a low-pass analog filter placed immediately after the DAC output pin. A simple resistor-capacitor (RC) filter removes the high-frequency transitions (the sharp corners of the steps), leaving only the fundamental low-frequency analog wave. Furthermore, many physical loads (like speaker diaphragms or heavy motor coils) possess natural mechanical or inductive inertia, meaning they cannot react instantly to the steps anyway. They act as natural low-pass filters, integrating the steps into smooth physical movements. Below is a diagram of low-pass reconstruction filtering:

Low-Pass Reconstruction Filter
Low-Pass Reconstruction Filter

Figure 6: A low-pass filter integrates the sharp steps of the raw DAC output, smoothing it into a continuous analog waveform.

8. PWM: The Impostor DAC

In many embedded systems, dedicated DAC hardware is absent because it requires substantial PCB silicon and pin counts. Instead, engineers often use a timer to generate Pulse-Width Modulation (PWM) signals, mimicking an analog output.

By toggling a digital pin rapidly between 0V and 3.3V at a high frequency (often tens of kilohertz) and adjusting the Duty Cycle (the ratio of HIGH time to the total period), we can represent different voltages. If we pass this PWM stream through a low-pass RC filter, the filter integrates the square pulses, smoothing the high-frequency switching into a steady DC voltage directly proportional to the duty cycle. The diagram below illustrates this integration:

PWM Impostor DAC
PWM Impostor DAC

Figure 7: Using high-frequency PWM duty-cycle pulses combined with a low-pass filter to generate an average analog voltage.

While PWM is cheap, simple, and highly efficient for power applications (like driving LEDs or brushless motors), it is an imperfect 'impostor' DAC. It suffers from slow response times (due to filter charging delays) and contains switching ripple noise that is difficult to filter out completely. A true DAC provides a steady, immediate voltage level without switching noise. The comparison below contrasts the two methods:

PWM vs True DAC Comparison
PWM vs True DAC Comparison

Figure 8: A true DAC provides clean, instantaneous voltage steps, whereas a filtered PWM introduces exponential rise delays and ripple noise.

9. Painting with Voltage

Let's observe these conversion behaviors. In the interactive panel below, modify reference voltage, DAC resolution, and digital input codes to watch how digital values translate into analog voltages on a meter.

10. The Illusion of Smoothness

How does sequence timing and low-pass filtering shape the output waveform? In the simulator below, adjust the waveform type, update rate, resolution, and low-pass reconstruction filter cutoff to see how a continuous curve is painted.

11. Real Embedded Applications

DACs are the expressive voice of microcontrollers. They drive audio amplifiers in smart speakers, generate control voltages in industrial loops (like proportional valves), produce high-frequency diagnostic test signals in lab instruments, calibrate medical pacemakers, and execute motor speed profiling in robotics. By giving digital systems a path to write back to the physical world, the DAC completes the handshake between computational logic and physical reality.

The Expressive Handshake

Timers taught machines when to pay attention. ADCs taught machines how to translate reality into digital coordinates. DACs taught machines how to write numbers back into physical reality.

For the first time, a machine could not only understand its environment, but actively influence it. Yet as these sensory and output capabilities expanded, a new system challenge emerged. Managing high-speed sampling, responding, keeping time, and communicating all at once required synchronized scheduling. The next engineering frontier was no longer sensing or speaking—it was scheduling what deserved the processor's attention next.

A processor without a DAC is a mind without a voice—fully capable of thought, but unable to sing.
System Tree Node Coordination

PrajnaEdge

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.

PrajnaEdge is a technology company created by Devaharsha Meesarapu.

CREATOR PROFILE

Devaharsha Meesarapu

Embedded Systems • Firmware • Edge AI

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.

View Resume →

ABOUT ME

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.

CONNECT

LinkedIn → GitHub →

Interactive Career Journey

BTech · ECE

Foundations

Where it all began — understanding the physical layer of computation. Circuits, signals, and systems gave me a mental model of how information moves through hardware.

⬡
Connects to Systems
Understanding circuits directly enables writing firmware that talks to peripherals at the register level.
What it is
BTech in Electronics and Communication
Undergraduate foundation covering analog & digital circuits, signal processing, microprocessors, and communication systems.
CircuitsSignal ProcessingMicroprocessorsVLSI
What I did
Core Engineering Fundamentals
Studied semiconductor physics, digital logic design, and embedded microcontrollers. Built prototypes using 8-bit MCUs.
8051Logic DesignPCB Basics
What I learned
The Hardware Mental Model
Every software abstraction sits on physical reality. Understanding silicon teaches you why timing, power, and noise are first-class engineering problems.
Let's Connect
Interested in embedded systems, AI, or building something meaningful? I'd love to hear from you.
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."

← Return to Systems Tree
Select Domain
Explore application domains branching from the Systems Tree
Automotive
Aerospace & Defence
Consumer
Embedded AI
Industrial
Medical
Multimedia
Network & Connectivity
Robotics
Explore Active Systems Tree →
← Return to Systems Tree
Select Depth
Examine computation through architectural depth layers
Architecture
Controller
Digital
Programming
Processor
Explore Processors → Explore Controllers →

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.