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

PD: I posted it in the old devkit repository, now it is in the correct repository.

EDIT:
@mrmonteith answered in the other repository.

I'm trying to remember when I first tried this. I think I used the flasher tool. You start the attempt at transfer, hold down the reset and flasher button, release the flasher button and then about a half second or so after release the reset. I don't have my device in front of me to check. Of course I only had to do it one time and I've had mine for about month. Hope it helps anyway. 

I tried too, but no works it.

Hello, I've a relay board with 3 pins, VCC, GND and IN. I've connected VCC to 3.3 and GND to GND of MCU. In is connected to a GPIO pin. With pinMode(pin, OUTPUT); and digitalWrite(RELAY1,LOW); and digitalWrite(RELAY1,LOW); relay doesn't work. I've tested that if I connect relay IN pin to VCC it doesn't work but if I connect it to GND it work. This relay hasn't jumper to set if it should work in HIGHT or LOW. I suppose that MCU GPIO should provide a GND signal to turn on relay but I don't know how.
Can you help me ?

I have OS X Yosemite. SiLabs drivers for the USB-Serial adapter are installed and working. I can communicate to the board via /dev/cu.SLAB_USBtoUART and I can use it in screen, ESPlorer, esptool.py... but strangely not minicom.

However, I haven't been able to flash new firmware successfully.

Can anyone confirm this can be done? I did it on older ESP01 hardware before but I don't rule out me doing something stupid.

• What tool did you use to flash?
• What firmware image?

I posted additional information here: http://www.esp8266.com/viewtopic.php?f=22&t=3903 but nobody has been able to help. Help is appreciated!

Adobe Acrobat X Pro is unable to read file NODEMCU_DEVKIT_V1.0.PDF. Acrobat says, "Acrobat could not open 'NODEMCU_DEVKIT_V1.0.PDF' because it is either not a supported file type or because the file has been damaged."

Hi, I am measuring the current consumed by a NodeMCU, connect a resistance of 1 ohm in series with the power supply and there are peaks of 200mV every 100ms that these peaks are due.

Hi, I have been using the nodemcu V3 for a week before the reset switch failed. It seems the nodemcu only works if the reset switch is kept pressed otherwise not. What might be the possible error? Also is there any way it can be rectified?

As per https://tinker.yeoman.com.au/2016/05/29/running-nodemcu-on-a-battery-esp8266-low-power-consumption-revisited/

It would be great it the usart used its own internal 3.3V regulator
https://yeomanblog.files.wordpress.com/2016/05/option2schematic.jpg
Plus a TX pull down resistor.
This is so it doesn't consume power while not in use.

It would be great if there was a jumper to disable the AMS1117 so that an external battery + MCP1700 + 1000uf Electrolytic could be used instead (for burst transmission of sensor data).

Please link good USB-->UART driver for windows

Hello,
Since I'm not able to send you an email, I'll try contacting you this way.
I'm interested in software/template you used to generate the following pinout image:

I'm currently working on a LoRaWAN node device which will have quite a bit of headers so I'm interested in creating a similar pinout graphic.

Best regards,
Leon

Hello,

I have been trying to find the NodeMcu V3 schematic through the web but with no luck. Does anybody has it?

Regards,
Pascal.

Hello, I am trying to connect and program a L18 proximity sensor for metals but the Nodemcu is not reading it, I connected it to D7, but tried all the Ds and even changed to work via analog and digital and nothing, stays are 0, which is non metal detected. I need help thanks!

I have bought a esp8266 nodemcu board, yet it is burned and smoked out when i connect 16v to Vin pin and GND to GND ? Diodes are burned as it is shown in the figure ?

I could not understand why ? Because diodes and AMS1117 has maximum power input rating as much as 18V ?

I am trying to flash a program into Amica NodeMCU ESP8266. I have tried in Window 10 and OSX.
I have tried

1. plain esptool.py command line in OSX 10.13.4 High Sierra

• esptool.py --port /dev/tty.SLAB_USBtoUART --baud 115200 --before "default_reset" --after "hard_reset" write_flash --flash_mode "dio" --flash_freq "80m" --flash_size 4MB 0x1000 /Users/soumensardar/Downloads/sketch_jul13a.ino.bin
• esptool.py --port /dev/tty.SLAB_USBtoUART write_flash 0x1000 /Users/soumensardar/Downloads/sketch_jul13a.ino.bin
  By holding down the FLASH button when plugin the USB to mac and/not clicking RST, I have issued the commands in terminal.
  Output:

esptool.py v2.4.1
Serial port /dev/tty.SLAB_USBtoUART
Connecting........_
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
MAC: b4:e6:2d:34:a7:ff
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Compressed 250496 bytes to 182688...

A fatal error occurred: Timed out waiting for packet content

2. Arduino 1.8.5 in OSX 10.13.4 High Sierra

By holding down the FLASH button when plugin the USB to mac and/not clicking RST, I have issued the commands in terminal.
And simple upload
Got this

esptool v0.4.13 - (c) 2014 Ch. Klippel <[email protected]>
	setting board to nodemcu
	setting baudrate from 115200 to 921600
	setting port from /dev/tty.usbserial to /dev/cu.SLAB_USBtoUART
	setting address from 0x00000000 to 0x00000000
