- Sun Mar 27, 2016 8:04 am
#44126
Hello community,
I recently got my first NodeMCU-ESP8266. I like the idea and the fast workflow.
However, I did not get it running.
At the backside of the module is written:
So I downloaded that driver and connected the module by USB - I used my original samsung USB cable (from my smartphone).
After that I downloaded the ESP8266Flasher to upload a NodeMCU firmware. I tried the flasher-built-in firmware, and later I used the master-version and even the dev-version from http://nodemcu-build.com/
The flasher seems to work properly:
1. The blue LED is flashing while the firmware is transmitted.
2. Changing the baud rate changes the led flashing speed.
3. After the firmware transmit is finished, the module is not communicating some seconds, I think it's rebooting.
But, of course, I do not know, if it's flashing properly.
After that step, I tried to save some init.lua to the module.
At first I used ESPlorer in three versions:
1. Self-compiled from the GitHub repository,
2. Pre-compiled stable version,
3. Pre-compiled dev version.
None of these versions were able to transfer a file or to do something else. I never read that much error messages
The MCU connection succeeded and then these messages followed:
I even tried the dumb mode - but it didn't work.
Only errors - so I tried another tool: LuaLoader.
It has similar problems: After the connection establishes, the tool can not understand the answer from the MCU, so it thinks the baud rate is not correct. Meanwhile I did try all of them. (From 110 to 921600)
Finally I tried putty. But it has the same problem: Only non readable garbish - no matter what baud rate I use.
I even tried a USB 3 port at the PC and later a USB 2 port.
Now someone could think, I chose the wrong COM port (I used COM13).
This hints proves its correctness:
- After resetting, putty/LuaLoader shows always the same (non readable) chars.
- When disconnecting the module, this COM ports disappears.
- The COM port appeared the first time after installing the driver and connecting the module.
Some questions:
- I often read, that the flash process must be enabled by connecting some pins. I did not connect anything - perhaps this is the problem?
- The circuit got some free place for another button with the text "flash" - what is that? Why is it free? (It has exactly the same layout/size as the reset button.)
- What is the problem here? Why can't I transfer a file?
I will attach some photos to show my setup.
I recently got my first NodeMCU-ESP8266. I like the idea and the fast workflow.
However, I did not get it running.
At the backside of the module is written:
1. Install CP2102 driver
2. Use 9600 baud rate
3. Connect Wi-Fi and enjoy
So I downloaded that driver and connected the module by USB - I used my original samsung USB cable (from my smartphone).
After that I downloaded the ESP8266Flasher to upload a NodeMCU firmware. I tried the flasher-built-in firmware, and later I used the master-version and even the dev-version from http://nodemcu-build.com/
The flasher seems to work properly:
1. The blue LED is flashing while the firmware is transmitted.
2. Changing the baud rate changes the led flashing speed.
3. After the firmware transmit is finished, the module is not communicating some seconds, I think it's rebooting.
But, of course, I do not know, if it's flashing properly.
After that step, I tried to save some init.lua to the module.
At first I used ESPlorer in three versions:
1. Self-compiled from the GitHub repository,
2. Pre-compiled stable version,
3. Pre-compiled dev version.
None of these versions were able to transfer a file or to do something else. I never read that much error messages
The MCU connection succeeded and then these messages followed:
Not able to detect firmware(after the connection has been established)
Communication failure(after I tried to transfer some file)
I even tried the dumb mode - but it didn't work.
Only errors - so I tried another tool: LuaLoader.
It has similar problems: After the connection establishes, the tool can not understand the answer from the MCU, so it thinks the baud rate is not correct. Meanwhile I did try all of them. (From 110 to 921600)
Finally I tried putty. But it has the same problem: Only non readable garbish - no matter what baud rate I use.
I even tried a USB 3 port at the PC and later a USB 2 port.
Now someone could think, I chose the wrong COM port (I used COM13).
This hints proves its correctness:
- After resetting, putty/LuaLoader shows always the same (non readable) chars.
- When disconnecting the module, this COM ports disappears.
- The COM port appeared the first time after installing the driver and connecting the module.
Some questions:
- I often read, that the flash process must be enabled by connecting some pins. I did not connect anything - perhaps this is the problem?
- The circuit got some free place for another button with the text "flash" - what is that? Why is it free? (It has exactly the same layout/size as the reset button.)
- What is the problem here? Why can't I transfer a file?
I will attach some photos to show my setup.
