Skip to content
BoKSA

Lab Tools for Prototyping

Lab Tools for Prototyping

Introduction

Firmware bugs feel like software problems until you measure the hardware. Lab tools let you see voltage, continuity, waveforms, and serial bits — turning guesses into facts. You do not need a €10 000 bench on day one; a multimeter, a USB logic analyzer, and occasional access to an oscilloscope cover most HBO-ICT embedded projects.

This article explains what each tool does, when to reach for it, and where to learn more on video.


Multimeter — the first tool to buy

A multimeter measures voltage, current, resistance, and often continuity (beep when wires touch).

Measurement Use in embedded
DC voltage Confirm 3.3 V / 5 V rails, battery level
DC current How much the board draws (watch fuse rating)
Resistance Resistor value, trace continuity
Continuity Find shorts, broken wires, GND connection

COM jack = common (black probe, usually GND). VΩmA jack for most measurements. 10 A jack only for high current — internal fuse blows if you overload.

In plain terms

A multimeter answers "is electricity actually here?" and "how much?" Like a thermometer for your circuit.

Safe habits

  • Start on highest voltage range, then step down.
  • Current is measured in series — wrong jack + high current = blown fuse.
  • Never measure resistance on a live circuit.

Logic analyzer — see digital timing

A logic analyzer records many digital channels over time — perfect for UART, SPI, I²C, PWM. Software (e.g. PulseView) decodes protocols.

Good for Not for
Baud rate wrong? Analog ripple on power rail
I²C NACK storms Sub-100 mV noise
Pulse width

Connect GND to target GND. Clip on SDA, SCL, TX, RX. Match voltage tolerance (3.3 V vs 5 V probes).


Oscilloscope — see analog shape

An oscilloscope plots voltage vs time — rising edges, ringing, noise, PWM duty cycle.

Good for When students need it
PWM verification Motor projects, audio
Power supply ripple Random resets
UART eye (advanced) High-speed debug
Button bounce (visual) Debouncing labs

Lab scopes are intimidating at first — use auto-scale, one channel, DC coupling, and a known 3.3 V GPIO toggle.


Other bench helpers

Tool Role
Soldering iron Permanent connections — see Soldering basics
Breadboard + jumpers Quick prototypes
Component tester Identify random resistors, transistors
Flux Better solder joints on SMD practice boards

Videos — multimeter

Complete beginner tutorial

How to Use a Multimeter for Beginners — voltage, resistance, continuity, amps.

In-depth tutorial

THE BEST Multimeter tutorial (HD)

Buying advice

EEVblog #75 - Digital Multimeter Buying Guide for Beginners


Videos — oscilloscope

Basics

Oscilloscope Tutorial (Basics 101)

What is an oscilloscope

How to use an oscilloscope / What is an oscilloscope


Videos — logic analyzer

Cheap analyzer on SPI, I²C, UART

Cheap logic analyzer SPI i2c UART

Triggering on a data pattern

LogicPort USB Logic Analyzer Triggering on a Data Pattern

Complex triggering

LogicPort Complex Triggering


Which tool when?

Symptom Try first
LED never lights Multimeter: voltage at LED, continuity
Wrong sensor values Logic analyzer on I²C, check address
Random resets Multimeter on 3.3 V rail under load; scope for ripple
UART garbage Logic analyzer decode, verify baud
Motor whine Scope on PWM pin — frequency and duty

Relevant topics


Starting points

  1. Measure 3.3 V and GND on your MCU board — record exact value.
  2. Continuity beep from MCU GND to USB shell GND.
  3. Capture UART TX with logic analyzer at 115200 — read ASCII.
  4. Scope one PWM pin while changing duty in code.

Focus points

  • Common ground between tool and device.
  • Fuse in multimeter — replace if blown, learn why.
  • 10× scope probe setting affects voltage readout — check attenuation.
  • Cheap analyzers are enough for I²C/UART at student speeds.

Key points

  • Multimeter — voltage, current, resistance, continuity — first purchase.
  • Logic analyzer — digital buses and serial decode.
  • Oscilloscope — analog waveforms, PWM, power integrity.
  • Match the tool to the symptom; measure before rewriting code.