nodemcu / nodemcu-devkit Goto Github PK

I am wondering, How is this picture useful to a developer?
https://github.com/nodemcu/nodemcu-devkit/blob/master/Documents/NodeMCU_DEVKIT_V0.9.png

I am working with arduino IDE.

Here is my problem : if I set one of the pin (pin 0) in INPUT_PULLUP mode, then the pin isn't actived by connecting it to 3.3v, but by connecting it to ground..... This is strange !

Any idea why ?

I uploaded the exe on virustotal and it was flagged as malicious. So, are they false positives or correct?

https://www.virustotal.com/gui/file/7e2665e90b09b6d4c72c5df7e09433178a0f4042b1313b3c40a876cbd12a247a?nocache=1

How can I flash firmware on the devkit from a Mac OS X? I succesfully installed the driver from here http://raysfiles.com/drivers/ch341ser_mac.zip and can talk with the ESPlorer to the AT firmware. But for some strange reason flashing does't work.
To do this I press the flash button while powering up and run the esptool.py as I do when I flash any other ESP8266...
Might this be an issue with the CH340G serial-to-usb converter?

https://github.com/SkyRocknRoll/CH341SER_LINUX

clone and follow the instructions mentioned there

What is the exact specification or part no of the onboard led used with this module and exactly at the minimum how much voltage the schematic diagram is expecting?

Are the following specification fits good?

If - Forward Current: @5 mA
Vf - Forward Voltage: |@2.85 V

The NodeMcu I am using for my project seems to have a certain problem in the resetting circuit. While programming through Arduino IDE it doesn't detect the MCU port connected until the reset switch is continuously pressed.
The driver is installed but the port isn't detected by either Arduino ide or system device manager. It is only detected when I continuously keep the reset switch pressed.
Is there anything I can do to remove this error or is there any alternate method.
The board is new and had been used just to install the driver.

How can I flash firmware on the devkit from Windows 10? Do i need to install any drivers? The board seems to be recognized (I'm trying to use the NodeMcu Flasher and it recognizes the device on the COM5 port). After hitting the Flash (F) button a blue led blink on the board, but the progress bar stays at 0%.

My board version is v1.0 (i guess, i bought it from china seller...)
Do i need to put the A0 to GND? or push the reset button?
Can someone describe me the whole procedure?

For some strange reason flashing does't work.

Hi!
Does someone have the driver for newer Linux Kernels? Thanks!

CH340G is 5V powered and thus pushing 5V level (through R12 ~4.3V) into ESP12 on RXD0 instead of 3.3V level.

hello people.
I did an extremely stupid thing i connected my nodemcu directly to a 2amp,5V charger and it continued working fine...but then after a while of usage... it started overheating and the code already in it, continues to work however it is not even recognised by my laptop after the incident.FYI: the square IC which i think is the micro controller gets heated up first and then the entire board heats up!
even after learning the hard way...of ways in which not power the micro controller, i manged to do something similar to my friend's as well...but in his case the previous code doesn't work and only the WiFi module alone heats up. I might have by mistake connected the ground (-ve being used as the reference) of a 12V battery to the adjacent pin : sclk. I dont understand how this might have caused the nodemcu to not work.
thanking you guys for your support!

Running Mac OSX 10.10.5 on an early 2011 Macbook Pro

I have the version 5 dev kit (the one with the CP2102), and the most current VCP CP2102 driver for my system. I even have a CP2102 breakout that I use to communicate with an ESP-01 (it works perfectly).

I bought the dev kit off amazon from DIY Mall.

When I plug in the dev kit the led on the ESP-12 module blinks, but I get nothing, absolutely nothing, under /dev/tty.*

Even if I use IORegistryExplorer, I see nothing.

What could be going wrong? Bad module?

I'm having troubles to flash or connect my devkit v1. It arrived my home 2 days ago and I was not able to flash it or at least communicate with it.

I'm going to describe my case. I connect my devkit v1 via USB to microUSB with the CP2102 USBtoUARP, then the blue led of the ESP8266 blinks twice and stop. After this I can see the SSID "AI_THINKER_DA7E19" and connect to it, I got a 192.168.4.2 and the device .1. It answers to the ping but there is not webserver. Now I try to flash it, first I tried with Linux and ESPTool,

# python2 esptool.py --port /dev/ttyUSB0 write_flash 0x00000 firmware.bin
Connecting...

A fatal error occurred: Failed to connect to ESP8266

Well I read somewhere it could be a bug with ESPtool with high values of baudrate, so I tried with --baud 9600 but the same output also with different baudrates. Meanwhile the program is in the state connecting..., the blue led blinks. I tried to reset with the Flash button pressed and the same result, nothing change. Also I tried wiring the GPIO0 to GND but still the same error.

Now it is the turn for Windows, I tried with the nodemcu-flasher, the driver was correctly install and the port is assigned correctly too. Select the COM port and set the baudrate to 9600 and flash. The log says Begin to find ESP8266 enters in a loop and the blue led blinks every 1/2 seconds. Just to point it out, in the tab operation not appears any mac, it says "Waiting...". Just like before I changed the Baudrate and I tried all of them but nothing happens. (I also press flash and reset like before but nothing)

After all this troubles I tried to communicate with the devkit via Serial port with putty and Screen. The connection seems to be established but nothing appears in it. Pressing RST it should write something... garbage or some characters but nothing.

I don't know if I'm doing something wrong or the devkit it's broken. Some solution or tip?

Thank you

https://stackoverflow.com/questions/30017344/moxa-realtty-module-compilation-error-on-linux-kernel-3-16

So could any update the ch341x.c to make driver usable for ubuntu 17.04
thank you very muchk

Do not have the most opportunities to do so.
Did not I buy devkit?

I really would like to buy and use NodeMCU, but one problem I have with it is its use of CH340G for USB to serial. It's not so much the part, but the lack of signed drivers for OS X. I understand that there are unsigned drivers for it, but it's unreasonable to ask OS X users to turn off checks.

Option 1: Is it possible to make signed drivers available?

Option 2: Use a different chip for USB to serial. Apple provides drivers for Prolific the prolific chipset built in with the OS X. This would be best since clients wouldn't even need to install drivers.

I am trying to install the mac drivers on an m1 macbook air. It gives me an error saying its incompatible with mac version