Skip to content

EN Installing firmware

Dirk Mueller edited this page Jan 8, 2020 · 13 revisions

Language: DE

Previous page Next page
Components supply Assembly of components

Installing USB2Serial driver

The operating system of the computer which will upload the sensor software or "firmware" to the NodeMCU - also called to flash - will need a driver to communicate with it. The computer will interact with the USB2Serial chip on the NodeMCU. This will also depend on the version of the NodeMCU. Linux natively provides drivers already.

Identify NodeMCU version

If the version of the NodeMCU is unknown, a description of either CP2102 or CH340G can be found on the back. Alternatively one of the chips are marked,in which case you will most likely need a magnifying glass.

CP2102 (NodeMCU v2)

CP210x USB TO UART Bridge Drivers

CH340G (NodeMCU v3)

CH340G Bridge Drivers

Restart the computer after installing the drivers. Comment MacOS >10.9: Unsigned drivers have to be explicitly allowed. A good description can be found here.

Install firmware

Caution: Do not use USB cables longer then 1m for uploading the firmware to NodeMCU.

We will be describing two variants of installing the sensor software. VARIANT 1 includes compilation of the source code, whereas with VARIANT 2 you use the esptool of the Arduino IDE to upload binaries. VARIANT 2 is recommended as fast path or for beginners. For both variants you'll need the follow these instructions:

  1. Download and install Arduino IDE.
  2. Install platform packages for ESP8266 with Boards Manager following these instructions.
  3. Close Arduino IDE.

Identifying the USB port

In order to upload the firmware you will need to supply information of the USB port the operating system is supposed to use. You can do this by connecting the NodeMCU to the port you want use later on and then start the Arduino IDE. At ToolsPort the available ports will be listed and the NodeMCU should be easy to find. To confirm this is actually the right port: Select the port and select ToolsGet Board Info. In the status bar, under VID and PID you should now see codes. Close the IDE now to free up the ports.

  • MAC: CP2102 on /dev/cu.SLAB_USBTOUART and CH340G on /dev/cu.wchusbserialXXXXXXXX.
  • Windows: COM3. If its not that port, just try the next ones in the list of available ports.
  • Linux: /dev/ttyUSB0 or similar

VARIANT 1 Arduino IDE

Here we show how to compile the firmware yourself and upload it to the NodeMCU.

  1. Start Arduino IDE (after previously installing platform packages and closing it).
  2. Install the libraries mentioned in Contributing.md.
  3. In the IDE at ToolsBoard select
    • NodeMCU 0.9 (ESP-12 Module) for NodeMCU v1
    • NodeMCU 1.0 (ESP-12E Module) for NodeMCU v2 und v3
  4. Now connect NodeMCU via USB and select the port at ToolsPort.
  5. Copy the source code to your computer. Best and most convenient method is to clone the repository or download the repository as archive and unpack it. Alternatively all files from the source code directory can be manually copied as well. If you do choose the latter, the RAW button might help.
  6. Open the sketch (INO) file in Arduino IDE.
  7. Change the ext_def.h to meet your requirements (WLAN configuration, sensors, ...)
  8. Now flash the NodeMCU with SketchUpload or the upload button (right arrow).

    Bildschirmaufnahme der Arduino-IDE beim Flashen der Firmware

VARIANT 2 Command line

In this variant we will use the command line tool esptool, which came with the Arduino IDE installation.

  1. Download the compiled firmware in English or another language
  2. Open a command prompt or terminal in your operating system.
  3. Paths below may differ due a different version number - also the location of the esptool might have changed with your installation:
    • Windows: "%USERPROFILE%\AppData\Local\Arduino15\packages\esp8266\tools\esptool\0.4.13\esptool.exe" -vv -cd nodemcu -cb 57600 -ca 0x00000 -cp COM11 -cf "_PATH-TO-DOWNLOADED-FIRMWARE-FILE_"
      • Change the port after-cp to yours
      • Use quotation marks as documented
    • Linux/MacOS: $PATH-TO-ESPTOOL -vv -cd nodemcu -cb 57600 -ca 0x00000 -cp $USBPORT -cf $BINARY
      • $PATH-TO-ESPTOOL mit look something like ~/Library/Arduino15/packages/esp8266/tools/esptool/0.4.13/esptool or ~/.arduino15/packages/esp8266/tools/esptool/0.4.13/esptool
      • $USBPORT might look like something like this /dev/cu.wchusbserial1410 or /dev/ttyUSB0
      • $BINARY is the path to the binary, eg. latest_en.bin or sensors-software/airrohr-firmware/airrohr-firmware.ino.nodemcu.bin

Description of parameters:

-vv           show additional information while flashing (useful for troubleshooting)  
-cd nodemcu   which reset method should be used
-cb 57600     baud rate for flashing
-ca 0x00000   start address in flash memory
-cp <pfad>    path to the port the NodeMCU is connected to
-cf <pfad>    path to downloaded firmware file

Deleting the configuration

First way: using ESP8266fs Plugin

You can delete the config with Arduino IDE and the ESP8266fs Plugin.

  • First you need to install the plugin. Follow the instruction on the plugin page.
  • Once the installation done, re-open Arduino IDE and be sure to have an empty sketch. Click on Tools>ESP8266 Sketch Data Upload. You'll have to confirm that you want to upload an empty SPIFFS image. The upload process (3 MB) might take a while. You are done when the output displays "Hard resetting via RTS pin...".

Second way: via esptool

  • Download this image file
  • Download ESP8266 Download Tool
  • Unzip the ESP8266 Download Tool and click on flash_download_tools_vX.X.X.exe
  • Select ESP8266 DownloadTool
  • Choose the path to the bin, add 0x100000 after @, set the right COM and click start image

For Linux

For Linux, yet untested with MacOs, there's a script to delete the config here.

Testing sensor activity

In Arduino IDE activate ToolsSerial Monitor to review debug information via USB. The output can be read at a baud rate of 9600. Errors such as WLAN login failures or unsuccessful upload of data can be monitored here.

Seiten

Dokumentation

Protokolle

for more, see Protokolle

Clone this wiki locally