- 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.
-
- 27 Apr, 2021 1 commit
-
-
serg3295 authored
-
- 11 Feb, 2020 1 commit
-
-
Marcel Stör authored
-
- 13 Jan, 2019 1 commit
-
-
Marcel Stör authored
Drop support for localized content, #2213 Restructure some content to match more closely what we have in master, #2542
-
- 24 Apr, 2017 1 commit
-
-
zelll authored
* added adc extension * add adc_number, for adc2
-
- 21 Sep, 2016 1 commit
-
-
Johny Mattsson authored
Heading towards having only ESP32-aware/capable code in this branch.
-
- 18 May, 2016 2 commits
-
-
Marcel Stör authored
-
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.
-
- 06 Mar, 2016 1 commit
-
-
Marcel Stör authored
-
- 08 Jan, 2016 2 commits
-
-
Marcel Stör authored
-
Marcel Stör authored
-
- 05 Jan, 2016 1 commit
-
-
Johny Mattsson authored
-