An error occurred while uploading the sketch
	espcomm_upload_file
	espcomm_upload_mem
opening port /dev/cu.SLAB_USBtoUART at 921600
	tcgetattr
warning: serialport_set_baudrate: baud rate 921600 may not work
	tcsetattr
	serial open
opening bootloader
resetting board
trying to connect
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
trying to connect
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	espcomm_send_command: receiving 2 bytes of data
	espcomm_send_command: receiving 2 bytes of data
	espcomm_send_command: receiving 2 bytes of data
	espcomm_send_command: receiving 2 bytes of data
	espcomm_send_command: receiving 2 bytes of data
	espcomm_send_command: receiving 2 bytes of data
	espcomm_send_command: receiving 2 bytes of data
	espcomm_send_command: receiving 2 bytes of data
Uploading 250496 bytes from /var/folders/dm/ck803jcd62bbn2hn8m5d6lch0000gn/T/arduino_build_732599/sketch_jul13a.ino.bin to flash at 0x00000000
	erasing flash
	size: 03d280 address: 000000
	first_sector_index: 0
	total_sector_count: 62
	head_sector_count: 16
	adjusted_sector_count: 46
	erase_size: 02e000
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	setting timeout 15000
	setting timeout 1000
warning: espcomm_send_command: didn't receive command response
warning: espcomm_send_command(FLASH_DOWNLOAD_BEGIN) failed
closing bootloader
error: espcomm_upload_mem failed

3. NodeMCU PyFlasher on OSX 10.13.4 High Sierra
   Console

Connecting........_
Detecting chip type... ESP8266
Chip is ESP8266EX
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Flash params set to 0x0240
Compressed 250496 bytes to 182688...

and it keeps on waiting here

4. NodeMCU Flasher Windows 10
   I do not have the exact error right now. But the lower left corner got red and the log says kind of timeout

I am using 1 meter USB cable provided by my smartphone manufacturer.
I have installed the CP2102 driver

Is there any problem with my NodeMCU module or I am missing any point?

Wow. this was a mission.
I'm on a Mac Sierra 10.12 with an ESP8266.

First, Arduino kept crashing.
Crash errors: nsinvalidargumentexception and setAutomaticCustomizeTouchBarMenuItemEnabled

It took probably 10 tries of installing different versions but Arduino keeps crashing
SOLUTION:
https://www.arduino.cc/download_handler.php?f=/arduino-1.8.7-macosx.zip

THEN I tried what felt like every SI Silicon Labs driver under the sun including the one that came with the manual to my ESP8266. DIDN't WORK. Tried quitting, restarting, updating java, different MicroUSB cables and followed this thread as well: #2

FINALLY here's the solution I found. The SI (cu.SLAB_USBtoUART) driver doesn't work, this one WORKS. Load it up.

SOLUTION:
http://blog.sengotta.net/wp-content/uploads/2015/11/CH341SER_MAC-1.4.zip

Hello gentleman,
I would like to use Nodemcu Lolin V3 as a part in my PCB layout. But I can't find any library for Eagle. Is there any existing one? Or does anybody plan to create one?
Thanks.

Hello!
I have my first ESP8266 module (NodeMCU 1.0) and I was able to make a HTML server on AP and STA mode.
So the next level was keep the server in STA mode working as much as possible on my home network so whenever I need the data acquired by a temperature and humidity sensor (I2C) I could connect by any device and get it on the browser.
It works great, but then I noticed that after a while the server did not answer my requests, ene the ping did not have answer from the ESP. As soon as I reset the board I get the webpage right away.
At this point I have not any clue about what happens but then I wondering if the ESP or WI-FI module was on a kind of “sleep mode”.
The loop works fine since I included a routine that shows the parameters (temperature and humidity) whenever I push the “flash” button on an Oled display. It works perfect so included a routine to reconnect the module to my network.
So I left the board connected to a 5V phone charger (1amp) overnight and after 30 minutes all works fine but on the middle of the night I try to retrieves the data and again the HTML server was not available. I push the button and the browser shows me the data.
The router is stable, the IP of the ESP does not matter if is assigned by the router or I set it out manually.
I guess something is going to sleep without I instructed to do so.
Anybody has experienced the same issue?
I have googled it and I found some very old forum but with no conclusion. They made a workaround with “thiker” function.
Please tour comments, ideas and if someone found the reason and have a solution....even better!!!

what are the limits of the voltage A0? Usual esp-12x up to 1v, you use a resistive divider at the input.
can i measure li-ion battery voltage?

Hi,

