- 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.
-
- 26 Jan, 2022 1 commit
-
-
Johny Mattsson authored
Also corrects assumption about number of UARTs available.
-
- 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).
-
- 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.
-
- 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.
-
- 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
-
- 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
-
- 29 Jan, 2019 1 commit
-
-
Javier Peletier 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()
-
- 20 Jun, 2017 1 commit
-
-
devsaurus authored
-
- 13 Jun, 2017 1 commit
-
-
zelll authored
* uart 1/2 * call -> pcall in uart_on_* functions * fix docs * fixed console driver when using custom console uart * fixed line_inverse and error callback * fixed a crash when uart.start() called more than one time
-
- 24 Apr, 2017 1 commit
-
-
zelll authored
* added adc extension * add adc_number, for adc2
-
- 18 Apr, 2017 1 commit
-
-
devsaurus authored
-
- 14 Apr, 2017 2 commits
- 01 Apr, 2017 1 commit
-
-
devsaurus authored
-
- 17 Mar, 2017 1 commit
-
-
devsaurus authored
-
- 04 Feb, 2017 1 commit
-
-
devsaurus authored
-
- 02 Feb, 2017 1 commit
-
-
devsaurus authored
-
- 13 Jan, 2017 1 commit
-
-
devsaurus authored
-
- 22 Sep, 2016 3 commits
-
-
Johny Mattsson authored
The heuristics could probably be improved a lot, but this is better than nothing at least.
-
Johny Mattsson authored
Now uses the designated partition (type 0xC2, 0x00) unconditionally.
-
Johny Mattsson authored
-
- 21 Sep, 2016 1 commit
-
-
Johny Mattsson authored
Also included the recent LVM fix. Platform flash layer not yet functional.
-
- 20 Sep, 2016 1 commit
-
-
Johny Mattsson authored
RTOS driver evicted as it did not play nice with stdio etc. Implemented a minimal driver to fully support Lua console on UART0. Output on UART0 done via stdout (provided by the IDF). Input and setup handled via driver_console/console.c. In addition to the direct input function console_getc(), the driver also registers in the syscall tables to enable regular stdio input functions to work (yay!). The Lua VM is still using the direct interface since it's less overhead, but does also work when going through stdin/fd 0. Auto-bauding on the console is not yet functional; revisit when the UART docs are available. Module registration/linking/enabling moved over to be Kconfig based. See updates to base_nodemcu/include/module.h and base_nodemcu/Kconfig for details. The sdk-overrides directory/approach is no longer used. The IDF is simply too different to the old RTOS SDK - we need to adapt our code directly instead. Everything in app/ is now unused, and will need to be gradually migrated into components/ though it is probably better to migrate straight from the latest dev branch.
-
- 16 Sep, 2016 1 commit
-
-
Johny Mattsson authored
Currently the UART driver break boot (or at least output).
-