- 21 May, 2024 1 commit
-
-
Jade Mattsson authored
With the switch to use the IDF's stdin for feeding the Lua VM, we unintentionally lost the ability to use uart.on('data') on the console uart. This is since we no longer install the nodemcu uart driver on said uart. In order to resolve this shortcoming, this commit refactors the uart.on('data') delimiter handling and moves it away from platform.c into uart.c where it really belongs. A new function, uart_feed_data(), is introduced, which is used both by the nodemcu uart driver task as well as the nodemcu console driver task (assuming the console is in fact a uart). The linebuffer allocation/freeing is still in response to uart.start()/uart.stop(), but it is now in uart.c rather than platform.c. The whole uart integration is still too tightly coupled between the platform component and the module component's uart.c, but this makes it slightly better at least.
-
- 26 Apr, 2024 1 commit
-
-
Jade Mattsson authored
* Proof-of-concept multi-type console support via stdio * Address crashes on linput's use of printf. On an empty line input, a C3 with UART console would panic while attempting to output the new Lua prompt. The backtrace shows a xQueueSemaphoreTake with uxItemSize==0 as the panic cause, deep inside the uart driver, invoked via vfs_uart and vfs_console layers, from printf. Similarly, the printf for outputting a backspace/erase sequence would also trigger a panic. This workaround (of not mixing fflush() with printf) is likely merely hiding a deeper issue, but it appears to be consistent. Plus, printf with no args and a user-supplied format string is a no-no and should be fixed anyway. * Work around IDF inconsistency with stdout buffering. * Increase console task stack size. Seems on Xtensa it ended up not being enough. * Switch to single-byte console reads. * Stop cheating and feed Lua from the right context. * Work around IDF buffering stdout even when told not to, on ACM consoles. * Initial build support for esp32c6. Plus fixup of module selection for a variety of targets. * Update github actions to node 20 versions. * Update github build to deal with Lua 5.3 being default. * Address fatal compiler warning. Newer IDF toolchain is stricter, and we'd apparently failed to build test the Lua-5.1 path for some time. * Initial build support for esp32h2. * Upgrade IDF to v5.1.3 * Fix left-over incorrect type in uzlib. * Avoid null pointer crashes when debugging startup. * Workaround for using wifi module on S2 with USB-CDC console. --------- Co-authored-by:
Jade Mattsson <github@frozenlogic.org>
-
- 07 Feb, 2024 1 commit
-
-
Christoph Thelen authored
* Choose the number of RMT buffers in the ws2812 module. The number of buffers required for optimal operation should be selected by the ws2812 module, not the caller. * Add parameters for RGB LED bit times. This patch adds compatibility for different RGB LEDS besides the WS2812. ESP evaluation boards like the ESP32-C3-DevKitM-1 use an SK68XXMINI-HS RGB LED which does not respond to the timings of this module. The patch adds optional parameters for the bit timings to the write function. If the new parameters are not supplied, the old values are used. An example for the SK68XXMINI-HS is provided in the documentation. * Remove restrictions from RTM translator. The old RMT translator was not able to split the bits of the source data into the size requested by the RMT transmitter. Either all 8 bits of an input byte were translated or none. The new routine removes the restriction by delivering exactly the requested amount of data to the transmitter, which results in a more balanced buffering of translated data under load. * Add a parameter for the RGB LED reset time. This patch introduces a new optional parameter for the reset time in the RGB LED communication. The default is 51.2 microseconds. A value of 0 sends no reset signal, which allows a small optimisation for consecutive write commands. Please note that the reset time of the old code should be 50 microseconds, as the define WS2812_DURATION_RESET suggested. Due to the restrictions of the old RMT translator routine, it was slightly increased to 51.2 microseconds. This patch keeps the value of 51.2 microseconds to be as compatible as possible. * Minimize the time drift between RMT channels. Place all RMT channels in a group to minimize the time drift between the signals. Please note that this feature is not available on all platforms. * Fix the description of the SK6812 LED in the example code. The SK6812 expects the data for the green LED first, then red and finally blue. It should be described as a GRB LED.
-
- 30 Jan, 2024 1 commit
-
-
Johny Mattsson authored
Plenty of dependency adjustments, printf format specificier updates, FreeRTOS type and macro name modernisation, not to mention API changes. Still plenty of legacy/deprecated drivers in use which will need updating. The following features have been removed due to no longer being available from the IDF: - ADC hall effect sensor reading - Configuration of SD SPI host via sdmmc module (now must be done first via the spimaster module) - FAT partition selection on external SD cards; only the first FAT partition is supported by the IDF now On the other hand, the eth module now supports the following new chipsets: - KSZ8001 - KSZ8021 - KSZ8031 - KSZ8051 - KSZ8061 - KSZ8091 - Possibly additional models in the LAN87xx series (the IDF docs aren't clear on precisely which models are handled) Further, the sdmmc module is now available on the ESP32-S3 as well.
-
- 13 May, 2023 2 commits
-
-
Tom Sutcliffe authored
By not relying on ifdefing for specific targets, but instead using the SOC_RMT_xxx macros to figure it out.
-
Tom Sutcliffe authored
By not relying on the internal details of the RMT registers. For example on the esp32s2, the threshold event bits start at bit 12 not bit 24, and on the esp32s3 the memory buffers are only 48 words not 64. Also the esp-idf recommends against hooking the rmt ISR in the first place. Instead, use the published rmt APIs (specifically rmt_write_sample and rmt_translator_init) and the default rmt ISR, which should be much more resilient against future esp32 SoC changes.
-
- 12 Oct, 2022 1 commit
-
-
Johny Mattsson authored
Slightly reworked embed_lfs.sh to better cope with attribute size changes in future compiler versions, without needing to be updated again. RMT register naming changed once again...
-
- 30 Aug, 2022 1 commit
-
-
Joo Aun Saw authored
-
- 29 Aug, 2022 2 commits
-
-
Joo Aun Saw authored
-
Joo Aun Saw authored
-
- 04 Jun, 2022 1 commit
-
-
h2zero authored
If this variable is not set in the config it may contain random data and set the clock source to the REF_CLK resulting in timing errors, the DHTx, DS18B20 and ws2812 devices to not communicate.
-
- 26 Jan, 2022 1 commit
-
-
Johny Mattsson authored
Also corrects assumption about number of UARTs available.
-
- 07 Jan, 2022 1 commit
-
-
Christoph Thelen authored
* Consider RMT channel limitations at allocation time. The ESP32-C3 is limited to TX on channel 0-1 and RX on channel 2-3.
-
- 04 Nov, 2021 1 commit
-
-
Bernd Meyer authored
-
- 20 Oct, 2021 1 commit
-
-
Johny Mattsson authored
The IDF-provided VFS resolves several issues: - The IDF components having a different view of the (virtual) file system compared to the Lua environment. - RTOS task/thread safety. Our legacy VFS was only ever safe to use from the LVM thread, which limited its usability. Upgrading it would have effectively required a reimplementation of the IDF VFS, which would have been a bigger task with larger on-going maintenance issues. - We're no longer needing to maintain our own SPIFFS component. - We're no longer needing to maintain our own FATFS component. - The legacy of the 8266's lack of standard C interface to the file system is no longer holding us back, meaning that we can use the standard Lua `io` module rather than the cobbled-together swiss army knife also known as the file module. Of course, the downside is that we'll either have to declare a backwards breakage in regard to the file module, or provide a Lua shim for the old functions, where applicable. Also included is some necessary integer type fixups in unrelated code, which apparently had depended on some non-standard types in either the SPIFFS or FATFS headers. A memory leak issue in the sdmmc module was also found and fixed while said module got switched over to the Espressif VFS. Module documentation has been updated to match the new reality (and I discovered in some places it wasn't even matching the old reality).
-
- 24 Aug, 2021 1 commit
-
-
Johny Mattsson authored
-
- 23 Aug, 2021 1 commit
-
-
Johny Mattsson authored
The IDF provides all we need these days, and the old driver was just needlessly conflicting with the IDF settings and setup. This also simplifies our uart input path as we no longer need to duplicate the raw byte handling for when "run_input" is false.
-
- 22 Aug, 2021 1 commit
-
-
Johny Mattsson authored
-
- 21 Aug, 2021 1 commit
-
-
Johny Mattsson authored
Changes have been kept to a minimum, but a serious chunk of work was needed to move from 8266isms to IDFisms. Some things got refactored into components/lua/common, in particular the LFS location awareness. As part of this work I also evicted our partition table manipulation code, as with the current IDF it kept breaking checksums and rendering things unbootable, which is the opposite of helpful (which was the original intent behind it). The uart module got relocated from base_nodemcu to the modules component properly, after I worked out how to force its inclusion using Kconfig alone.
-
- 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.
-
- 29 Jul, 2021 1 commit
-
-
Johny Mattsson authored
I2S constants have changed; docs updated.
-
- 15 Jul, 2021 1 commit
-
-
Johny Mattsson authored
Yet to come: - part 2: dealing with deprecated and removed APIs - part 3: making it actually work again
-
- 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
-
- 29 Oct, 2019 1 commit
-
-
f4grx authored
Fixes #2933
-
- 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.
-
- 22 Jul, 2019 1 commit
-
-
Johny Mattsson authored
* Port LFS from ESP8266 to ESP32
-
- 31 May, 2019 1 commit
-
-
devsaurus authored
remove ESP_INTR_FLAG_IRAM to fix #2564
-
- 28 Apr, 2019 1 commit
-
-
devsaurus authored
- new displays - binding for updateDisplay() and updateDisplayArea() - use user_ptr instead of hal workaround
-
- 29 Jan, 2019 1 commit
-
-
Javier Peletier authored
-
- 17 Jan, 2019 1 commit
-
-
devsaurus authored
-
- 30 Nov, 2018 1 commit
-
-
Skirmantas Lauzikas authored
* ESP32: add support for RS485 This commit adds support for switching UART mode to RS485/IRDA. Also included are patches for memory leaks then handling UART events other than data. * ESP32: Documentation for uart.setmode()
-
- 23 Nov, 2018 1 commit
-
-
Arnim Läuger authored
-
- 04 Nov, 2018 1 commit
-
-
devsaurus authored
- implement file.size for spiffs (#1516) - fix vfs_lseek() result checking in enduser_setup and clarify SPIFFS_lseek() return value (#1570) - Handle error condition in file.read() (#1599)
-
- 03 Nov, 2018 1 commit
-
-
devsaurus authored
-
- 07 Oct, 2018 2 commits
- 15 Apr, 2018 1 commit
-
-
devsaurus authored
-
- 04 Apr, 2018 1 commit
-
-
devsaurus authored
-
- 02 Apr, 2018 1 commit
-
-
devsaurus authored
-