ESP32 Getting Started: First Flash and WiFi Scan

The ESP32 packs dual-core processing, WiFi, Bluetooth and rich peripherals into a board cheaper than a pizza. Getting from boxed board to first wireless sketch takes twenty minutes once you know the two quirks. Bootloader button and board manager.

At a glance: 7 minute guide · part 1 of 10 in the complete IoT and ESP32 guide track · includes a worked example and a quick-reference table.

Board support and wiring

Here is the working theory in one pass. Install the ESP32 board package via Boards Manager, then select your exact variant (DevKit, WROOM, C3…). Most boards auto-enter bootloader; older ones need BOOT held during "Connecting…". USB power is enough no external supply required for the first flash.

S	p	e	c
E	S	P	3	2		(	W	R	O	O	M	)
N	o	t	e
Cores	2 × 240 MHz	Plenty for WiFi + logic
Flash/RAM	4 MB / ~520 KB	PSRAM on some variants
Logic level	3.3 V	Not 5 V tolerant
WiFi	802.11 b/g/n	2.4 GHz only
Deep sleep	~10 µA	Battery projects

First sketch: scan the air

The WiFiScan example lists every access point with RSSI. It proves the radio, antenna and toolchain in one run. Read RSSI as signal strength: −40 dBm excellent, −80 dBm marginal. This sketch is also the tool you will reuse for site surveys.

Two habits from day one

Set a unique hostname and put WiFi reconnect logic in loop() examples often connect once in setup() and die when the router reboots. Our reconnection guide covers the robust pattern.

How to apply this in your build

Work through the sequence below each step assumes the previous one passed. For numbers that need calculating, the linked tools at the end of this guide do the arithmetic instantly.

1. Install the ESP32 board package and drivers
2. Select the exact board and port from Tools
3. Open the WiFiScan example and upload
4. Open Serial Monitor at 115200 and read the networks list

Worked example

A first scan printing 9 networks, strongest at −44 dBm, confirms the radio path works. The same sketch run near a planned mounting spot predicts whether an external antenna is needed. Run the numbers yourself with the Battery Life Calculator and the result should agree to within rounding.

Practical note from the bench. Keep a dedicated "test" ESP32 flashed with WiFiScan and a GPIO blink it isolates toolchain problems from project problems in minutes.

Common mistakes to avoid

• Holding BOOT only after "Connecting…" appears timing missed, upload fails
• Feeding 5 V signals into 3.3 V GPIO
• Assuming the 5 V pin outputs regulated 5 V from USB on every variant

Key takeaways

• Board support and wiring the foundation of this guide; revisit it if any measurement here surprises you.
• First sketch: scan the air the foundation of this guide; revisit it if any measurement here surprises you.
• Two habits from day one the foundation of this guide; revisit it if any measurement here surprises you.

Who this guide is for

Beginners get a single focused topic instead of a whole textbook chapter. It works as an early stop in the complete IoT and ESP32 guide path. Intermediate readers use it as a reference the table, the worked example and the mistake list answer the questions that come up mid-build. If you teach, the structure (theory, application, example, failure modes) maps cleanly onto a lab session.

What you need before starting

Nothing exotic: the parts or tools named in the guide, a multimeter. The Battery Life Calculator open in a tab. Install the ESP32 board package and drivers before you begin the guide assumes it and keep the quick-reference table above within sight while you work through the steps.

Quick reference card

Aspect	Where to find it in this guide
Core theory	Board support and wiring
Application steps	How to apply this in your build
Worked numbers	Worked example
Failure modes	Common mistakes to avoid

How this fits the complete IoT and ESP32 guide track

This guide is one stop in the structured learning path. Start from the complete IoT and ESP32 guide complete guide for the full map, or continue with ESP32 strapping pins and robust WiFi reconnection. For the arithmetic, open the Battery Life Calculator.

Frequently asked questions

Why will my ESP32 not upload? Ninety percent of cases: wrong board variant, or the bootloader needs the BOOT button. Both are Tools-menu fixes.

Can I program ESP32 like an Arduino? Yes the Arduino core, plus PlatformIO or ESP-IDF when you need more control.

Is there a calculator for this? Yes the Battery Life Calculator tool runs the formulas from this guide instantly, client-side, with no signup.

Continue the learning path

• The complete iot, sensors & esp32 guide: IoT, Sensors & ESP32 complete guide
• Read next: lorawan for beginners: long-range iot without wifi
• Also in this track: antenna basics for iot: wavelength, gain and matching
• Continue with: biomedical sensors: how wearables measure the body
• Calculate as you go: battery life estimator · LM317 regulator designer · wire gauge checker
• Bookmark this page against the day a measurement surprises you. Most readers return to the table and the mistake list first, and that is the correct order.

Measurement discipline

Keep a lab notebook entry for every build in this track. The measured values, the deviations from the guide and the reason for each. Six months from now, those notes are worth more than any tutorial. They describe your bench and your components rather than a general case.

When a result here disagrees with your expectation, write down both numbers before changing anything. The gap between predicted and measured is where the real engineering lives. It is usually a tolerance, a parasitic or an assumption that was never checked.

