-->
Page 1 of 1

Two NodeMCU implementations - one works the other doesn't.

PostPosted: Sat Feb 07, 2015 6:08 pm
by HAAGDEN
I have two boards, one a standard NodeMCU and the other a board bought on eBay that had, I suspect IOT,) firmware that I have replaced with NodeMCU firmware using the LuaLoader v.1.0.0.2. I got the MAC and STA addresses during this process. I believe the burn was successful as I used the same procedure to reburn the NodeMCU board. The NodeMCU has an onboard CH340G. For the other board I have tried both an FT232RC and a Prolifics CP2102 but both give garble in response to a Restart command. The set up can hopefully be seen in the images although not sure the links will work

I suspect a Baud Rate problem however I can't understand why with the same firmware the two boards respond differently. I have tried various Baud Rates however I can't try 76800 as I don't understand the AN by FTDI on how to use 'aliasing' to get non standard rates.

Any ideas?

https://www.dropbox.com/s/xesb5f93fk7h2 ... 4.jpg?dl=0
https://www.dropbox.com/s/7abp54mjxy61t ... 3.jpg?dl=0

Update: I have managed to resolve most of the issues:-
1). Removed the jumper (after burning the NodeMCU firmware) as this holds GPIO0 at GND and hence in the burn mode.
2). Fitted a 10K pull up resistor from GPIO0 to 3.3V.
4). I made a slight amendment to my Power Wiring to improve the GND return to the USB - TTL Converter

With these changes and a 9600 baud rate I got the normal response and was able to upload init.lua and list the uploaded files using the LuaUploader v1.0.2.2 from Harry Wiguna. These is also an excellent review of this board at the following link :-

http://blog.squix.ch/2015/01/esp8266-te ... eview.html

Now this board and the second Board, a standard NodeMCU, return local IP addresses after up-lloading running an init.lua

Now to write some more Apps.