ESP32 WiFi/Bluetooth DevKit: RF-Aware PCB Design

Modified: Mar. 5, 2026

Published: Mar. 5, 2026

Become Contributor Expert Support

This lesson introduces RF-aware PCB design through a practical project: an ESP32-WROOM-32 development board with WiFi and Bluetooth. You will design the schematic with a CP2102N USB-UART bridge and auto-reset circuit, then lay out a 2-layer PCB that respects the antenna keepout zone and maintains ground plane continuity for wireless performance. #KiCad #ESP32 #RFDesign

What We Are Building

Board specifications:

Bill of Materials

ESP32 Module Overview

Key Pins

Strapping Pins

The ESP32 samples several GPIO pins at reset to determine boot mode and other configuration. The critical ones for this board:

Do not connect heavy loads to GPIO0, GPIO2, GPIO5, GPIO12, or GPIO15 without understanding their strapping behavior. The ESP32 datasheet and the WROOM-32 module datasheet both document these requirements.

RF-Aware Design Principles

This is what separates an ESP32 board that works reliably from one that drops WiFi connections or has poor range. The layout around the antenna area directly affects wireless performance.

Antenna Keepout Summary

Schematic Capture

Create a new KiCad project named esp32-devkit. Open the schematic editor and build the following sub-circuits.

Power Supply

1. Place the USB Micro-B connector. Add USB_B_Micro from the Connector library. This provides VBUS (5V), D+, D-, ID, and GND.

2. Add VBUS protection. Connect VBUS through polyfuse F1 (500 mA) to a net labeled VBUS_5V. Place a 4.7 µF decoupling capacitor (C7) from VBUS_5V to GND near the connector.

3. Place the AMS1117-3.3 LDO (SOT-223). Connect VBUS_5V to the input pin through a 10 µF capacitor (C1). Connect the output to a +3V3 power net through a 10 µF capacitor (C2). The AMS1117 also needs the input cap for stability.

4. Add power flags. Place PWR_FLAG symbols on +3V3 and GND if ERC reports undriven power nets.

ESP32-WROOM-32 Module

1. Place the ESP32 module. Add ESP32-WROOM-32 from the RF_Module library. The symbol shows all exposed pins of the module including the ground pad.

2. Connect all power pins. Wire every VDD pin to +3V3 and every GND pin (including the large ground pad) to GND. The WROOM-32 has multiple ground pins; all must be connected for proper RF return currents.

3. EN pin circuit. Connect EN to +3V3 through a 10 kΩ pull-up resistor (R1). Place a 100 nF capacitor (C6) from EN to GND. This RC filter prevents noise from accidentally resetting the module. The EN pin also connects to the auto-reset circuit and the EN pushbutton (SW1).

4. GPIO0 strapping. Connect GPIO0 to +3V3 through a 10 kΩ pull-up resistor (R2). This ensures normal boot from flash. GPIO0 also connects to the auto-reset circuit and the BOOT pushbutton (SW2).

5. UART0 connections. Connect TXD0 (GPIO1) to the CP2102N RXD pin. Connect RXD0 (GPIO3) to the CP2102N TXD pin. Note the crossover: the ESP32 TX goes to the bridge RX, and vice versa.

6. Decoupling capacitors. Place 100 nF caps (C3, C4) on the VDD pins, as close to the module as possible in the schematic. Physical placement matters more, but schematic proximity helps during layout.

7. User LED. Connect GPIO2 through a 330 ohm resistor (R5) to the anode of D1 (blue LED), cathode to GND. GPIO2 is safe to use as a user LED after boot completes.

8. GPIO headers. Place two 1x19 pin headers (J2, J3) and route all remaining GPIO pins to them. Follow the ESP32-DevKitC pinout order if you want compatibility with existing tutorials and shields.

CP2102N USB-UART Bridge

1. Place the CP2102N. Add CP2102N-A02-GQFN28 from the Interface_USB library (or create a custom symbol if not available). The CP2102N has an internal oscillator, so you do not need an external 12 MHz crystal. This simplifies the design compared to the older CP2102.

2. USB data lines. Connect the USB Micro-B D+ and D- pins to the CP2102N’s D+ and D- pins. The CP2102N handles all USB protocol internally.

3. Power connections. Connect the CP2102N VDD pin to +3V3 and VBUS to the VBUS pin (if available on the package) or to +3V3 through the regulator. Add a 100 nF decoupling capacitor (C5) from VDD to GND.

4. UART pins. Connect CP2102N TXD to ESP32 RXD0 (GPIO3). Connect CP2102N RXD to ESP32 TXD0 (GPIO1).

5. Control signals. Bring out the RTS and DTR pins. These connect to the auto-reset circuit described next. The CP2102N asserts these signals when the programming tool (esptool or Arduino IDE) requests a reset into bootloader mode.

Auto-Reset Circuit

This is the circuit that makes one-click programming possible. Without it, you would need to hold the BOOT button, press EN, release BOOT, and then click upload every time you flash new firmware.

