- Demonstrate the ESP32-S2's human-computer interaction functionalities
- Provide the users with the tools for development of human-computer interaction applications based on the ESP32-S2
There are many ways of how the ESP32-S2's abundant functionalities can be used. For starters, the possible use cases may include:
-**Smart home**: From simplest smart lighting, smart door locks, smart sockets, to video streaming devices, security cameras, OTT devices, and home appliances
-:doc:`user-guide-esp-lyrap-cam-v1.1` - camera board
Due to the presence of multiplexed pins on ESP32-S2, certain extension board combinations have limited compatibility. For more details, please see :ref:`user-guide-esp32-s2-kaluga-1-kit-ext-board-compatibility`.
This document is **mostly dedicated to the main board** and its interaction with the extension boards. For more detailed information on each extension board, click their respective links.
This guide covers:
-`Getting Started`_: Provides an overview of the ESP32-S2-Kaluga-1 and hardware/software setup instructions to get started.
-`Hardware reference`_: Provides more detailed information about the ESP32-S2-Kaluga-1's hardware.
-`Hardware Revision Details`_: Covers revision history, known issues, and links to user guides for previous versions of the ESP32-S2-Kaluga-1.
-`Related Documents`_: Gives links to related documentation.
Getting Started
===============
This section describes how to get started with the ESP32-S2-Kaluga-1. It begins with a few introductory sections about the ESP32-S2-Kaluga-1, then Section `Start Application Development`_ provides instructions on how to do the initial hardware setup and then how to flash firmware onto the ESP32-S2-Kaluga-1.
Overview
--------
The ESP32-S2-Kaluga-1 main board is the heart of the kit. It integrates the ESP32-S2-WROVER module and all the connectors for extension boards. This board is the key tool in prototyping human-computer interaction interfaces.
* Water rejection, ESP32-S2 can be configured to disable all touchpads automatically if multiple pads are simultaneously covered with water and to re-enable touchpads if the water is removed
- Switch to ON to enable connection between ESP32-S2 and FT2232; JTAG debugging will then be possible using USB-UART/JTAG Port. See also :doc:`../../api-guides/jtag-debugging/index`.
Please proceed to :doc:`../../get-started/index`, where Section :ref:`get-started-step-by-step` will quickly help you set up the development environment.
The programming guide and application examples for your ESP32-S2-Kaluga-1 kit can be found in `esp-dev-kits <https://github.com/espressif/esp-dev-kits/tree/master/esp32-s2-kaluga-1>`_ repository on GitHub.
If you want to use more than one extension board at the same time, please check the table given below.
..list-table::
:widths:20 15 33 32
:header-rows:1
* - Boards Used
- HW Conflict
- Limitations
- Solution
* - 8311A v1.3 + CAM v1.1
- I2S Controller
- ESP32-S2 has only one I2S interface. But both extension boards require connection via the ESP32-S2's I2S interface (LyraT-8311A in Standard mode, ESP-LyraP-CAM in Camera mode).
- Utilize time division multiple access, or use a different audio module that can be connected via other GPIOs or DAC.
- Touch actions cannot be triggered because of the multiplexed pin IO11. ESP-LyraP-LCD32 will not be affected because its BLCT pin will be disconnected from IO6.
- Do not initialize IO11 (NETWORK) for your ESP-LyraP-TouchA, or configure the BLCT pin to `-1` (= do not use BLCT) for your ESP-LyraP-LCD32.
* - 8311A v1.3 + LCD32 v1.2
- IO6
- BLCT pin of ESP32-S2-Kaluga-1 will be disconnected from IO6.
- Configure the BK pin to `-1` (= do not use BLCT) for your ESP-LyraP-LCD32.
* - TouchA v1.1 + 8311A v1.3
- Pin BT_ADC on ESP-LyraT-8311A
- This pin is required for initialization of the six button on ESP-LyraT-8311A. At the same time, ESP-LyraP-TouchA needs this pin for its touch actions.
- If you plan to use buttons on ESP-LyraT-8311A, do not initialize pin IO6 (PHOTO) for your ESP-LyraP-TouchA.
* - TouchA v1.1 + CAM v1.1
- IO1, IO2, IO3
- Cannot be used simultaneously because of the mentioned multiplexed pins.
- For ESP-LyraP-TouchA, do not initialize IO1 (VOL_UP), IO2 (PLAY), and IO3 (VOL_DOWN).
* - TouchA v1.1 + LCD32 v1.2 + CAM v1.1
- IO1, IO2, IO3, IO11
- Conflicts on the mentioned multiplexed pins.
- For ESP-LyraP-TouchA, do not initialize IO1 (VOL_UP), IO2 (PLAY), IO3 (VOL_DOWN), and IO11 (NETWORK).
* - TouchA v1.1 + LCD32 v1.2 + 8311A v1.3
- IO6, IO11
- If ESP-LyraT-8311A's pin BT_ADC is used to initialize the board's six buttons, IO6 and IO11 will not be available for the other boards.
- Do not initialize IO11 (NETWORK) for your ESP-LyraP-TouchA. Also, if you need to use BT_ADC, do not initialize IO6 (PHOTO).
Also, all extension boards and the :ref:`JTAG interface <jtag-debugging-tip-jtag-pins-reconfigured>` share the same pins IO39, IO40, IO41 and IO42. For this reason, the following may disturb the JTAG operation:
* Plugging in any extension board
* Debugging an application that is using an extension board
