- 04 Aug, 2016 1 commit
-
-
Marcel Stör authored
-
- 02 Aug, 2016 1 commit
-
-
Yury Popov authored
-
- 05 Jun, 2016 1 commit
-
-
Philip Gladstone authored
Fixes #1164 and thus also #1150, #1149, #1147 and #898. * Move to latest version of SPIFFS * Add SPIFFS porting layer for NodeMCU * Add option to delete output if it doesn't fit * Change FLASHSIZE to be in bits by default: default 4mb 32mb * Add SPIFFS_MAX_FILESYSTEM_SIZE override * Add notes on SPIFFS_FIXED_LOCATION * Add 1M boundary * Include the current version of the LICENSE
-
- 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.
-
- 20 Mar, 2016 1 commit
-
-
philip authored
-
- 06 Mar, 2016 1 commit
-
-
TerryE authored
-
- 03 Mar, 2016 1 commit
-
-
TerryE authored
-
- 01 Mar, 2016 1 commit
-
-
TerryE authored
-
- 26 Feb, 2016 1 commit
-
-
TerryE authored
AFAIK no one uses the wifi.startsmart() and wifi.stopsmart(). Removing them frees up an extra 20-25K of Flash to use as filesystem. So I have added a new config define WIFI_SMART_ENABLE which is enabled by default so the default functionality is the same, but if this is commented out then this code is omitted. I have also removed wofs and upgrade from this build as we no longer support these.
-
- 20 Feb, 2016 1 commit
-
-
TerryE authored
-
- 17 Feb, 2016 1 commit
-
-
TerryE authored
As with the last commit this rolls up the follwowing, but include the various review comments on the PR. - **Documentation changes**. I've added the taks FAQ as a stub new Extension developer FAQ, and split the old FAQ into a Lua Developer FAQ and a Hardware FAQ. - **Tasking I/F**. New `app/task/Makefile`, `app/task/task.c`, `app/include/task/task.h` and `app/Makefile` as per previous commit. Cascade changes to `app/driver/uart.c`, `app/include/driver/uart.h`, `app/user/user_main.c` and `app/modules/node.c` - **GPIO Rework** to `app/modules/gpio.c` and `pin_map.[hc]`, `platform.[hc]` in `app/platform` - **Other Optimisations** Move the `platform_*_exists()` from `app/platform/common.c` to static inline declarations in `platform.h` as this generates faster, smaller code. Move lgc.a routines out of iram0.
-
- 20 Jan, 2016 1 commit
-
-
Johny Mattsson authored
Plus boat-load of fixes to actually make that build.
-
- 15 Jan, 2016 1 commit
-
-
Johny Mattsson authored
Reduces the size from 179 to 102 bytes.
-
- 14 Jan, 2016 1 commit
-
-
philip authored
-
- 12 Jan, 2016 1 commit
-
-
Johny Mattsson authored
-
- 02 Jan, 2016 1 commit
-
-
dnc40085 authored
node.dsleep was using sint32 to hold sleep time when it should be using uint32
-
- 16 Dec, 2015 1 commit
-
-
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.
-
- 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.
-
- 09 Nov, 2015 1 commit
-
-
Johny Mattsson authored
This got broken in the 1.4.0 overhaul, mea culpa.
-
- 08 Nov, 2015 1 commit
-
-
TerryE authored
-
- 12 Oct, 2015 2 commits
-
-
Johny Mattsson authored
It was piggybacking on the Lua readline timer which no longer exists. Also cleaned up injection of Lua commands via CoAP & node.input().
-
Johny Mattsson authored
Again, the os_xxx version has been removed from the SDK.
-
- 10 Aug, 2015 1 commit
-
-
devsaurus authored
-
- 03 Jul, 2015 2 commits
- 27 Jun, 2015 1 commit
-
-
Johny Mattsson authored
-
- 26 Mar, 2015 1 commit
-
-
HuangRui authored
-
- 17 Mar, 2015 1 commit
-
-
Markus Gritsch authored
This function allows setting the CPU frequency to node.CPU80MHZ or node.CPU160MHZ.
-
- 15 Mar, 2015 3 commits
- 06 Mar, 2015 1 commit
-
-
funshine authored
-
- 16 Feb, 2015 2 commits
-
-
HuangRui authored
Bug not fixed in this version =(
-
HuangRui authored
The open source LWIP is broken, use espressif's liblwip.a. Uses system_get_vdd33 instead of readvdd33. The espressif's sdk0.9.6 beta1 (2015.02.15) release note 1、Optimize smartconfig to version v0.8; 2、Optimize AT to version 0.22.b1; 1>、Fixed bugs; 2>、Optimize the speed of transparent transmission; 3、Optimize boot to version 1.3(b3); 1>、Fix compatibility problem of dual flash ; 4、Solve problem of the large current in deep sleep; 5、Fixed problem “check mem fail”; 6、Fixed problem of UDP socket may stop listening broadcast packet after a long time running under some special router; 7、Fixed bug related to wifi_station_scan; 8、Other optimize to make the software more reliable;
-
- 13 Feb, 2015 1 commit
-
-
funshine authored
-
- 12 Feb, 2015 1 commit
-
-
funshine authored
-
- 29 Jan, 2015 1 commit
-
-
HuangRui authored
* dsleep( us, option ) Hardware has to support deep-sleep wake up (XPD_DCDC connects to EXT_RSTB with 0R). system_deep_sleep(0) ,set no wake up timer,connect a GPIO to pin RST, the chip will wake up by a falling-edge on pin RST. ** us: Integer time to sleep. if us = 0, it will sleep forever. ** option: Integer option=0, init data byte 108 is valuable; option>0, init data byte 108 is valueless. More details as follows: 0, RF_CAL or not after deep-sleep wake up, depends on init data byte 108. 1, RF_CAL after deep-sleep wake up, there will belarge current. 2, no RF_CAL after deep-sleep wake up, there will only be small current. 4, disable RF after deep-sleep wake up, just like modem sleep, there will be the smallest current.
-
- 28 Jan, 2015 1 commit
-
-
alonewolfx2 authored
usage: -- no wakeup until rst pin to low node.dsleep(0) -- 4 mean no RF after deepsleep. node.dsleepsetoption(4)
-
- 26 Jan, 2015 1 commit
-
-
alonewolfx2 authored
example usage and result ``` print(node.readvdd33()) 3348 > ```
-
- 05 Jan, 2015 1 commit
-
-
HuangRui authored
-