Go to file
Johny Mattsson 51912d5505
Reworked linker magic to work with IDF 3.3 (#2805)
With the IDF asserting full control over the linker scripts and insisting on
the application description being the first entry in the .flash.rodata
section, or previous method of doing link-time arrays stopped working.
Why? Because the build patched in a SHA256 digest straight into our arrays.

With the limited language of the gcc linker scripts I could find no other
way of getting it in cleanly.

The IDF "linker fragments" support can not be made to work for our needs:
  - no support for setting alignment before including objects
  - no support for declaring symbols
  - no support for adding our terminating zeros
  - insists on grouping objects by lib rather than by declared grouping,
    which means we could at most have a single link-time-array using
    the IDF mechanism
  - also does not like underscores in section names, but that's just an
    annoyance

So, the least bad option that I could come up with was to use a project-wide
makefile snippet to add a target in-between the IDF's generation of the
esp32.project.ld file, and the linking of our NodeMCU.elf. In this target
we read in the esp32.project.ld linker script, check whether we have our
arrays in there, and if not rewrites the linker script.

Oh, and the esp32.project.ld file only came into existence on the IDF 3.3
branch, so I had to change up the IDF to the latest release/3.3 as well.
I would've preferred a stable tag, but the v3.3-beta3 had a really nasty
regression for us (can't add partition entry), so that was a no-go.
2019-06-22 12:05:34 +10:00
.github Update ISSUE_TEMPLATE.md 2016-05-02 21:39:05 +02:00
components Reworked linker magic to work with IDF 3.3 (#2805) 2019-06-22 12:05:34 +10:00
docs ESP32: Pulse counter module released (#2739) 2019-06-12 22:34:24 +02:00
examples consolidate telnet example 2016-01-06 23:18:42 +01:00
lua_compat Set missing DATABITS_8 property (#2672) 2019-04-22 11:41:13 +02:00
lua_examples remove table-based (un)sunscribe from mqtt docs and provide example code 2019-01-31 22:35:21 +01:00
lua_modules Joystick Lua library and example code (#2710) 2019-04-22 14:46:49 +02:00
sdk Reworked linker magic to work with IDF 3.3 (#2805) 2019-06-22 12:05:34 +10:00
tools ESP32 precompiled toolchain (#2730) 2019-04-22 14:45:27 +02:00
.gitignore ESP32: Pulse counter module released (#2739) 2019-06-12 22:34:24 +02:00
.gitmodules ESP32 precompiled toolchain (#2730) 2019-04-22 14:45:27 +02:00
.travis.yml Use Xenial distribution for Travis (#2736) 2019-04-22 19:45:59 +02:00
CONTRIBUTING.md Switch from readthedocs.org to readthedocs.io 2016-04-28 08:09:35 +02:00
LICENSE update doc 2014-11-21 00:10:01 +08:00
Makefile ESP32 precompiled toolchain (#2730) 2019-04-22 14:45:27 +02:00
README.md Add ESP32 README.md and build/flash docs (#1873) 2017-03-24 23:51:13 +01:00
mkdocs.yml add pulsecnt.md to mkdocs 2019-06-12 22:36:06 +02:00
sdkconfig.defaults select custom partition table in sdkconfig.defaults (#2636) 2019-04-17 22:44:08 +02:00

README.md

NodeMCU on ESP32

Join the chat at https://gitter.im/nodemcu/nodemcu-firmware Build Status Documentation Status License

A Lua based firmware for ESP32 WiFi SOC

NodeMCU is an eLua based firmware for the ESP32 WiFi SOC from Espressif. The firmware is based on the Espressif IoT Development Framework and uses a file system based on spiffs. The code repository consists of 98.1% C-code that glues the thin Lua veneer to the SDK.

The NodeMCU firmware is a companion project to the popular NodeMCU dev kits, ready-made open source development boards with ESP8266-12E chips.

Summary

  • Easy to program wireless node and/or access point
  • Based on Lua 5.1.4 (without debug, os modules)
  • Asynchronous event-driven programming model
  • 10+ built-in modules
  • Firmware available with or without floating point support (integer-only uses less memory)
  • Up-to-date documentation at https://nodemcu.readthedocs.io

Programming Model

The NodeMCU programming model is similar to that of Node.js, only in Lua. It is asynchronous and event-driven. Many functions, therefore, have parameters for callback functions. To give you an idea what a NodeMCU program looks like study the short snippets below. For more extensive examples have a look at the /lua_examples folder in the repository on GitHub.

-- a simple HTTP server
srv = net.createServer(net.TCP)
srv:listen(80, function(conn)
	conn:on("receive", function(sck, payload)
		print(payload)
		sck:send("HTTP/1.0 200 OK\r\nContent-Type: text/html\r\n\r\n<h1> Hello, NodeMCU.</h1>")
	end)
	conn:on("sent", function(sck) sck:close() end)
end)
-- connect to WiFi access point
wifi.mode(wifi.STATION, true)

wifi.sta.on("connected", function() print("connected") end)
wifi.sta.on("got_ip", function(event, info) print("got ip "..info.ip) end)

-- mandatory to start wifi after reset
wifi.start()
wifi.sta.config({ssid="SSID", pwd="password", auto=true}, true)

Documentation

The entire NodeMCU documentation is maintained right in this repository at /docs. The fact that the API documentation is maintained in the same repository as the code that provides the API ensures consistency between the two. With every commit the documentation is rebuilt by Read the Docs and thus transformed from terse Markdown into a nicely browsable HTML site at https://nodemcu.readthedocs.io/en/dev-esp32/.

Support

See https://nodemcu.readthedocs.io/en/dev/en/support/.

License

MIT © zeroday/nodemcu.com