- 26 Dec, 2016 1 commit
-
-
Arnim Läuger authored
-
- 04 Dec, 2016 1 commit
-
-
Arnim Läuger authored
-
- 27 Oct, 2016 1 commit
-
-
Philip Gladstone authored
-
- 18 Oct, 2016 1 commit
-
-
Arnim Läuger authored
Thank you.
-
- 13 Oct, 2016 1 commit
-
-
Arnim Läuger authored
-
- 04 Oct, 2016 2 commits
-
-
Jim Paris authored
The esp_init_data_default.bin is now extracted from the SDK (and its patch file, if present), and the contents are automatically embedded into user_main.o.
-
Johny Mattsson authored
To work around the pesky "rf_cal[0] !=0x05" hang when booting on a chip which doesn't have esp_init_data written to it. It is no longer possible to do the writing of the esp_init_data_default from within nodemcu_init(), as the SDK now hangs long before it gets there. As such, I've had to reimplement this in our user_start_trampoline and get it all done before the SDK has a chance to look for the init data. It's unfortunate that we have to spend IRAM on this, but I see no better alternative at this point.
-
- 03 Oct, 2016 1 commit
-
-
Johny Mattsson authored
Input during startup (especially while doing initial filesystem format) ran the risk of filling up the task queue, preventing the start_lua task from being queued, and hence NodeMCU would not start up that time.
-
- 05 Sep, 2016 1 commit
-
-
Arnim Läuger authored
* Add FatFs * enable BUILD_FATFS for all-module build * push vfs into rest of firmware * align maximum filename length * increase timeout for acmd41 during card initialization * switch from DOS to Unix path semantics chdrive() is substituted by chdir() * update to fatfs R.012a incl. patches 1-6 * add callback for rtc provisioning in file * update docs
-
- 04 Sep, 2016 1 commit
-
-
Yury Popov authored
Fixes #1457
-
- 24 Jul, 2016 1 commit
-
-
Marcel Stör authored
-
- 22 Jul, 2016 1 commit
-
-
Arnim Läuger authored
-
- 05 Jun, 2016 2 commits
-
-
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
-
dnc40085 authored
-
- 27 May, 2016 1 commit
-
-
dnc40085 authored
Moved call from `luaopen_wifi (wifi.c)` to `user_rf_pre_init (user_main.c)` Note: This change adds ~440 us to boot time
-
- 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.
-
- 23 Mar, 2016 1 commit
-
-
devsaurus authored
-
- 20 Mar, 2016 1 commit
-
-
philip authored
-
- 11 Mar, 2016 1 commit
-
-
TerryE authored
-
- 10 Mar, 2016 1 commit
-
-
Bernd Meyer 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.
-
- 23 Dec, 2015 1 commit
-
-
Johny Mattsson authored
Removed earlier TCP port randomisation fix - the new SDK has its own fix even though Espressif told me they wouldn't fix it. Yay?
-
- 12 Nov, 2015 1 commit
-
-
Johny Mattsson authored
Make ADC vs readvdd33 option user_config.h configurable for the init data, and made readvdd33 the default.
-
- 05 Nov, 2015 1 commit
-
-
Johny Mattsson authored
This addresses the issue where a server would otherwise reject a valid connection attempt from a rebooted node, due to the server thinking that packet belonged to a recently closed session. By starting off the local TCP port numbers at random* points each boot the risk of port reuse across a reboot is significantly reduced. *) As random as can be had via the lower 12 bits of the ccounter.
-
- 01 Nov, 2015 1 commit
-
-
Jonathan karras 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
The Lua input timer has been the thorn in the side which prevents a lot of potential sleeping, unnecessarily.
-
- 10 Jul, 2015 2 commits
-
-
Johny Mattsson authored
-
Johny Mattsson authored
Added Lua module rtctime to interface with it. This keeps as accurate time as is possible on the ESP8266, including across deep sleeps (provided rtctime.dsleep() is used rather than node.dsleep()). Intended to be used together with NTP for high accuracy time keeping. The API is via rtctime.{get,set}timeofday(), working from Unix epoch. Note that 160MHz CPU clock is not currently supported by the rtctime code, as it is only aware of the 52MHz boot clock and the regular 80Mhz default clock. See rtctime.h for detailed info on how this all works.
-
- 23 Jun, 2015 2 commits
-
-
Johny Mattsson authored
Accessing 8bit and 16bit constants from ROM rather than RAM comes with a performance cost, as these loads go through the load/store exception vector. Any performance critical constants can be forced back into RAM as RAM_CONST_ATTR. The entry point has changed from call_user_start() to user_start_trampoline() in order for the exception handler to be installed early enough.
-
Johny Mattsson authored
-
- 29 May, 2015 1 commit
-
-
dnc40085 authored
-
- 21 May, 2015 1 commit
-
-
HuangRui authored
-
- 02 Apr, 2015 1 commit
-
-
funshine authored
-
- 15 Mar, 2015 1 commit
-
-
HuangRui authored
-
- 23 Jan, 2015 1 commit
-
-
funshine authored
-
- 06 Jan, 2015 1 commit
-
-
HuangRui authored
-
- 05 Jan, 2015 2 commits
- 30 Dec, 2014 1 commit
-
-
HuangRui authored
-