ESP8266 NodeMCU issue
Posted: Thu Jul 05, 2018 2:51 amHi,
I'm new to the ESP8266 (I'm using a NodeMCU version for now) and I'd like to dig in.
I downloaded the appropriate drivers and the ESPlorer tool.
From the ESPlorer, I can see the proper communication port, I can open the connection and then the tool says it's communicating with the MCU, but the "Open" light never becomes green. It sticks at Red and a blue LED is flashing on the ESP8266 NodeMCU. See following screenshot:
I also have a video of the Blue LED Flashing and a Slow Motion Video of the LED's flashing when powering up the ESP8266 but my video-file-format cannot be uploaded (which one can I use?).
When powering on the ESP8266 NodeMCU, first a small led flashes once on (what I think is) the ESP8266 itself, then a bigger LED starts flashing on the board (that probably makes it the NodeMCU version of it).
I've read about updating the Firmware but to be honest I'm a little reluctant to do so before I've proved the communication to be in good shape.
Anyone any thoughts on how to resolve this?
Regards,
Rob.
btw: I'm using a MacBook running MacOS High Sierra 10.13.5.
I'm new to the ESP8266 (I'm using a NodeMCU version for now) and I'd like to dig in.
I downloaded the appropriate drivers and the ESPlorer tool.
From the ESPlorer, I can see the proper communication port, I can open the connection and then the tool says it's communicating with the MCU, but the "Open" light never becomes green. It sticks at Red and a blue LED is flashing on the ESP8266 NodeMCU. See following screenshot:
I also have a video of the Blue LED Flashing and a Slow Motion Video of the LED's flashing when powering up the ESP8266 but my video-file-format cannot be uploaded (which one can I use?).
When powering on the ESP8266 NodeMCU, first a small led flashes once on (what I think is) the ESP8266 itself, then a bigger LED starts flashing on the board (that probably makes it the NodeMCU version of it).
I've read about updating the Firmware but to be honest I'm a little reluctant to do so before I've proved the communication to be in good shape.
Anyone any thoughts on how to resolve this?
Regards,
Rob.
btw: I'm using a MacBook running MacOS High Sierra 10.13.5.