mirror of
https://github.com/letscontrolit/ESPEasy.git
synced 2026-07-27 19:57:38 +00:00
104 lines
3.5 KiB
ReStructuredText
104 lines
3.5 KiB
ReStructuredText
.. _Hardware_page:
|
|
|
|
Hardware page
|
|
*************
|
|
|
|
|
|
ESPEasy has some centralized hardware configuration settings, shown in this page, and divided in sections.
|
|
|
|
|
|
---------------
|
|
Wifi Status LED
|
|
---------------
|
|
|
|
To display the Wifi acitivity, a pin can be configured to light up a LED when data is transfered via Wifi. Optionally, the LED signal can be 'inverted'.
|
|
|
|
As many ESP boards have an onboard LED connected to GPIO-2 and inverted, it is shown as a note how to configure that.
|
|
|
|
.. image:: Hardware_Wifistatusled.png
|
|
|
|
|
|
---------
|
|
Reset pin
|
|
---------
|
|
|
|
To provide a possible escape from a malfunctioning ESP module, a factory-reset button/feature can be configured by setting up a GPIO-pin for this.
|
|
|
|
.. warning::
|
|
**When connecting this pin to ground for ca. 10 seconds the unit will be completely reset, and all settings/configuration irretrievably deleted!**
|
|
|
|
This feature can be useful in a development/laboratory environment, for when the configuration gets corrupted in some way.
|
|
|
|
|
|
.. image:: Hardware_Resetpin.png
|
|
|
|
|
|
|
|
--------------------
|
|
PCF & MCP Direct I/O
|
|
--------------------
|
|
|
|
Added: 2025-02-02
|
|
|
|
For interacting with the PCF8574 or MCP23017 GPIO Extenders no Device Task is required, so no I2C Bus configuration is available.
|
|
|
|
When multiple I2C Buses are configured (ESP32 only), we need some configuration to overcome that situation, to avoid having to connect these I/O extenders on the first I2C Bus.
|
|
|
|
.. image:: Hardware_PCFMCP_I2CSelector.png
|
|
|
|
When using multiple PCF and/or MCP GPIO extenders, they must all be connected to this I2C Bus, and any Device Tasks should also use the same I2C Bus.
|
|
|
|
NB: If only 1 I2C Bus is configured, this section isn't shown.
|
|
|
|
|
|
-------
|
|
SD Card
|
|
-------
|
|
|
|
When the compile-time option for SD-card support is enabled, the ``CS`` pin for the SD-card interface can be configured here. For the SD-card interface to work, **Init SPI** should also be enabled.
|
|
|
|
.. image:: Hardware_SDCard.png
|
|
|
|
|
|
-------------------
|
|
GPIO boot states
|
|
-------------------
|
|
|
|
For some GPIO pins, the boot state (initial configuration after startup) can be configured.
|
|
|
|
Some differences exist between ESP8266 and ESP32:
|
|
|
|
* ESP8266 can't initialize GPIO's 6, 7, 8, 9 and 11 (used for flash-chip by ESP8266 chip).
|
|
* ESP8285 can't initialize GPIO's 6, 7, 8 and 11 (used by flash of ESP8285 chip).
|
|
* ESP32 / ESP32-S2 can't initialize all GPIO's, only GPIO pins that are actually available for use are shown.
|
|
|
|
*ESP8266 GPIO boot states:*
|
|
|
|
.. image:: Hardware_GPIObootstatesESP8266.png
|
|
|
|
*ESP32 GPIO boot states:*
|
|
|
|
.. image:: Hardware_GPIObootstatesESP32.png
|
|
|
|
(Besides the serial pins, also I2C and SPI are configured)
|
|
|
|
If the board supports PSRAM, it has these differences:
|
|
|
|
.. image:: Hardware_GPIObootstatesESP32-PSRAM.png
|
|
|
|
Overview of the GPIO pin mapping of ESP32 (link to Espressif documentation): `ESP32 DevKitC <https://docs.espressif.com/projects/esp-idf/en/latest/esp32/_images/esp32-devkitC-v4-pinout.png>`_
|
|
|
|
*ESP32-S2 GPIO boot states:*
|
|
|
|
.. image:: Hardware_GPIObootstatesESP32-S2.png
|
|
|
|
(Only the serial port logging is enabled on this unit, no SPI or I2C)
|
|
|
|
If the board supports PSRAM, it hides GPIO-26
|
|
|
|
.. image:: Hardware_GPIObootstatesESP32-S2-PSRAM.png
|
|
|
|
(GPIO-26 is missing from the range, as it can not be used if PSRAM is present)
|
|
|
|
Overview of the GPIO pin mapping of ESP32-S2 (link to Espressif documentation): `ESP32-S2 Saola1 <https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/_images/esp32-s2_saola1-pinout.jpg>`_
|