- 11 Aug, 2021 1 commit
-
-
Johny Mattsson authored
The uzlib and parts of Lua had to be switched over to use the C standard int types, as their custom typedefs conflicted with RISC-V toolchain provided typedefs. UART console driver updated to do less direct register meddling and use the IDF uart driver interface for setup. Still using our own ISR rather than the default driver ISR. Down the line we might want to investigate whether the IDF ISR would be a better fit. Lua C modules have been split into common and ESP32/ESP32-S specific ones. In the future there might also be ESP32-C3 specific modules, which would go into components/modules-esp32c3 at that point. Our old automatic fixup of flash size has been discarded as it interferes with the checksumming done by the ROM loader and results in unbootable systems. The IDF has already taken on this work via the ESPTOOL_FLASHSIZE_DETECT option, which handles this situation properly.
-
- 04 Aug, 2021 1 commit
-
-
Johny Mattsson authored
-
- 29 Jul, 2021 1 commit
-
-
Johny Mattsson authored
I2S constants have changed; docs updated.
-
- 28 Jul, 2021 3 commits
-
-
Johny Mattsson authored
- Added support for WPA3 - Evicted left-over broken WiFi auto-reconnect - Updated docs
-
Johny Mattsson authored
-
Johny Mattsson authored
-
- 26 Jul, 2021 1 commit
-
-
Johny Mattsson authored
-
- 22 Jul, 2021 1 commit
-
-
Johny Mattsson authored
Updated docs to reflect new WiFi station connect behaviour.
-
- 21 Jul, 2021 2 commits
-
-
Johny Mattsson authored
Now boots to the Lua prompt, and modules are included and findable.
-
Johny Mattsson authored
Plus addressing some warnings.
-
- 20 Jul, 2021 1 commit
-
-
Johny Mattsson authored
Only compile-tested so far. Of note is that the WiFi auto-connect (flag) functionality has been removed from the IDF, and as a follow-on so has the "auto" field in the wifi config. On the Ethernet side, support for the TLK110 PHY seems to have been removed, but on the other hand there is now new support for several others.
-
- 19 Jul, 2021 1 commit
-
-
Johny Mattsson authored
Some parts dry-coded in the disabled modules; to be fixed when sorting out the deprecated/removed APIs used in said modules. Still untested beyond compile/linking.
-
- 15 Jul, 2021 2 commits
-
-
Johny Mattsson authored
-
Johny Mattsson authored
Yet to come: - part 2: dealing with deprecated and removed APIs - part 3: making it actually work again
-
- 02 Apr, 2021 1 commit
-
-
Marcel Stör authored
-
- 14 Feb, 2021 1 commit
-
-
tomsci authored
-
- 22 Jan, 2021 1 commit
-
-
jmdasnoy authored
-
- 17 Jan, 2021 1 commit
-
-
tomsci authored
Supporting wakeup from (non-EXT1) GPIO, UART, ULP, timer and touch
-
- 05 Jan, 2021 2 commits
- 17 Sep, 2020 1 commit
-
-
Marcel Stör authored
Undos changes from #3135
-
- 23 Aug, 2020 1 commit
-
-
Nathaniel Wesley Filardo authored
Using the NODEMCU_ namespace prefix makes it obvious that these are not part of Lua proper (contrast, e.g., LUA_BUILTIN_STRING). Using "CMODULE" gives us room to differentiate between modules whose implementation is in C and whose implemenation is in Lua ("LMODULE"). The ESP8266 branch can adopt the same convention when it moves to Kconfig; see https://github.com/nodemcu/nodemcu-firmware/issues/3130
-
- 22 Aug, 2020 1 commit
-
-
tomsci authored
-
- 03 Aug, 2020 1 commit
-
-
David Thornley authored
Manifests as multiple definition of esp_event_send during compilation, as bthci triggers inclusion of `event_loop.c`. Also improved lbth_init() to support BTDM or BLE_ONLY controller modes.
-
- 27 Jul, 2020 1 commit
-
-
Javier Peletier authored
-
- 08 Jul, 2020 1 commit
-
-
Marcel Stör authored
-
- 18 May, 2020 1 commit
-
-
tomsci authored
-
- 01 May, 2020 1 commit
-
-
Tom Sutcliffe authored
-
- 27 Apr, 2020 1 commit
-
-
tomsci authored
Fixes #2880
-
- 29 Oct, 2019 1 commit
-
-
f4grx authored
Fixes #2933
-
- 27 Oct, 2019 1 commit
-
-
John Lauer authored
* Touch module 1st checkin * ESP32. Check-in 2 for Touch sensor module * ESP32: Touch module. Sample Lua code. * ESP32: Latest YouTube vid * ESP32: Touch docs update * Added opt_* methods for value retrieval
-
- 12 Oct, 2019 1 commit
-
-
Johny Mattsson authored
* Fix uart regressions & bugs. Using `uart.on()` with a search character was broken in that it did not invoke the callback on a full UART buffer as documented. Logic reworked to match docs again. Fixed memory leak on `task_post()` failure (eep!). Improved logic to attempt to coalesce input bytes to reduce the number of `task_post()` slots used up by the platform uart. Finally, added a semaphore to prevent the platform uart from overrunning the `task_post()` slots all the time on high baud rates (e.g. 1mbit). With the semaphore in there, the LVM RTOS task gets a chance to actually process the received data and free up a `task_post()` slot or two. The above mentioned read coalescing then allows the platform uart to immediately catch up. Also added an error log message if the `task_post()` actually does fail. * Don't cache the uart delims. Doing so makes reconfiguring those settings from within the callback not take effect until the currently buffered bytes have been processed.
-
- 27 Sep, 2019 1 commit
-
-
f4grx authored
-
- 12 Aug, 2019 1 commit
-
-
Arnim Läuger authored
* fix handling of optional power pin * add init example for wESP32 * add example for eth.on()
-
- 22 Jul, 2019 1 commit
-
-
Johny Mattsson authored
* Port LFS from ESP8266 to ESP32
-
- 20 Jul, 2019 1 commit
-
-
Arnim Läuger authored
Ethernet module added.
-
- 19 Jul, 2019 1 commit
-
-
Johny Mattsson authored
* Move task_post() into IRAM so it can be used by IRAM'd ISRs. * Don't leave crud on stack on pcall error.
-
- 14 Jul, 2019 1 commit
-
-
Johny Mattsson authored
To avoid races between the lwIP callbacks (lwIP RTOS task) and the Lua handlers (LVM RTOS task), the data flow and ownership has been simplified and cleaned up. lwIP callbacks now have no visibility of the userdata struct. They are limited to creating small event objects and task_post()ing them over to the LVM "thread", passing ownership in doing so. The shared identifier then becomes the struct netconn*. On the LVM side, we keep a linked list of active userdata objects. This allows us to retrieve the correct userdata when we get an event with a netconn pointer. Because this list is only ever used within the LVM task, no locking is necessary. The old approach of stashing a userdata pointer into the 'socket' field on the netconn has been removed entirely, as this was both not thread/RTOS-task safe, and also interfered with the IDFs internal use of the socket field (even when using only the netconn layer). As an added benefit, this removed the need for all the SYS_ARCH_PROTECT() locking stuff. The need to track receive events before the corresponding userdata object has been established has been removed by virtue of not reordering the "accept" and the "recv" events any more (previously accepts were posted with medium priority, while the receives where high priority, leading to the observed reordering and associated headaches). The workaround for IDF issue 784 has been removed as it is now not needed and is in fact directly harmful as it results in a double-free. Yay for getting rid of old workarounds! DNS resolution code paths were merged for the two instances of "socket" initiated resolves (connect/dns functions). Also fixed an instance of using a stack variable for receiving the resolved IP address, with said variable going out of scope before the DNS resolution necessarily completed (hello, memory corruption!). Where possible, moved to use the Lua allocator rather than plain malloc. Finally, the NodeMCU task posting mechanism got a polish and an adjustment. Given all the Bad(tm) that tends to happen if something fails task posting, I went through a couple of iterations on how to avoid that. Alas, the preferred solution of blocking non-LVM RTOS tasks until a slot is free turned out to not be viable, as this easily resulted in deadlocks with the lwIP stack. After much deliberation I settled on increasing the number of available queue slots for the task_post() mechanism, but in the interest of user control also now made it user configurable via Kconfig.
-
- 11 Jul, 2019 1 commit
-
-
Johny Mattsson authored
The netbuf_data() function only returns data from the first pbuf in the chain. We need to use netbuf_first() and netbuf_next() to walk the pbuf chain and act on each in turn.
-
- 06 Jul, 2019 1 commit
-
-
Johny Mattsson authored
* Implemented otaupgrade module. * Added partition table example for otaupgrade. * Copy-paste omission. Whoops. * Updated otaupgrade docs after review.
-