j3d1/esp-open-rtos
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
53 commits 10 branches 1 tag 25 MiB
C 98.2%
C++ 0.7%
Makefile 0.5%
Assembly 0.2%
Python 0.2%
Other 0.1%
Find a file
Angus Gratton a173ffa81d Remove custom entry point, pending merge of esptool.py patch adding --entry-symbol option
2015-06-03 14:29:56 +10:00
axtls Fix up submodule paths, add some hints for submodule usage 2015-06-02 18:51:22 +10:00
examples Change symbol extraction to use objdump not nm 2015-06-02 17:57:33 +10:00
FreeRTOS Change symbol extraction to use objdump not nm 2015-06-02 17:57:33 +10:00
include Rename the sdk_prototypes header to sdk_private 2015-06-02 17:15:00 +10:00
ld Remove custom entry point, pending merge of esptool.py patch adding --entry-symbol option 2015-06-03 14:29:56 +10:00
lib Remove custom entry point, pending merge of esptool.py patch adding --entry-symbol option 2015-06-03 14:29:56 +10:00
lwip Fix up submodule paths, add some hints for submodule usage 2015-06-02 18:51:22 +10:00
.dir-locals.el Working variant of esp_iot_rtos_sdk (files from commit ec75c85f9ef53) 2015-05-07 14:22:25 +10:00
.gitignore gitignore: Ignore gdb history 2015-05-07 14:24:44 +10:00
.gitmodules Fix up submodule paths, add some hints for submodule usage 2015-06-02 18:51:22 +10:00
common.mk Remove custom entry point, pending merge of esptool.py patch adding --entry-symbol option 2015-06-03 14:29:56 +10:00
LICENSE Add actual LICENSE file 2015-06-03 07:53:55 +10:00
README.md Add wiki link, clean up README a bit 2015-06-03 09:15:56 +10:00

README.md

esp-open-rtos

A community developed open source FreeRTOS-based framework for ESP8266 WiFi-enabled microcontrollers. Intended for use in both commercial and open source projects.

Similar to, but substantially different from, the Espressif IOT RTOS SDK.

Quick Start

  • Install esp-open-sdk and make the toolchain available on your PATH. (Despite the similar name esp-open-sdk has different maintainers - but we think it's fantastic!)

    (Other toolchains will also work, as long as a gcc cross-compiler is available on the PATH. The proprietary Tensilica "xcc" compiler will probably not work.)

  • Install esptool.py and make it available on your PATH.

  • The build process uses GNU Make, and the utilities sed and grep. Linux & OS X should have these already. Windows users can get these tools a variety of ways - MingGW is one option.

  • Use git to clone the esp-open-rtos project (note the --recursive):

git clone --recursive git@github.com:superhouse/esp-open-rtos.git
cd esp-open-rtos
  • Build an example project (found in the 'examples' directory) and flash it to a serial port:
make flash -j4 -C examples/http_get ESPPORT=/dev/ttyUSB0

Run make help -C examples/http_get for a summary of other Make targets.

The Build Process wiki page has in-depth details of the build process.

Goals

  • Provide professional-quality framework for WiFi-enabled RTOS projects on ESP8266.
  • Open source code for all layers above the MAC layer, ideally lower layers if possible (this is a work in progress, see Issues list.
  • Leave upstream source clean, for easy interaction with upstream projects.
  • Flexible build and compilation settings.

Current status is alpha quality, under development. AP STATION mode (ie wifi client mode) and UDP/TCP client modes are tested. Other functionality should work. Contributors and testers are welcome!

Open Source Components

  • FreeRTOS V7.5.2
  • lwIP v1.4.1, modified via the esp-lwip project by @kadamski.
  • axTLS compiled from development version v1.5.3, plus modifications for low memory devices.

Binary Components

Binary libraries (inside the lib dir) are all supplied by Espressif as part of their RTOS SDK. These parts were MIT Licensed.

As part of the esp-open-rtos build process, all binary SDK symbols are prefixed with sdk_. This makes it easier to differentiate binary & open source code, and also prevents namespace conflicts.

Some binary libraries appear to contain unattributed open source code:

  • libnet80211.a & libwpa.a appear to be based on FreeBSD net80211/wpa, or forks of them. (See this issue).
  • libudhcp has been removed from esp-open-rtos. It was released with the Espressif RTOS SDK but udhcp is GPL licensed.

Licensing

  • BSD license (as described in LICENSE) applies to original source files, and lwIP. LWIP is Copyright (C) Swedish Institute of Computer Science.

  • FreeRTOS is provided under the GPL with the FreeRTOS linking exception, allowing non-GPL firmwares to be produced using FreeRTOS as the RTOS core. License details in files under FreeRTOS dir. FreeRTOS is Copyright (C) Real Time Engineers Ltd.

  • Source & binary components from the Espressif IOT RTOS SDK were released under the MIT license. Source code components are relicensed here under the BSD license. Components are Copyright (C) Espressif Systems.

Contributions

Contributions are very welcome!

  • If you find a bug, please raise an issue to report it.

  • If you have feature additions or bug fixes then please send a pull request.

  • There is a list of outstanding 'enhancements' in the issues list. Contributions to these, as well as other improvements, are very welcome.

If you are contributing code, please ensure that it can be licensed under the BSD open source license. Specifically:

  • Code from Espressif IoT SDK cannot be merged, as it is provided under either the "Espressif General Public License" or the "Espressif MIT License", which are not compatible with the BSD license.

  • Recent releases of the Espressif IoT RTOS SDK cannot be merged, as they changed from MIT License to the "Espressif MIT License" which is not BSD compatible. The Espressif binaries used in esp-open-rtos were taken from revision ec75c85, as this was the last MIT Licensed revision.

For code submissions based on reverse engineered binary functionality, please either reverse engineer functionality from MIT Licensed Espressif releases or make sure that the reverse engineered code does not directly copy the code structure of the binaries - it cannot be a "derivative work" of an incompatible binary.

The best way to write suitable code is to first add documentation somewhere like the esp8266 wiki describing factual information gained from reverse engineering - such as register addresses, bit masks, orders of register writes, etc. Then write new functions referring to that documentation as reference material.

Sponsors

Work on esp-open-rtos is sponsored by SuperHouse Automation.