Hard-won notes

Measure current during transmit bursts. Sags under load are power problems, no firmware fixes those.

Location, then device, then measurement. Document the tree before flashing the first device.

One more thing before you build

A note on radio current, which defines this track: transmit bursts draw in spikes, not averages. Scope the supply or log RSSI before concluding the protocol is at fault.

Working through Board support and wiringand First sketch scan the air with that habit in mind takes minutes, and it is the difference between reading about this topic and owning it.

Extended Application Notes

This section expands the practical application of esp32 getting started: first flash and wifi scan beyond the worked example, into the situations builders actually meet. Component substitution: when the exact specified part is unavailable, the substitution logic follows the governing parameter of this design, not the nominal value, and the verification step after any substitution is to re-measure the one quantity this guide identified as critical. Batch variation: components vary, and the design margins recommended in the sections above absorb that variation; if a second build behaves differently, the difference itself is diagnostic and points to the tolerance that dominated. Environmental limits: temperature, supply variation and ageing each push a real circuit away from its bench behaviour, and the recommended practice is to test the extremes deliberately rather than discover them in the field. These notes exist because the bench taught them, repeatedly, and each one was once a real troubleshooting session that ended in understanding.

Failure Analysis in Depth

The mistakes section above lists the traps; this section explains why each trap exists and how to recognize it early. Holding BOOT only after "Connecting…" appears timing missed, upload fails Feeding 5 V signals into 3.3 V GPIO Assuming the 5 V pin outputs regulated 5 V from USB on every variant. Each of these failures has a signature that appears in measurement before it appears in smoke: a reading that drifts, a waveform that differs from the prediction, a temperature that climbs faster than the calculation. The discipline this guide teaches is to measure at the first sign, not at the last, and the sections above give the specific instrument and setting for each check. Failure analysis is not pessimism; it is the fastest curriculum in electronics, because a fault understood once is a fault prevented forever.

Pre-Build Checklist

Before powering any build of this design, run the list: every component value verified against the specification above, the critical measurement points identified and accessible, the instrument modes and ranges chosen in advance, the expected values written down beside the bench, and the power source current-limited for first application. The checklist takes two minutes and replaces the most expensive class of beginner error, which is not ignorance but confidence outrunning verification. Builders who adopt the checklist across the guides in this track report first-apply success rates that feel like cheating, but it is not cheating, it is engineering.

What Comes Next

Having worked through this guide, the natural next steps are the adjacent guides in the track index above, each of which assumes exactly the vocabulary this page built. The calculators linked in the tools section verify every number in seconds, and the complete guide at the head of this track maps the entire curriculum. Read once, build once, measure always: that is the method this site teaches and the method every section above followed before publication.

Theory in Practice, Extended

The theory section of esp32 getting started: first flash and wifi scan deserves one more pass with the bench in mind, because knowing a relationship and applying it under constraint are different skills. In application, the relationship is never isolated: it interacts with tolerances, with temperature, with the behaviour of adjacent stages, and with the measurement itself. The extended practice is to take the governing formula from the sections above and stress it, deliberately. Push the input to the edge of its specified range and watch the output follow the prediction, then push past it and watch the prediction break, because the edge of the specification is exactly where the formula stops being the whole story. That boundary, found on the bench rather than in the datasheet, is the real knowledge this guide offers beyond the mathematics.

Component Sourcing and Substitution Notes

Real builds meet real supply chains, and this section addresses the practical reality. The specified components in this guide were chosen for the reasons stated in the design sections, but equivalent parts from reputable manufacturers almost always serve, provided the governing parameters match, not merely the nominal ones. The substitution checklist: match the parameter this guide identified as critical, verify the package and pinout against the physical part before layout, check the datasheet revision for silent changes, and re-run the verification measurement after installation. Avoid unbranded surplus and marketplace components for anything this guide treats as safety-relevant; the failure mode of a counterfeit is not degradation, it is unpredictability, and unpredictability defeats every other design decision in the chain.

Instrumentation for This Design

Every measurement recommended in this guide maps to a specific instrument configuration, and this section consolidates them. Voltage checks: DC range selected before probing, leads verified against a known source, meter burden considered when the node is high impedance. Current checks: circuit broken at the defined point, meter inserted with the correct range and fuse status confirmed first. Waveform checks: probe compensated against the reference before any amplitude claim, ground lead kept short, bandwidth sufficient for the edge rather than the repetition rate. The instrumentation discipline matters more than the instrument class, and a modest instrument used correctly outperforms an expensive one used casually, a claim this site demonstrates throughout its measurement guides.

Documentation Template for This Build

Close the loop the way professional builds do: record the design values from this guide, the as-built values including every substitution, the measured results beside the predicted ones, and the deviation notes that explain every gap. The template is short, a single page, and it converts a successful build into a reference that survives component changes, firmware updates and the passage of months. Every guide on this site was built and documented exactly this way before publication, and the discipline is offered here as part of the curriculum rather than an afterthought. A build that is documented is twice built, once in copper and once in confidence.