The ESP8266 NodeMCU is a classic, cost-effective WiFi board that popularised browser-based internet control of hardware.
1. Hardware Specifications
- Processor: Single-core 32-bit Tensilica L106 processor running at 80 MHz (can be overclocked to 160 MHz).
- Logic Level: 3.3V. All pins operate on 3.3V logic.
- Memory Limits: 4 MB Flash, 80 KB SRAM.
- Wireless: Integrated 802.11 b/g/n Wi-Fi. No Bluetooth.
2. Detailed Pinout & GPIO Map (Board Labels vs. GPIO IDs)
[!IMPORTANT]
GPIO ID Discrepancies: On the ESP8266 NodeMCU, the labels printed on the board (D0–D10) do NOT correspond to the GPIO numbers used in code. When programming in OMS, you must reference the GPIO ID listed below, rather than the physical board label:
3. Critical Pin Warnings
- Flash Memory Pins (GPIO 6 - GPIO 11): These pins are internally connected to the onboard SPI flash memory. Connecting sensors or pulling these pins high/low will instantly crash the ESP8266 and corrupt the application binaries.
- Logic Tolerance: Pins are strictly 3.3V logic tolerant. Applying 5V directly to any GPIO will damage the module.
4. Compiler Settings & IDE Properties
When targeting this board, the compiler utilizes the following parameters:
- FQBN:
esp8266:esp8266:generic
- Default Flashing Baud Rate:
115200
- Flash Mode / File Type:
esp (uploaded as a consolidated binary file)
- Flash Memory Offsets:
{ bootloader: 0x0000, partitions: 0x0000, app: 0x0000 } (monolithic compilation)
- Programming Runtimes: Supports C++ (Arduino) and MicroPython.
5. Supported Blockly Board Blocks
All of the generic Board IO blocks from Section 3.2 are available: board_builtin_led (controls
D4's diagnostic LED), board_digital_write/board_digital_read, board_analog_read (the single
A0 pin), board_attach_interrupt, board_hw_timer, board_deep_sleep. This chip has no DAC,
Hall sensor, or touch hardware, so board_analog_out always falls back to a PWM approximation and
board_read_touch/board_internal_hall aren't usable.
WiFi (wifi_connect and more) requires installing the separate Wi-Fi extension first — there
is no board-specific esp8266_wifi_connect block.
6. Simulator and Flashing Diagnostics
- Simulator: Digital states and simple loops run locally. Simulated A0 input returns value 0–1023. Wireless routines are bypassed.
- Flashing Guide: Connect the USB cable. Select the COM port corresponding to your CH340 or CP2102 serial driver. Click Flash. NodeMCU includes an auto-reset circuit (using DTR/RTS flow control lines) to enter flashing mode automatically. If flashing times out, hold the FLASH (GPIO 0 / D3) button, press RST, and release FLASH to manually trigger bootloader mode.
7. Communication Buses & Electrical Capabilities
Beyond the per-pin table above, here's the board's bus-level capability summary (from its own
capabilities config):
| Bus | Details |
|---|
| UART | 1 hardware bus — TX on D10/GPIO1, RX on D9/GPIO3, shared with the USB programming port. |
| I2C | Default on D2 (SDA) / D1 (SCL). |
| SPI | Default on MOSI D7, MISO D6, SCK D5, CS D8. |
| 1-Wire | No dedicated 1-Wire hardware peripheral. Sensors like the DHT11 bit-bang the timing on any regular digital pin instead. |
| Analog (ADC) | 1 input-only pin (A0), 10-bit resolution. No hardware DAC, no touch, no Hall sensor. |
| PWM | 8 channels, 10-bit resolution, up to ~1 kHz — notably lower max frequency than the true ESP32 chips. |
Electrical limits: max 12 mA per pin (lower than ESP32/S2/S3/C3 — this chip's I/O drivers are
weaker), max 500 mA total across all pins combined.
8. Further Reading