WeMos D1 Mini (ESP8266): Getting Started
Time to complete: 2–10min; Level of difficulty: Beginner
This guide will show you how to configure the WeMos D1 Mini to start programming its onboard ESP8266 Serial to Wi-Fi module. After completing this you’ll be able to simply connect the board to the USB port and start programming it using the Arduino IDE.
List of Materials
- 1 x WeMos ESP8266 D1 Mini V2 IoT Kit (5-Piece)
The WeMos D1 Mini Development Board
The WeMos family of boards is one of the latest additions to the ESP8266-based Internet Of Things (IoT) ecosystem.
The Wemos D1 Mini small form-factor and wide range of plug-and-play shields make it an ideal solution for quickly getting started with programming the ESP8266 SoC.
What is the ESP8266?
We've written a very detailed account of the ESP8266 System On a Chip (SoC), if you want to find out the full story behind this little chip we invite you to read it:
In short, the ESP8266 Serial to Wi-Fi SoC was released in the summer of 2014, and it has become a center point in the development of inexpensive IoT applications. Given that Wi-Fi chips have been available for around a decade, you may be wondering what makes the ESP8266 special. Besides being released at the 'right' time, meaning as Internet Of Things (IoT) have entered everyday speak among developers and tech entrepreneurs, there are a few reasons behind its meteoric rise in popularity:
- Very capable microcontroller (32-bit 80MHz, built-in Wi-Fi, adequate I/O buses and peripherals; full specs below)
- Extremely low-cost; ~$1 in moderate volumes)
- Open SDK that works with GCC
- Arduino IDE integration
We'll learn over the next few steps we'll learn how to set up our computers to be able to communicate with the WeMos D1 Mini board in order to program its onboard ESP8266.
WeMos D1 Mini vs. NodeMCU DevKit 1.0
Both the Wemos D1 Mini and the NodeMCU DevKit are development boards for the ESP8266 that allow us to program the onboard SoC with ease from a computer's USB port. Here are a few things to consider when making the choice for one vs. the other:
WeMos D1 Mini
- SoC: ESP8266 (ESP-12F Module)
- USB-to-Serial: WCH's CH340
- Cost: $7.50
- GPIO: 11 Digital, 1 Analog
- Size: 34.2mm × 25.6mm
- Voltage Reg.: RT9013 500mA LDO
- Power Input: (3.0~5.5VDC)
NodeMCU DevKit v1.0
- SoC: ESP8266 (ESP-12F Module)
- USB-to-Serial: Silicon Labs' CP2102
- Cost: $9.95
- GPIO: 16 Digital, 1 Analog
- Size: 49.0mm × 24.5mm
- Voltage Reg.: AMS1117 1A LDO
- Power Input: (4.0~15.0VDC)
The most important considerations to us are the size and number of GPIO, so those will be the deciding factors when choosing one over the other. Note that both boards can be powered using the Micro-USB connector or the available Vin pin (labeled 5V on the WeMos D1 Mini), but the power input on the NodeMCU DevKit boards can be significantly higher thanks to its 1117-based power regulator.
Typically, the NodeMCU DevKit boards ship with male pins pre-soldered, which makes it ready for use on a breadboard. Meanwhile, the WeMos D1 Mini boards ship with an assortment of header pins: male, female, and long-pin female for the users' convenience.
The latter of the three are used to stack the board on both the top and the bottom sides.
Soldering the Pin Headers
The WeMos D1 Mini development boards are shipped with 3 pairs of header pins: male, female, and long-pin female. Depending on the application, one of these options will be suitable.
Because in this tutorial we will not be connecting anything to the WeMos D1 Mini development board (other than the USB cable), we won't need to solder the pin headers just yet. We'll certainly do so in the upcoming tutorials, so remember to check them out if you're curious about this step.
Installing The USB Drivers
Before we can start writing code that runs on the ESP8266, we'll need to communicate with the Wemos D1 Mini Development Board using a computer's USB interface. In particular, we'll need to install and configure a Virtual COM Port (VCP) driver to allow sending/receiving data from the USB-to-Serial UART module on the board: WCH's CH340.
The CH340 is a popular chip used in many inexpensive development boards such as the Arduino-compatible Nano 3.0. As expected, the driver installation process will vary depending on your Operating System.
It used to be a painful task getting the CH340 chip recognized by OS X, not only was the driver unsigned but it needed some pre-installation commands entered using the Terminal. However, as of November of 2015, a new driver has been released and it works right out of the box: CH34x_Install_V1.3.zip.
More info on this driver is found on Björn's Blog!
Before installing the driver we need to access
System Preferences → Security & Privacy → General, and set the option for
Allow apps downloaded from: to
Mac App Store and identified developers so that the driver can run properly. Then, we can follow the instructions on the driver's README file to complete the installation (fixed the grammar a bit):
- Extract the contents of the zip file to a local installation directory
- Double-click CH34x_Install_V1.3.pkg
- Follow and complete the installation procedure
- Restart the computer after the installation finishes
Once the computer restarts, open the Terminal.App (use the Finder to Navigate to
Applications → Utilities → Terminal) and once it's open type the command:
This returns a list of peripherals currently connected to the computer. Typically, boards carrying the CH340 chip appear listed as
fa130 in the image below.
If we issue the command before connecting the board, there usually aren't any
usbmodem devices available.
Luckily for Linux users, the CH340 is recognized without the need for installing drivers! Similar to OS X we can open up a Terminal window, and issue the same command:
ls /dev/tty* | grep 'USB\|ACM'
On Linux, boards carrying USB to Serial adapters (e.g., CH340, CP2102, FT232R) are listed as either /dev/tty.ACM or /dev/tty.USB where is a number. Issuing the command once prior to connecting the USB is a quick way to narrow down which entry corresponds to the board.
Depending on your Windows version, download one of these files:
Once installed we should see the message:
Device driver software installed successfully.
You can manually verify that everything is in working order by following these steps:
- Open the
Device Manager(available through
Control Panel → System & Security → Device Managerin the
- Under the
Ports (COM & LPT)entry, there should be an open port named
USB-SERIAL CH340 (COM )where
Now that we're ready to communicate with our ESP8266 via the CH340, we can explore how to load our code onto it.
Loading Code With The Arduino IDE
For those of us who want to use the ESP8266 as a regular microcontroller such as the ATmega328 in the Arduino UNO, then it's possible to write custom firmware and load it on the chip. As is typical in programming microcontrollers, the custom firmware will replace anything previously stored in the chip's flash memory.
Although we can use the manufacturer's SDK to develop our custom firmware, it is much easier to use the good ol' Arduino IDE.
If you don't have the Arduino IDE installed, please look at our detailed tutorial on how to get it on your system.
In the Arduino IDE open the Preferences window and enter the URL below into the Additional Boards Manager URLs field, and select OK.
Select the menu option
Tools → Board → Boards Manager... and scroll down and to locate the option esp8266 by ESP8266 Community which should be the last item on the list, and click
After restarting the Arduino IDE we can now select the board we're using from the menu option
Tools → Board → NodeMCU 1.0 (ESP-12E Module). Then, we specify the correct CPU Frequency (
Tools → CPU Frequency: "" → 80MHz) and Upload Speed (
Tools → Upload Speed: "" → 115200). Finally, the last step is to select the correct option for the Port (
Tools → Port → /dev/cu.SLAB_USBtoUART).
At this point we can write our own firmware and upload it. To get started we can try one of the examples
File → Examples → ESP8266WiFi → WiFiScan. After uploading it, we can open the Serial Monitor window and observe the results. Note that we need to match the baud rate, so check that 115200 is selected from the drop down menu!
Other Firmware Options
Keep in mind that only one firmware option can be running on the ESP8266 onboard your WeMos D1 Mini at a time. For instance, if you have the the factory firmware (AT+Commands interpreter) and upload the Blink program from the Arduino IDE, you'll need to re-flash the AT+Commands firmware to be able to use it once again. The process is painless, so we encourage you to try all options available.
Visit our other tutorials to get started with all the different projects for the WeMos D1 Mini and its family of shields!