- 09 Jun, 2016 1 commit
-
-
Johny Mattsson authored
A fair bit of reshuffling with include paths and overrides was necessary, as the two RTOS SDKs (ESP8266 and ESP32) don't have the same header structure (or even libraries for that matter). Uses the xtensa-esp108-elf toolchain to build. Completely untested beyond linking, as I still can't flash the ESP32 module I have :( I'd be most surprised if it does anything useful at this point considering I've spent almost no time on the linker script or UART setup. Anything using espconn has been ifdef'd out since espconn is not (and probably will not be) available. Notably this includes the entire net module as well as coap, mqtt and enduser_setup. Many (most?) hardware bus drivers and related modules are also ifdef'd out for now due to hardware differences. Functions surrounding sleep, rtc and RF modes have also been hit by the ifdef hammer. Grep'ing for __ESP8266__ and/or FIXME is a quick way of finding these places. With time I hope all of these will be reinstated.
-
- 30 May, 2016 1 commit
-
-
Johny Mattsson authored
Uart driver currently disabled as it's not (yet) compatible with RTOS. Running Lua task with excessive stack to avoid smashing it; need to work out what's using so much stack space. Changed some flash reading functions to not attempt to drop an entire 4k flash page onto the stack. Ensure the task pump doesn't attempt to retrieve from uninitialised queues.
-
- 18 May, 2016 1 commit
-
-
Johny Mattsson authored
- Stop fighting against the SDK in terms of owning/writing the init_data block. NodeMCU included a default init_data block because originally the SDK did not, but by now it's not needed. - Expose a way to reconfigure the ADC mode from Lua land. With most people using the cloud builder and not able to change the #define for byte 107 this has been a pain point. - Less confusion about which init_data has been used. Lua code can now simply state what mode it wants the ADC to be in, and not worry about the rest of the init_data complexities such as the init_data changing location due to flashing with wrong flash_size setting, or doing/not doing a chip-erase before loading new NodeMCU firmware.
-
- 16 Dec, 2015 2 commits
-
-
Johny Mattsson authored
Module creation & registration now made a lot simpler. In essence, each module file is now self-contained and only needs a NODEMCU_MODULE(MYNAME, "myname", myname_map, luaopen_myname); line to both be automatically recognised by the Lua initialization as well as honor the LUA_USE_MODULES_MYNAME #define.
-
TerryE authored
carrying on Johny's edits as per my comments on #810
-
- 12 Dec, 2015 1 commit
-
-
Johny Mattsson authored
As per #810 & #796, only LUA_OPTIMIZE_MEMORY=2 & MIN_OPT_LEVEL=2 are supported when building. This commit effects that limitation. With this change modules/auxmods.h no longer needs to be updated for every new module, nor do module writers need to cater for a hypothetical LUA_OPTIMIZE_MEMORY < 2 scenario.
-
- 10 Nov, 2015 1 commit
-
-
Johny Mattsson authored
-
- 17 Oct, 2015 1 commit
-
-
aeprox authored
Replace undocumented readvdd33 function with SDK function system_get_vdd33
-
- 23 May, 2015 1 commit
-
-
dnc40085 authored
connected
-
- 19 May, 2015 1 commit
-
-
HuangRui authored
-
- 26 Mar, 2015 1 commit
-
-
HuangRui authored
-
- 05 Jan, 2015 1 commit
-
-
HuangRui authored
-
- 22 Dec, 2014 1 commit
-
-
funshine authored
-