1. Transistor Q1 (controls EN). Connect the collector to the EN net. Connect the emitter to GND. Connect the base through a 10 kΩ resistor (R3) to the RTS signal from CP2102N.

2. Transistor Q2 (controls GPIO0). Connect the collector to the GPIO0 net. Connect the emitter to GND. Connect the base through a 10 kΩ resistor (R4) to the DTR signal from CP2102N.

3. Cross-coupling. Add a 100 nF capacitor from DTR to the EN net (in parallel with Q1’s path). Add a 100 nF capacitor from RTS to the GPIO0 net (in parallel with Q2’s path). This capacitor coupling ensures the correct timing sequence. The exact topology follows the ESP32-DevKitC reference design published by Espressif.

4. Manual buttons. Wire SW1 (EN button) between the EN net and GND. Wire SW2 (BOOT button) between GPIO0 and GND. These allow manual reset and bootloader entry when no USB is connected.

ERC and Footprint Assignment

1. Run ERC. Click Inspect > Electrical Rules Checker. Common warnings to address: unconnected GPIO pins (add “no connect” flags if intentionally unused), missing power flags, and conflicting pin types on the USB data lines.

2. Assign footprints. Open Tools > Assign Footprints. Key assignments:

   • ESP32-WROOM-32: RF_Module:ESP32-WROOM-32 (the official KiCad footprint includes the antenna keepout courtyard)
   • CP2102N: Package_DFN_QFN:QFN-28-1EP_5x5mm_P0.5mm_EP3.35x3.35mm
   • AMS1117-3.3: Package_TO_SOT_SMD:SOT-223-3_TabPin2
   • USB Micro-B: Select a footprint matching your connector (e.g., Connector_USB:USB_Micro-B_Molex_47346-0001)
   • 0402 passives: Capacitor_SMD:C_0402_1005Metric and Resistor_SMD:R_0402_1005Metric
   • 0805 bulk caps: Capacitor_SMD:C_0805_2012Metric
   • Tactile switches: Button_Switch_SMD:SW_Push_1P1T_NO_6x3.5mm

3. Generate the netlist. Click Tools > Update PCB from Schematic (or press F8) to transfer the schematic to the PCB editor.

PCB Layout

Board Outline and Module Placement

1. Draw the board outline. Switch to the Edge.Cuts layer and draw a rectangle approximately 55mm x 28mm. The ESP32 module is 18mm wide, so 28mm gives adequate clearance on both sides for pin headers.

2. Place the ESP32 module at one short edge. Position the module so the antenna section extends to (or slightly beyond) the board edge. The antenna must point outward with no board material or components blocking it. Align the module center with the board center horizontally.

3. Place the USB connector at the opposite short edge. This maximizes the distance between the USB connector (a source of digital noise) and the antenna. The USB connector’s metal shell should align flush with the board edge.

4. Place the LDO between USB and ESP32. Position the AMS1117-3.3 and its capacitors along the power path from USB to the module. Keep the power traces short and direct.

5. Place the CP2102N near the USB connector. The USB data lines should be as short as possible between the connector and the UART bridge. Place C5 (decoupling) adjacent to the CP2102N VDD pin.

Antenna Keepout Zone in KiCad

1. Identify the antenna area. The ESP32-WROOM-32 footprint in KiCad includes a courtyard that marks the antenna region. The antenna extends approximately 5mm beyond the metal shielding can at the top of the module.

2. Draw a Rule Area. Select Add Rule Area (also called Keep Out Zone) from the right toolbar. In the properties dialog, check “Keep out copper pour” for all copper layers (F.Cu, B.Cu). Draw a rectangle covering the entire antenna area plus 2mm margin on all sides.

3. Verify no copper exists in the keepout. After filling zones (press B), visually inspect the antenna area. There should be no ground pour, no traces, and no vias within the keepout rectangle on any copper layer.

4. Board edge alignment. If the antenna extends beyond the board edge, the Edge.Cuts outline should follow the module edge at the antenna end. Some designers extend the board slightly beyond the antenna for mechanical protection, but leave the extended area completely free of copper.

Ground Pour and Plane Strategy

1. Create GND zone on F.Cu. Add a filled zone covering the entire board, assigned to the GND net. Set zone priority to 0.

2. Create GND zone on B.Cu. Same process on B.Cu, also assigned to GND with priority 0.

3. Add via stitching. Place GND vias every 3 to 5mm across the board area (except in the antenna keepout zone). Concentrate stitching vias around the ESP32 module’s ground pad area and along the board edges.

4. Verify ground continuity. After filling zones, use the net inspector to confirm that all GND pads are connected to the same net. Look for isolated ground islands caused by trace routing that could split the pour.

Component Placement Summary

Trace Routing Tips

Design Rules for JLCPCB 2-Layer

Set these minimum design rules in Board Setup > Design Rules > Constraints:

Running DRC

1. Fill all zones (Edit > Fill All Zones, or press B).

2. Open Inspect > Design Rules Checker.

3. Fix any clearance violations, unconnected nets, or minimum width violations.