I have managed to burn 4 ESP8266 on a dev. board (https://github.com/nodemcu/nodemcu-devkit-v1.0), and the reason is still unknown for me.

The history is like this:
After I have burned the:
– 1st one I removed GPIO10 from my code an also let if floating,
– 2nd I have reduced the current for driving MOC3041 from 15 to 7.6mA,
– 3rd I removed the ADC In setting (analogRead) from my code, even if I don
t use it for anything, yet.

Now I have the following circuit:
220V AC -> Power transformer from 220 to 6V (AC) -> Rectifier bridge (Vout ~8.6V DC) -> 2 capacitors (470uF + 100nF) -> LM7805 -> Power the ESPshield to Pin 15 (+) and Pin 7 (-) -> use Pin8/GPIO14 as an output to power an opto-triac MOC3041 (current was limited to 7.6mA using a 270ohm resistor) ->a triac to drive a load of 21W (7 x AC LED lamp) -> Pin1/GPIO16 used as an input (if pin state is changed than also the output is changed).

After running the application ~15 minutes (Playing on/off via web requests) I have played also a little bit with the input pin and everything worked as expected. Then I have decided to let lamps ON (input pin was pulled to GND - Red led from shield lit), but after ~5 -10 minute the lamps turned off (Red led from shield remained on) and now the 4th ESP is dead.

I have checked the value of current limiting resistor for the Red Led (470 ohm, value was obtained after I have removed the resistor from the shield) and from my calculations the current ~3.2mA is small enough not to damage the ESP, and now I have no idea what I
m doing wrong.
If you think that is relevant I can provide also the code (written using Arduino IDE)

Have anyone an idea that can help me with this issue?

Hi.
I am beginner in using proteus
Can you on how to upload code for nodemcu in proteus.
I have created the source code and the simulation. now I want to simulate it. but I don't know how I can upload the compiled code from Arduino IDE. I need your help

Hello!

Let me get this straight. I bought the following board:
http://www.aliexpress.com/item/Free-shipping-NodeMCU-development-board-for-ESP-12E-from-ESP8266-esp-12E-Lua-IoT-programable-wifi/32583355412.html

I use the Arduino IDE, and everything works pretty much fine. I only have one problem:
If i test it for the blink sketch it reads HIGH as LOW and LOW as HIGH.

Example:
[code]
void setup() {
// initialize digital pin 16 as an output.
pinMode(16, OUTPUT);
}

// the loop function runs over and over again forever
void loop() {
digitalWrite(16, HIGH); // turn the LED on (HIGH is the voltage level)
delay(1000); // wait for a second
digitalWrite(16, LOW); // turn the LED off by making the voltage LOW
delay(100); // wait for 1/10 second
}
[/code]

This should do (as far as i know) that the LED is on for 1 second and then have a short pause of 1/10 second.
But what the board is really making is the opposite. The LED is off for 1 second following a short blink 1/10 second and so on...
Am I insane or is this plain inverted?

I'm on a mac with Arduino IDE 1.6.8
I use the following bridge drivers:
https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Thank you for answers!

Schematics say about v 0,9 .. but many type at now .. v1 v2 v3 ... therefore ? thx

I want to use the Vin pin to power NodeMCU, but it's not clear which is the maximum value we can use.

In the rear of the PCB it's written "Vin +5v recommended, +10V MAX".

But in this pdf, in the "POWER" section is written:
"Max Supply Voltage: 20V"

Guys, can you help me. I've just got my NODEMCU ESP-12e with CP2102 (1.0), I'm using a MAC AIR, but the device doesn't appear on the PORT list, as some of the guys above. I'be tried different cables as well a USB interface that allows me to input an extra 5V DC PSU to feed the NODEMCU, no response at all. The Blink sketch compiles OK, the board is correctly set for NODEMCU 1.0 (ESP-12e Module), but no way to make it works. I heard that I should download a driver for CP2102, is it right? If so, where can I find it? Any help? Thanks!

Hi, I recently purchased a nodeMCU dev kit off of amazon.

I'm running Mac 10.10, and I have the most recent CP2102 driver. I own a couple of CP2102 breakouts that I can connect to no problem.

I am entirely unable to get any kind of response out of the dev kit using the micro USB port. Nothing shows up under /dev/tty.* and IO Registry Explorer is unable to locate the device in the USB port. I've tried to circumvent the CP2102 chip on the dev kit using one of my breakouts (connecting txd and rxd) and I seem to be able to connect to the module. I was having trouble communicating with the firmware (it was acting a little erratic) so I decided to reflash the AT firmware then the nodeMCU firmware. After reflashing I am unable to get any kind of response out of the chip over serial (through either AT or nodeMCU).

Is there anything I can do or is the module simply defective?

usb header breakout support, D+ D- inputs for usb etc. even if they were 2mm pitch holes or pads.

I would love to see PTC protection, or at least a footprint for it, instead of just the schottky ( which will magic smoke on direct short real quick btw ) 😄

Hi everyone,

I am using NodeMCU Amica. It has UART communication with GPS sensor, pin D5(Rx) is connected the GPS_TX and getting data with SoftwareSerial library. The problem coming is, If I connect the power to NodeMCU when the UART pin is connected, the data does not comes. But if the UART pin is connected after connecting the power to NodeMCU, the data comes. This problem is not at the other pins of NodeMCU (Eg. D2). Are there some specifications related to D5 pin?

The pin-name of D5 is MTMS as given in NodeMCU ESP8266 datasheet.

I checked the schematic "NODEMCU_DEVKIT_V1.0.PDF" in this GitHub page and found MTMS written in red (please see the attached picture) but unable to understand what it means.

If anyone knows about the above problem please help.

I`m not sure this is Issue worthy so lease delete when not:

I'm trying to power the waterproof version of the DS18b20 Temperatur Sensor via the D1 (GPIO05) Pin.

I tested the setup first by using the 3.3 Volt Out Pin and by connecting a 4.7 Resistor between VCC and the Data Pin (GPIO04) and everything worked.

Now when I'm trying the same setup but with the D1 (GPIO05) Pin instead of the 3.3 V I only get the 85 °C Error reading as if it's not properly wired.

GPI05 puts out 3.3 V when set high so that should work. I also tried the setup with different sensors like the HR-SR04 Ultrasound and the DHT-22. They all work fine.

I program it with blynk examples using audrino IDE to perform with blynk app
at first it work fine by powering with usb
Then I try to power it from Vin pin and GND with 9v battery after that it's no longer working and not even wiith usb.The Led on the board blinking all the time :@
I can't buy a new one :'(

I the pin image you labeled VIN 5V. This does not work by default. Is there a way to activate it?

A group of friends and I made a backpack for 1.0v NodeMcu hope you like it, we welcome your comments

https://www.tindie.com/products/sabas1080/nodemcu-v10-esp8266-lipolyliion-backpack-rev-a/

Discount code: BBF6B2F

Thanks

This is a non-technical issue, but may be an issue that others are encountering.

Our company, located in Canada, would like to make volume purchases of "official" (i.e. Amica) NodeMCU V2 modules. However, we have been unable to locate a Canadian, or even US-based, wholesaler.

Can anyone provide contact information for a North American wholesaler of "real" Amica modules? (we don't want to purchase "knock-offs" for use in commercial products).

Thank you.

Note: if this is an inappropriate issue, please let me know and I will close it.

Hai ,

We are developing Nodemcu board and this github has 4 gerber files related to the Nodemcu board
which one should i select or which is the latest version gerber file???

Hi, all
since esp32 is out for beta, the chip is much more capable than esp8266.
I'd like to know that what features we should added to our new devkit.
usb chip? flash size? pin-to-pin compatible with devkit v1.0?
Thanks in advance.

Hi there guys.

Awesome work on this project. I have a V2 board and cannot find the files anywhere. Do you plan on putting them up?

Where do I find working drivers for OSX 10.10 (Yosemite)?

1. I have OSX 10.10.3 on MBP11,2
2. I downloaded OSX drivers from the vendor website (direct zip download)
3. Unpacked the ZIP, mounted DMG file, installed using the PKG installer.
4. Restarted computer
5. I connected NodeMcu devkit v1.0 through USB 3.0 port

There is a file/folder /Library/Extensions/SiLabsUSBDriver.kext, but no serial port available for the device.

$ ls -lah /dev/cu*
crw-rw-rw-  1 root  wheel   18,   1 Jul  8 13:32 /dev/cu.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel   18,   3 Jul  8 13:32 /dev/cu.Bluetooth-Modem
crw-rw-rw-  1 root  wheel   18,   5 Jul  8 13:32 /dev/cu.DadaFon4-WirelessiAP

$ ls -lah /dev/tty.*
crw-rw-rw-  1 root  wheel   18,   0 Jul  8 13:32 /dev/tty.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel   18,   2 Jul  8 13:32 /dev/tty.Bluetooth-Modem
crw-rw-rw-  1 root  wheel   18,   4 Jul  8 13:32 /dev/tty.DadaFon4-WirelessiAP

No success with ESPlorer and Arduino IDE.

EDIT 1

Apparently it works for some people (?), but not for me: http://blog.squix.ch/2015/05/esp8266-flashing-nodemcu-v10-on-mac-os.html

EDIT 2:

It looks like the kext isn't loaded?

$ kextstat
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
    1   92 0xffffff7f80a3e000 0x8c50     0x8c50     com.apple.kpi.bsd (14.3.0)
    2    7 0xffffff7f80f9c000 0x28c0     0x28c0     com.apple.kpi.dsep (14.3.0)
    3  118 0xffffff7f80a03000 0x20500    0x20500    com.apple.kpi.iokit (14.3.0)
    4  125 0xffffff7f80a24000 0xbf50     0xbf50     com.apple.kpi.libkern (14.3.0)
    5  108 0xffffff7f80a00000 0x2d50     0x2d50     com.apple.kpi.mach (14.3.0)
    6   53 0xffffff7f80a30000 0x8590     0x8590     com.apple.kpi.private (14.3.0)
    7   71 0xffffff7f80a39000 0x4900     0x4900     com.apple.kpi.unsupported (14.3.0)
    8    4 0xffffff7f80da3000 0x9c000    0x9c000    com.apple.kec.corecrypto (1.0) <7 6 5 4 3 1>
    9    0 0xffffff7f80ea4000 0xc000     0xc000     com.apple.kec.pthread (1) <7 6 5 4 1>
   10    1 0xffffff7f80fd5000 0x9000     0x9000     com.apple.kec.Libm (1) <4>
   11   23 0xffffff7f813b7000 0x9000     0x9000     com.apple.iokit.IOACPIFamily (1.4) <7 6 4 3>
   12   31 0xffffff7f80b24000 0x2f000    0x2f000    com.apple.iokit.IOPCIFamily (2.9) <7 6 5 4 3>
   13    2 0xffffff7f82956000 0x5f000    0x5f000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>
   14    1 0xffffff7f810a5000 0xb000     0xb000     com.apple.driver.AppleFDEKeyStore (28.30) <8 7 6 5 4 3 1>
   15    2 0xffffff7f813b0000 0x7000     0x7000     com.apple.iokit.IOReportFamily (31) <5 4 3>
   16   10 0xffffff7f80a47000 0x26000    0x26000    com.apple.iokit.IOStorageFamily (2.0) <7 6 5 4 3 1>
   17    0 0xffffff7f814a7000 0x19000    0x19000    com.apple.driver.DiskImages (396) <16 7 6 5 4 3 1>
   18    1 0xffffff7f822ce000 0xf000     0xf000     com.apple.driver.AppleCredentialManager (1.0) <7 5 4 3 1>
   19    2 0xffffff7f80fa2000 0xd000     0xd000     com.apple.driver.AppleMobileFileIntegrity (1.0.5) <7 6 5 4 3 2 1>
   20    0 0xffffff7f822dd000 0x23000    0x23000    com.apple.driver.AppleKeyStore (2) <19 18 8 7 6 5 4 3 1>
   21    0 0xffffff7f80f9f000 0x2000     0x2000     com.apple.security.TMSafetyNet (8) <7 6 5 4 2 1>
   22    2 0xffffff7f80faf000 0x5000     0x5000     com.apple.kext.AppleMatch (1.0.0d1) <4 1>
   23    1 0xffffff7f80fb4000 0x17000    0x17000    com.apple.security.sandbox (300.0) <22 19 7 6 5 4 3 2 1>
   24    0 0xffffff7f80fcb000 0x9000     0x9000     com.apple.security.quarantine (3) <23 22 7 6 5 4 2 1>
   25    0 0xffffff7f829cc000 0x8000     0x8000     com.apple.nke.applicationfirewall (161) <7 6 5 4 3 1>
   26    0 0xffffff7f82929000 0x3000     0x3000     com.apple.driver.AppleAPIC (1.7) <4 3>
   27    3 0xffffff7f81358000 0x4000     0x4000     com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
   28    0 0xffffff7f829bb000 0x7000     0x7000     com.apple.driver.AppleACPIEC (3.1) <27 13 11 5 4 3>
   29    0 0xffffff7f821e9000 0x4000     0x4000     com.apple.driver.AppleSMBIOS (2.1) <7 4 3>
   30    0 0xffffff7f82546000 0x3000     0x3000     com.apple.driver.AppleHPET (1.8) <11 7 5 4 3>
   31    6 0xffffff7f810b0000 0x76000    0x76000    com.apple.iokit.IOHIDFamily (2.0.0) <14 7 6 5 4 3 2 1>
   32    0 0xffffff7f829c5000 0x4000     0x4000     com.apple.driver.AppleACPIButtons (3.1) <31 13 11 7 6 5 4 3 1>
   33    0 0xffffff7f8220a000 0x8000     0x8000     com.apple.driver.AppleRTC (2.0) <11 5 4 3 1>
   34    1 0xffffff7f825bb000 0x5000     0x5000     com.apple.driver.AppleEFIRuntime (2.0) <7 6 5 4 3>
   35    0 0xffffff7f821d1000 0x8000     0x8000     com.apple.driver.AppleSmartBatteryManager (161.0.0) <27 11 5 4 3 1>
   36    1 0xffffff7f825c0000 0xb000     0xb000     com.apple.driver.AppleEFINVRAM (2.0) <34 7 6 5 4 3 1>
   37   16 0xffffff7f8101d000 0x65000    0x65000    com.apple.iokit.IOUSBFamily (720.4.4) <12 7 5 4 3 1>
   38    0 0xffffff7f81158000 0x22000    0x22000    com.apple.driver.AppleUSBXHCI (710.4.11) <37 12 7 5 4 3 1>
   39    5 0xffffff7f80fde000 0x2c000    0x2c000    com.apple.iokit.IONetworkingFamily (3.2) <7 6 5 4 3 1>
   40    1 0xffffff7f816de000 0x7000     0x7000     com.apple.driver.mDNSOffloadUserClient (1.0.1b8) <39 4 3 1>
   41    1 0xffffff7f816e5000 0xab000    0xab000    com.apple.iokit.IO80211Family (730.60) <39 8 7 6 5 4 3 1>
   42    0 0xffffff7f81798000 0x5e6000   0x5e6000   com.apple.driver.AirPort.Brcm4360 (930.37.3) <41 40 39 12 7 6 5 4 3 1>
   43    7 0xffffff7f8123f000 0xde000    0xde000    com.apple.iokit.IOThunderboltFamily (4.2.2) <5 4 3 1>
   44    0 0xffffff7f820f1000 0x1b000    0x1b000    com.apple.driver.AppleThunderboltNHI (3.1.7) <43 12 11 5 4 3 1>
   45    0 0xffffff7f820df000 0x5000     0x5000     com.apple.driver.AppleThunderboltPCIDownAdapter (2.0.2) <43 12 5 4 3 1>
   46    3 0xffffff7f82133000 0xf000     0xf000     com.apple.driver.AppleThunderboltDPAdapterFamily (4.0.6) <43 11 5 4 3 1>
   47    0 0xffffff7f8215d000 0x6000     0x6000     com.apple.driver.AppleThunderboltDPInAdapter (4.0.6) <46 43 5 4 3 1>
   48    3 0xffffff7f81686000 0x16000    0x16000    com.apple.iokit.IOAHCIFamily (2.7.5) <5 4 3 1>
   49    0 0xffffff7f8292e000 0x1b000    0x1b000    com.apple.driver.AppleAHCIPort (3.1.2) <48 12 5 4 3 1>
   50    0 0xffffff7f816ac000 0x9000     0x9000     com.apple.iokit.IOAHCIPassThrough (1.0.3) <48 5 4 3 1>
   51    0 0xffffff7f816b9000 0x18000    0x18000    com.apple.iokit.IOAHCIBlockStorage (2.7.1) <48 16 6 5 4 3 1>
   52    0 0xffffff7f81fb9000 0x3000     0x3000     com.apple.driver.XsanFilter (404) <16 5 4 3 1>
   53    0 0xffffff7f811bd000 0x1c000    0x1c000    com.apple.driver.AppleUSBHub (705.4.2) <37 5 4 3 1>
   54    0 0xffffff7f81ef5000 0xa000     0xa000     com.apple.BootCache (36) <7 6 5 4 3 1>
   55    0 0xffffff7f8284c000 0x2000     0x2000     com.apple.driver.AppleFileSystemDriver (3.0.1) <16 4 3>
   56    0 0xffffff7f82850000 0x5000     0x5000     com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1>
   57    0 0xffffff7f82857000 0x3000     0x3000     com.apple.AppleFSCompression.AppleFSCompressionTypeDataless (1.0.0d1) <7 6 4 3 2 1>
   58    1 0xffffff7f81df7000 0xde000    0xde000    com.apple.driver.CoreStorage (471.20.7) <16 7 6 5 4 3 1>
   59    0 0xffffff7f81edb000 0x16000    0x16000    com.apple.driver.CoreStorageFsck (471.20.7) <58 16 7 6 5 4 3 1>
   60    1 0xffffff7f8114e000 0xa000     0xa000     com.apple.driver.AppleUSBComposite (705.4.9) <37 4 3 1>
   61    0 0xffffff7f811b6000 0x7000     0x7000     com.apple.driver.AppleUSBMergeNub (705.4.0) <60 37 4 3 1>
   62    4 0xffffff7f80ae2000 0x2b000    0x2b000    com.apple.iokit.IOSCSIArchitectureModelFamily (3.7.5) <5 4 3 1>
   63    1 0xffffff7f8108e000 0x11000    0x11000    com.apple.iokit.IOUSBMassStorageClass (3.7.2) <62 37 16 5 4 3 1>
   64    1 0xffffff7f80eb0000 0x18000    0x18000    com.apple.iokit.IOSCSIBlockCommandsDevice (3.7.5) <62 16 5 4 3 1>
   65    0 0xffffff7f821b6000 0x8000     0x8000     com.apple.driver.AppleUSBCardReader (3.5.5) <64 63 62 37 16 5 4 3 1>
   66    0 0xffffff7f8135c000 0x7000     0x7000     com.apple.iokit.SCSITaskUserClient (3.7.5) <62 16 5 4 3 1>
   67    3 0xffffff7f81144000 0xa000     0xa000     com.apple.iokit.IOUSBHIDDriver (705.4.0) <37 31 5 4 3 1>
   68    0 0xffffff7f81ff2000 0x4000     0x4000     com.apple.driver.AppleUSBTCKeyboard (240.2) <67 37 31 7 6 5 4 3 1>
   69    0 0xffffff7f81ff8000 0x2000     0x2000     com.apple.driver.AppleUSBTCKeyEventDriver (240.2) <31 5 4 3>
   70    0 0xffffff7f82001000 0x13000    0x13000    com.apple.driver.AppleUSBMultitouch (245.2) <67 37 31 6 5 4 3 1>
   71    0 0xffffff7f81ffc000 0x3000     0x3000     com.apple.driver.AppleUSBTCButtons (240.2) <67 37 31 7 6 5 4 3 1>
   72   16 0xffffff7f81450000 0x3b000    0x3b000    com.apple.iokit.IOGraphicsFamily (2.4.1) <12 7 5 4 3 1>
   73    1 0xffffff7f8227b000 0xe000     0xe000     com.apple.driver.AppleSMBusController (1.0.13d1) <27 12 11 5 4 3>
   74    0 0xffffff7f8228c000 0xe000     0xe000     com.apple.driver.AppleMCCSControl (1.2.11) <73 72 12 11 7 5 4 3 1>
   75    4 0xffffff7f81497000 0x10000    0x10000    com.apple.iokit.IONDRVSupport (2.4.1) <72 12 7 5 4 3>
   76    6 0xffffff7f813ca000 0x1a000    0x1a000    com.apple.driver.AppleSMC (3.1.9) <11 7 5 4 3 1>
   77    2 0xffffff7f82820000 0x5000     0x5000     com.apple.driver.AppleBacklightExpert (1.1.0) <75 72 12 5 4 3>
   78    0 0xffffff7f82921000 0x5000     0x5000     com.apple.driver.AppleBacklight (170.7.4) <77 76 75 72 12 5 4 3>
   79    2 0xffffff7f8281d000 0x3000     0x3000     com.apple.driver.AppleGraphicsControl (3.10.22) <72 12 11 7 5 4 3 1>
   80    0 0xffffff7f82825000 0x14000    0x14000    com.apple.driver.AppleMuxControl (3.10.22) <79 77 72 12 11 7 6 5 4 3 1>
   81    1 0xffffff7f82142000 0xe000     0xe000     com.apple.driver.AppleThunderboltDPOutAdapter (4.0.6) <46 43 5 4 3 1>
   82    0 0xffffff7f82150000 0xd000     0xd000     com.apple.driver.AppleThunderboltEDMSink (4.0.2) <81 46 43 5 4 3 1>
   83    6 0xffffff7f813c0000 0xa000     0xa000     com.apple.driver.IOPlatformPluginFamily (5.9.1d7) <11 7 6 5 4 3>
   84    1 0xffffff7f813e6000 0x17000    0x17000    com.apple.driver.X86PlatformPlugin (1.0.0) <83 76 37 11 7 6 5 4 3 1>
   85    1 0xffffff7f81406000 0x12000    0x12000    com.apple.driver.IOPlatformPluginLegacy (1.0.0) <83 11 7 6 5 4 3>
   86    0 0xffffff7f8141a000 0x10000    0x10000    com.apple.driver.ACPI_SMC_PlatformPlugin (1.0.0) <85 83 76 12 11 7 6 5 4 3>
   87    1 0xffffff7f8134e000 0x5000     0x5000     com.apple.iokit.IOSlowAdaptiveClockingFamily (1.0.0) <7 6 5 4 3 1>
   88    0 0xffffff7f82300000 0x2000     0x2000     com.apple.driver.AppleIntelSlowAdaptiveClocking (4.0.0) <87 4 3>
   89    2 0xffffff7f8234f000 0x6f000    0x6f000    com.apple.iokit.IOAcceleratorFamily2 (156.14) <72 12 7 6 5 4 3 1>
   90    3 0xffffff7f82456000 0x6000     0x6000     com.apple.AppleGraphicsDeviceControl (3.10.22) <7 6 5 4 3 1>
   91    0 0xffffff7f8245c000 0x4b000    0x4b000    com.apple.driver.AppleIntelFramebufferAzul (10.0.6) <90 89 72 15 12 11 7 6 5 4 3 1>
   92    0 0xffffff7f82860000 0xa8000    0xa8000    com.apple.driver.AppleCameraInterface (5.33.0) <12 7 6 5 4 3 1>
   93    0 0xffffff7f821de000 0x5000     0x5000     com.apple.driver.AppleSMCLMU (2.0.7d0) <76 72 5 4 3>
   94    1 0xffffff7f810a2000 0x3000     0x3000     com.apple.iokit.IOUSBUserClient (705.4.0) <37 7 5 4 3 1>
   95    0 0xffffff7f821e6000 0x3000     0x3000     com.apple.driver.AppleSMBusPCI (1.0.12d1) <12 5 4 3>
   96    2 0xffffff7f81f01000 0x78000    0x78000    com.apple.vecLib.kext (1.2.0) <10 6 5 4 3>
   97    4 0xffffff7f81f79000 0x30000    0x30000    com.apple.iokit.IOAudioFamily (203.3) <96 5 4 3 1>
   98    2 0xffffff7f82579000 0xc000     0xc000     com.apple.iokit.IOHDAFamily (272.18) <5 4 3 1>
   99    1 0xffffff7f8258c000 0x1c000    0x1c000    com.apple.driver.AppleHDAController (272.18) <98 97 72 12 7 6 5 4 3 1>
  100    0 0xffffff7f822c6000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.3) <83 12 5 4 3>
  101    0 0xffffff7f82111000 0x17000    0x17000    com.apple.driver.AppleThunderboltIP (2.0.2) <43 39 12 5 4 3 1>
  102    0 0xffffff7f8285b000 0x3000     0x3000     com.apple.driver.AppleFIVRDriver (4.1.0) <4 3>
  103    0 0xffffff7f82508000 0xb000     0xb000     com.apple.driver.AppleHV (1) <7 6 5 4 3 1>
  104    0 0xffffff7f82503000 0x3000     0x3000     com.apple.driver.AppleHWAccess (1) <7 5 4 3>
  105    1 0xffffff7f81339000 0x13000    0x13000    com.apple.iokit.IOSurface (97.4) <7 5 4 3 1>
  106    0 0xffffff7f823cc000 0x60000    0x60000    com.apple.driver.AppleIntelHD5000Graphics (10.0.6) <105 89 72 12 7 6 5 4 3 1>
  107    0 0xffffff7f81df1000 0x5000     0x5000     com.apple.Dont_Steal_Mac_OS_X (7.0.0) <76 7 4 3 1>
  108    2 0xffffff7f8154a000 0xab000    0xab000    com.apple.iokit.IOBluetoothFamily (4.3.4f4) <15 7 5 4 3 1>
  109    0 0xffffff7f81011000 0x6000     0x6000     com.apple.iokit.IOUserEthernet (1.0.1) <39 6 5 4 3 1>
  110    1 0xffffff7f81605000 0x23000    0x23000    com.apple.iokit.IOBluetoothHostControllerUSBTransport (4.3.4f4) <108 37 12 11 7 5 4 3 1>
  111    0 0xffffff7f81628000 0x9000     0x9000     com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (4.3.4f4) <110 108 37 12 11 7 5 4 3>
  112    0 0xffffff7f81533000 0x2000     0x2000     com.apple.iokit.IOBluetoothUSBDFU (4.3.4f4) <37 4 3>
  113    0 0xffffff7f81fc2000 0x5000     0x5000     com.apple.driver.AppleUpstreamUserClient (3.6.1) <72 12 11 7 5 4 3 1>
  114    1 0xffffff7f825a8000 0x13000    0x13000    com.apple.kext.OSvKernDSPLib (1.15) <5 4>
  115    1 0xffffff7f825cb000 0x131000   0x131000   com.apple.driver.DspFuncLib (272.18) <114 97 96 36 6 5 4 3 1>
  116    0 0xffffff7f82706000 0xab000    0xab000    com.apple.driver.AppleHDA (272.18) <115 99 98 97 75 72 6 5 4 3 1>
  117    0 0xffffff7f82841000 0x7000     0x7000     com.apple.driver.AppleGraphicsDevicePolicy (3.7.7) <90 79 72 12 11 7 6 5 4 3 1>
  118    0 0xffffff7f82269000 0x4000     0x4000     com.apple.driver.AppleOSXWatchdog (1) <12 7 6 5 4 3 1>
  119    0 0xffffff7f82588000 0x2000     0x2000     com.apple.driver.AppleHDAHardwareConfigDriver (272.18) <4 3>
  120    1 0xffffff7f813fd000 0x7000     0x7000     com.apple.driver.X86PlatformShim (1.0.0) <84 83 76 7 4 3>
  121    0 0xffffff7f82800000 0x14000    0x14000    com.apple.driver.AGPM (110.19.5) <90 83 75 72 12 5 4 3>
  122    0 0xffffff7f82262000 0x4000     0x4000     com.apple.driver.ApplePlatformEnabler (2.2.0d4) <7 5 4 3>
  123    1 0xffffff7f8120b000 0xe000     0xe000     com.apple.iokit.IOSerialFamily (11) <7 6 5 4 3 1>
  124    0 0xffffff7f81536000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (4.3.4f4) <123 7 5 4 3 1>
  125    2 0xffffff7f80e3f000 0x5000     0x5000     com.apple.kext.triggers (1.0) <7 6 5 4 3 1>
  126    0 0xffffff7f80f91000 0x9000     0x9000     com.apple.filesystems.autofs (3.0) <125 7 6 5 4 3 1>
  127    0 0xffffff7f81fb1000 0x5000     0x5000     com.apple.driver.AudioAUUC (1.70) <97 72 12 11 7 5 4 3 1>
  128    3 0xffffff7f829d6000 0x58000    0x58000    org.virtualbox.kext.VBoxDrv (4.3.28) <7 5 4 3 1>
  129    0 0xffffff7f82a2e000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (4.3.28) <128 94 37 7 5 4 3 1>
  130    0 0xffffff7f82a36000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (4.3.28) <128 7 5 4 3 1>
  131    0 0xffffff7f82a3b000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (4.3.28) <128 5 4 1>
  132    0 0xffffff7f80e44000 0x59000    0x59000    com.apple.filesystems.smbfs (3.0.1) <125 8 7 6 5 4 3 1>

Edit 3:

$ kextutil -tn /Library/Extensions/SiLabsUSBDriver.kext
/Library/Extensions/SiLabsUSBDriver.kext appears to be loadable (including linkage for on-disk libraries).

Edit 4:

The device does work, as I can join its network and ping it.

i was trying make circuit design with nodemcu with proteus software but couldn't find the include libraries to work with it in the proteus software. Can any anyone help.

Hello gentleman,
I would like to use Nodemcu as a part in my PCB layout. But I can't find any library for Eagle. Is there any existing one? Or does anybody plan to create one?
Thanks.

Hi,

I can not save files to the file system on my board. I have tried the last 4 firmware releases and it doesn't change the problem. It seems to be related to the amica boards. I have the revision before this and it works 100% of the time.

file.open("script1.lua","w+")
file.writeline([[print( "Hello World" )]])
file.close()

OUTPUT:

stdin:1: open a file first

I am opening the file on the first line.

Please help

Is it possible to publish the Vowstar_*.IntLib files?

I'd like to import these into EasyEDA but it can only import the ascii versions. Can someone export these files from Altium as ASCII? Thanks!