4. Pay special attention to the antenna keepout zone. Verify that DRC does not report any copper inside the keepout area.

Manufacturing

The Gerber and drill file export process is the same as Lesson 3. Generate Gerbers for F.Cu, B.Cu, F.Mask, B.Mask, F.SilkS, B.SilkS, and Edge.Cuts, plus the drill file. Zip everything and upload to JLCPCB.

Firmware: WiFi Scan

Once the board is assembled, verify that the ESP32 boots correctly and WiFi works by running a network scan. We use the Arduino framework for simplicity, since it handles all the ESP-IDF configuration behind the scenes.

Arduino IDE Setup

1. Install ESP32 board support. In Arduino IDE, go to File > Preferences and add https://espressif.github.io/arduino-esp32/package_esp32_index.json to the Additional Board Manager URLs. Then open Tools > Board > Boards Manager, search for “esp32”, and install the Espressif package.

2. Select the board. Go to Tools > Board > ESP32 Arduino and select “ESP32 Dev Module”.

3. Select the port. Plug in the board via USB. The CP2102N should enumerate as a serial port. On Linux it appears as /dev/ttyUSB0, on Windows as a COM port, and on macOS as /dev/tty.usbserial-XXXX. Select it under Tools > Port.

4. Set upload speed. Under Tools > Upload Speed, select 921600 for fast programming. The auto-reset circuit handles the bootloader entry automatically.

WiFi Scan Sketch

/*
 * ESP32 WiFi Scanner
 * Scans for nearby WiFi networks and prints results over serial.
 * Upload via USB with auto-reset (just click Upload in Arduino IDE).
 */

#include <WiFi.h>

void setup() {
    Serial.begin(115200);
    delay(1000);
    Serial.println("ESP32 WiFi Scanner");
    Serial.println("==================");

    WiFi.mode(WIFI_STA);
    WiFi.disconnect();
    delay(100);

    Serial.println("Setup complete. Starting scan...\n");
}

void loop() {
    Serial.println("Scanning for networks...");
    int numNetworks = WiFi.scanNetworks();

    if (numNetworks == 0) {
        Serial.println("No networks found.");
    } else {
        Serial.print(numNetworks);
        Serial.println(" networks found:\n");
        Serial.println("  # | SSID                             | RSSI | Ch | Encryption");
        Serial.println("----+----------------------------------+------+----+-----------");

        for (int i = 0; i < numNetworks; i++) {
            char line[100];
            const char* encType;

            switch (WiFi.encryptionType(i)) {
                case WIFI_AUTH_OPEN:            encType = "Open";     break;
                case WIFI_AUTH_WEP:             encType = "WEP";      break;
                case WIFI_AUTH_WPA_PSK:         encType = "WPA";      break;
                case WIFI_AUTH_WPA2_PSK:        encType = "WPA2";     break;
                case WIFI_AUTH_WPA_WPA2_PSK:    encType = "WPA/WPA2"; break;
                case WIFI_AUTH_WPA2_ENTERPRISE: encType = "WPA2-Ent"; break;
                default:                        encType = "Unknown";  break;
            }

            snprintf(line, sizeof(line), "%3d | %-32s | %4d | %2d | %s",
                     i + 1,
                     WiFi.SSID(i).c_str(),
                     WiFi.RSSI(i),
                     WiFi.channel(i),
                     encType);
            Serial.println(line);
        }
    }

    Serial.println("\nNext scan in 10 seconds...\n");
    delay(10000);
}

Expected Output

Open the Serial Monitor at 115200 baud after uploading. You should see output similar to this:

ESP32 WiFi Scanner
==================
Setup complete. Starting scan...

Scanning for networks...
5 networks found:

  # | SSID                             | RSSI | Ch | Encryption
----+----------------------------------+------+----+-----------
  1 | HomeNetwork                      |  -42 |  6 | WPA2
  2 | Office_5G                        |  -55 | 36 | WPA2
  3 | CoffeeShop                       |  -68 |  1 | WPA/WPA2
  4 | IoT_Sensors                      |  -71 | 11 | WPA2
  5 | Guest_Network                    |  -78 |  6 | Open

Next scan in 10 seconds...

Troubleshooting

If the board does not respond after clicking Upload:

• Check the auto-reset circuit. Hold the BOOT button, press and release EN, then release BOOT. Click Upload again. If this works but auto-reset does not, inspect the transistor wiring and the DTR/RTS connections from the CP2102N.
• Verify 3.3V power. Measure the voltage on the ESP32 VDD pins. It should be 3.3V plus or minus 0.1V. Low voltage (below 3.0V) indicates an LDO or capacitor problem.
• Check serial port. If no serial port appears when you plug in the board, the CP2102N may not be soldered properly. Check for solder bridges on the QFN pads, especially between adjacent pins.
• WiFi scan returns zero networks. Check the antenna keepout zone on your PCB. Copper under the antenna is the most common cause of poor WiFi performance on custom ESP32 boards. Also verify that no metal enclosure or your hand is covering the antenna during testing.

What You Have Learned