ci: partially enable example build for esp32c2

examples/cxx/exceptions/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # Example: C++ exception handling
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/cxx/experimental/esp_event_async_cxx/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # ESP-Event asynchronous example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/cxx/experimental/esp_event_cxx/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # ESP Event synchronous example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/cxx/experimental/esp_mqtt_cxx/ssl/README.md

@@ -0,0 +1,2 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |

examples/cxx/experimental/esp_mqtt_cxx/tcp/README.md

@@ -0,0 +1,2 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |

examples/cxx/experimental/esp_timer_cxx/README.md

@@ -1,10 +1,13 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # Example: ESPTimer C++ class
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 
 This example demonstrates usage of the ESPTimer c++ class in ESP-IDF.
 
-In this example, the `sdkconfig.defaults` file sets the `CONFIG_COMPILER_CXX_EXCEPTIONS` option. 
+In this example, the `sdkconfig.defaults` file sets the `CONFIG_COMPILER_CXX_EXCEPTIONS` option.
 This enables both compile time support (`-fexceptions` compiler flag) and run-time support for C++ exception handling.
 This is necessary for the C++ APIs.
 

examples/cxx/experimental/simple_i2c_rw_example/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Example: C++ I2C sensor read for MPU9250
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/cxx/experimental/simple_spi_rw_example/README.md

@@ -1,10 +1,13 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Example: C++ SPI sensor read for MCU9250 inertial/giroscope sensor
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 
 This example demonstrates usage of C++ SPI classes in ESP-IDF to read the `WHO_AM_I` register of the sensor.
 
-In this example, the `sdkconfig.defaults` file sets the `CONFIG_COMPILER_CXX_EXCEPTIONS` option. 
+In this example, the `sdkconfig.defaults` file sets the `CONFIG_COMPILER_CXX_EXCEPTIONS` option.
 This enables both compile time support (`-fexceptions` compiler flag) and run-time support for C++ exception handling.
 This is necessary for the C++ SPI API.
 

examples/cxx/pthread/README.md

@@ -1,8 +1,11 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # C++ pthread Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 
-Support for the [C++ threads](http://www.cplusplus.com/reference/thread/thread/) in ESP-IDF is implemented on top of the [ESP-pthread](https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/system/esp_pthread.html#overview) component. Thus, C++ threads created using the standard thread class constructor will automatically inherit the current ESP-pthread configuration. This example demonstrates how to leverage the thread configuration functions provided by ESP-pthread (e.g., `esp_pthread_get_default_config()` and `esp_pthread_set_cfg()`) to modify the stack sizes, priorities, names, and core affinities of the C++ threads. 
+Support for the [C++ threads](http://www.cplusplus.com/reference/thread/thread/) in ESP-IDF is implemented on top of the [ESP-pthread](https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/system/esp_pthread.html#overview) component. Thus, C++ threads created using the standard thread class constructor will automatically inherit the current ESP-pthread configuration. This example demonstrates how to leverage the thread configuration functions provided by ESP-pthread (e.g., `esp_pthread_get_default_config()` and `esp_pthread_set_cfg()`) to modify the stack sizes, priorities, names, and core affinities of the C++ threads.
 
 **Note: Due to the use of the C++ threads, this example is written in C++ instead of C.**
 

examples/cxx/rtti/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # Example: C++ run-time type info (RTTI)
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/ethernet/basic/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Ethernet Example
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 
@@ -22,7 +25,7 @@ Besides that, `esp_eth` component can drive third-party Ethernet module which in
 The ESP-IDF supports the usage of multiple Ethernet interfaces at a time when external modules are utilized which is also demonstrated by this example. There are several options you can combine:
    * Internal EMAC and one SPI Ethernet module.
    * Two SPI Ethernet modules of the same type connected to single SPI interface and accessed by switching appropriate CS.
-   * Internal EMAC and two SPI Ethernet modules of the same type. 
+   * Internal EMAC and two SPI Ethernet modules of the same type.
 
 #### Pin Assignment
 

examples/ethernet/enc28j60/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ENC28J60 Example
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 

examples/ethernet/eth2ap/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # eth2ap Example
 (See the README.md file in the upper level 'examples' directory for more information about examples. To try a more complex application about Ethernet to WiFi data forwarding, please go to [iot-solution](https://github.com/espressif/esp-iot-solution/tree/release/v1.0/examples/eth2wifi).)
 

examples/ethernet/iperf/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Ethernet iperf Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/mesh/internal_communication/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Mesh Internal Communication Example
 
 This example demonstrates how to use the mesh APIs to set up a mesh network, send and receive messages over the mesh network and etc.

examples/mesh/ip_internal_network/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Mesh IP Internal Networking example
 
 This example demonstrates how to use mesh to create a IP capable sub-network.
@@ -6,11 +9,11 @@ and uses internal communication at the same time
 
 ## Functionality
 
-This example uses experimental NAT feature to translate addresses/ports from an internal subnet, that is created 
+This example uses experimental NAT feature to translate addresses/ports from an internal subnet, that is created
 by the root node running a DHCP server. At the same time, the nodes communicate using low level mesh send/receive
 API to exchange data, such as routing table from root to all nodes and an event notification from one node
 to all other nodes in the mesh. As a demonstration, the same event is also published at the mqtt broker
-on a subscribed topic, so both internal mesh_recv() notification as well as mqtt data event are to be received. 
+on a subscribed topic, so both internal mesh_recv() notification as well as mqtt data event are to be received.
 
 ### Hardware Required
 

examples/mesh/manual_networking/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Mesh Manual Networking Example
 
 ESP-MESH provides the function of self-organized networking, but if users disable this function on one node, users must designate a parent for this node.

examples/network/network_tests/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Intel net test suite for LwIP network stack
 
 This project provides a test interface to esp32 network stack in order to execute standard set of
@@ -46,7 +49,7 @@ Purpose of this test is to execute standard network suite on a ESP32 network sta
 DUT, Device (Network stack in this case) under test, runs normally on target, but a specific interface with configured esp-netif for passing arbitrary data to
 and from the network stack. Embedded code `net_suite.c` implements an application which serves stdin/stdout and propagates the data to/from this test interface.
 
-Standard Intel net suite executed by TTCN3 engine uses udp ports for input/ouput of network packets. Python script `net_suite.py` translates this communication 
+Standard Intel net suite executed by TTCN3 engine uses udp ports for input/ouput of network packets. Python script `net_suite.py` translates this communication
 from/to those udp ports to stdin/stdout, where after propagating over USB/UART to the ESP32 board are processed in the network stack (on the target).
 
 Actual test execution, progress, evaluation and test reporting is done using standard net-test-suite scripts running on PC.

examples/network/simple_sniffer/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Simple Sniffer Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/openthread/ot_br/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # OpenThread Border Router Example
 
 ## Overview
@@ -18,8 +21,8 @@ Connect the two SoCs via UART, below is an example setup with ESP32 DevKitC and
 
 ESP32 pin | ESP32-H2 pin
 ----------|-------------
-   GND    |      G 
-   GPIO4  |      TX      
+   GND    |      G
+   GPIO4  |      TX
    GPIO5  |      RX
 
 ### Configure the project
@@ -231,16 +234,16 @@ sudo sysctl -w net/ipv6/conf/wlan0/accept_ra_rt_info_max_plen=128
 For mobile devices, the route table rules will be automatically configured after iOS 14 and Android 8.1.
 
 
-### Testing IPv6 connectivity 
+### Testing IPv6 connectivity
 
 Now in the joining device, check the IP addresses:
 
 ```
-> ipaddr                                                              
+> ipaddr
 fde6:75ff:def4:3bc3:9e9e:3ef:4245:28b5
-fdde:ad00:beef:0:0:ff:fe00:c402                                       
+fdde:ad00:beef:0:0:ff:fe00:c402
 fdde:ad00:beef:0:ad4a:9a9a:3cd6:e423
-fe80:0:0:0:f011:2951:569e:9c4a                                        
+fe80:0:0:0:f011:2951:569e:9c4a
 ```
 
 You'll notice an IPv6 global prefix with only on address assigned under it. This is the routable address of this Thread node.
@@ -275,7 +278,7 @@ Done
 This service will also become visible on the Wi-Fi network:
 
 ```bash
-$ avahi-browse -r _test._udp -t   
+$ avahi-browse -r _test._udp -t
 
 + enp1s0 IPv6 my-service                                    _test._udp           local
 = enp1s0 IPv6 my-service                                    _test._udp           local

examples/peripherals/adc/dma_read/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ADC DMA Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/adc/single_read/single_read/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ADC Single Read Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/i2c/i2c_self_test/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # I2C Self-Test Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/i2c/i2c_simple/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # I2C Simple Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/i2c/i2c_tools/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # I2C Tools Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/i2s/i2s_es8311/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # I2S ES8311 Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/lcd/gc9a01/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # GC9A01 porting example
 
 [esp_lcd](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/lcd.html) provides several panel drivers out-of box, e.g. ST7789, SSD1306, NT35510. However, there're a lot of other panels on the market, it's beyond `esp_lcd` component's responsibility to include them all.

examples/peripherals/lcd/i2c_oled/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # I2C OLED example
 
 [esp_lcd](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/lcd.html) supports I2C interfaced OLED LCD, whose color depth is usually 1bpp.

examples/peripherals/lcd/tjpgd/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 ## LCD tjpgd example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/sigmadelta/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Sigma Delta Modulation Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -12,7 +15,7 @@ This example uses the sigma-delta driver to generate modulated output on a GPIO.
 Besides the [ESP32 development board](https://www.espressif.com/en/products/hardware/development-boards) you need a LED and a resistor to limit the LED current. Connect them as below:
 
 ```
-             330R            LED     
+             330R            LED
 GPIO4 +----/\/\/\----+------|>|-----+ GND
 ```
 

examples/peripherals/spi_master/hd_eeprom/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 ## SPI master half duplex EEPROM example
 
  This code demonstrates how to use the SPI master half duplex mode to read/write a AT93C46D

examples/peripherals/spi_slave/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 ## SPI slave example
 
 These two projects illustrate the SPI Slave driver. They're supposed to be flashed into two separate Espressif chips connected to eachother using the SPI pins defined in app_main.c. Once connected and flashed, they will use the spi master and spi slave driver to communicate with eachother. The example also includes a handshaking line to allow the master to only poll the  slave when it is actually ready to parse a transaction.

examples/peripherals/spi_slave_hd/append_mode/master/README.md

@@ -1 +1,4 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 See README.md in the parent directory

examples/peripherals/spi_slave_hd/segment_mode/seg_master/README.md

@@ -1 +1,4 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 See README.md in the parent directory

examples/peripherals/twai/twai_alert_and_recovery/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # TWAI Alert and Recovery Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/twai/twai_network/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # TWAI Network Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/peripherals/twai/twai_self_test/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # TWAI Self Test Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/protocols/asio/asio_chat/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 
 # Asio chat client and server examples
 
@@ -48,7 +51,7 @@ Set following parameters under Example Configuration Options:
 - Connect to the server using multiple clients, for example using any option below.
     - build and run asio chat client on your host machine
     - run chat_client asio example on ESP platform
-    - since chat messages consists of ASCII size and message, it is possible to 
+    - since chat messages consists of ASCII size and message, it is possible to
         netcat `nc IP PORT` and type for example ` 4ABC<CR>` to transmit 'ABC\n'
 
 ## Running the example in client mode

examples/protocols/asio/ssl_client_server/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Asio SSL client/server example
 
 Simple Asio client and server with SSL/TLS transport
@@ -13,8 +16,8 @@ to connect to internet or a local network via WiFi or Ethernet to easily exercis
 
 * Open the project configuration menu (`idf.py menuconfig`)
 * Configure Wi-Fi or Ethernet under "Example Connection Configuration" menu. See "Establishing Wi-Fi or Ethernet Connection" section in [examples/protocols/README.md](../../README.md) for more details.
-* Enable the ASIO client and set server's host name to examine client's functionality. 
-The ASIO client connects to the configured server and sends default payload string "GET / HTTP/1.1" 
+* Enable the ASIO client and set server's host name to examine client's functionality.
+The ASIO client connects to the configured server and sends default payload string "GET / HTTP/1.1"
 * Enable the ASIO server to examine server's functionality. The ASIO server listens to connection and echos back what was received.
 
 ### Build and Flash
@@ -58,7 +61,7 @@ D
 ### Both server and client enabled
 
 The below output demonstrates the client connecting to the ASIO server via loopback interface, so no WiFi, nor Ethernet connection
-was established. 
+was established.
 ```
 I (0) cpu_start: App cpu up.
 I (495) heap_init: Initializing. RAM available for dynamic allocation:

examples/protocols/asio/tcp_echo_server/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Asio TCP echo server example
 
 Simple Asio TCP echo server using WiFi STA or Ethernet.

examples/protocols/asio/udp_echo_server/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Asio UDP echo server example
 
 Simple Asio UDP echo server using WiFi STA or Ethernet.

examples/protocols/coap_client/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 
 # CoAP client example
 
@@ -18,7 +21,7 @@ If the URI is prefixed with coap+tcp://, then the CoAP will try to use TCP for t
 NOTE: coaps+tcp:// is not currently supported, even though both libcoap and MbedTLS support it.
 
 The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with
-constrained nodes and constrained networks in the Internet of Things.   
+constrained nodes and constrained networks in the Internet of Things.
 The protocol is designed for machine-to-machine (M2M) applications such as smart energy and
 building automation.
 
@@ -61,9 +64,9 @@ See the Getting Started Guide for full steps to configure and use ESP-IDF to bui
 
 ## Example Output
 Prerequisite: we startup a CoAP server on coap server example,
-or use the default of coap://californium.eclipseprojects.io.  
+or use the default of coap://californium.eclipseprojects.io.
 
-and you could receive data from CoAP server if succeed,  
+and you could receive data from CoAP server if succeed,
 such as the following log:
 
 ```

examples/protocols/coap_server/README.md

@@ -1,7 +1,10 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 
 # CoAP server example
 
-(See the README.md file in the upper level 'examples' directory for more information about examples.)  
+(See the README.md file in the upper level 'examples' directory for more information about examples.)
 This CoAP server example is very simplified adaptation of one of the
 [libcoap](https://github.com/obgm/libcoap) examples.
 
@@ -17,7 +20,7 @@ NOTE: Client sessions trying to use coaps+tcp:// are not currently supported, ev
 libcoap and MbedTLS support it.
 
 The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with
-constrained nodes and constrained networks in the Internet of Things.   
+constrained nodes and constrained networks in the Internet of Things.
 The protocol is designed for machine-to-machine (M2M) applications such as smart energy and
 building automation.
 
@@ -58,8 +61,8 @@ idf.py -p PORT flash monitor
 See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects.
 
 ## Example Output
-current CoAP server would startup a daemon task,   
-and the log is such as the following:  
+current CoAP server would startup a daemon task,
+and the log is such as the following:
 
 ```
 ...
@@ -76,7 +79,7 @@ I (2622) CoAP_server: Connected to AP
 ...
 ```
 
-If a CoAP client queries the `/Espressif` resource, CoAP server will return `"Hello World!"`  
+If a CoAP client queries the `/Espressif` resource, CoAP server will return `"Hello World!"`
 until a CoAP client does a PUT with different data.
 
 ## libcoap Documentation

examples/protocols/esp_http_client/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP HTTP Client Example
 
 See the README.md file in the upper level 'examples' directory for more information about examples.

examples/protocols/esp_local_ctrl/README.md

@@ -1,5 +1,6 @@
 | Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
 | ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP Local Control using HTTPS server
 
 This example creates a `esp_local_ctrl` service over HTTPS transport, for securely controlling the device over local network. In this case the device name is resolved through `mDNS`, which in this example is `my_esp_ctrl_device.local`.

examples/protocols/http2_request/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # HTTP/2 Request Example
 
 Establish an HTTP/2 connection with https://http2.github.io

examples/protocols/http_request/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # HTTP Request Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -72,7 +75,7 @@ Connection: close
         margin: 0;
         padding: 0;
         font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
-        
+
     }
     div {
         width: 600px;
@@ -92,7 +95,7 @@ Connection: close
             width: auto;
         }
     }
-    </style>    
+    </style>
 </head>
 
 <body>
@@ -105,7 +108,7 @@ Connection: close
 </body>
 </html>
 I (11467) example: ... done reading from socket. Last read return=0 errno=128.
-I (11477) example: 10... 
-I (12477) example: 9... 
-I (13477) example: 8... 
+I (11477) example: 10...
+I (12477) example: 9...
+I (13477) example: 8...
 ```

examples/protocols/http_server/advanced_tests/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # HTTP server advanced tests
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/protocols/http_server/captive_portal/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Captive Portal Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/protocols/http_server/file_serving/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Simple HTTP File Server Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -70,7 +73,7 @@ See the Getting Started Guide for full steps to configure and use ESP-IDF to bui
 
    The following steps assume that IP address 192.168.1.100 was assigned.
 
-2. Test the example interactively in a web browser. The default port is 80. 
+2. Test the example interactively in a web browser. The default port is 80.
 
     1. Open path http://192.168.1.100/ or http://192.168.1.100/index.html to see an HTML page with list of files on the server. The page will initially be empty.
     2. Use the file upload form on the webpage to select and upload a file to the server.

examples/protocols/http_server/persistent_sockets/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # HTTPD Server Persistent Sockets Example
 
 The Example consists of HTTPD server persistent sockets demo.

examples/protocols/http_server/restful_server/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # HTTP Restful API Server Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -57,7 +60,7 @@ Only if you deploy the website to SD card, then the following pin connection is
 
 ### Configure the project
 
-Open the project configuration menu (`idf.py menuconfig`). 
+Open the project configuration menu (`idf.py menuconfig`).
 
 In the `Example Connection Configuration` menu:
 

examples/protocols/http_server/simple/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Simple HTTPD Server Example
 
 The Example consists of HTTPD server demo with demostration of URI handling :

examples/protocols/http_server/ws_echo_server/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Websocket echo server
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -24,7 +27,7 @@ We register the URI handler with the standard API `httpd_register_uri_handler()`
 ```c
 static const httpd_uri_t ws_uri_handler_options = {
         ... // httpd options
-        
+
         .is_websocket = true,               // Mandatory: set to `true` to handler websocket protocol
         .handle_ws_control_frames = false,  // Optional: set to `true` for the handler to receive control packets, too
         .supported_subprotocol = "chat",    // Optional: set supported subprotocol for this handler

examples/protocols/icmp_echo/README.md

@@ -1,12 +1,15 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # ICMP Echo-Reply (Ping) example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 
-Ping is a useful network utility used to test if a remote host is reachable on the IP network. It measures the round-trip time for messages sent from the source host to a destination target that are echoed back to the source. 
+Ping is a useful network utility used to test if a remote host is reachable on the IP network. It measures the round-trip time for messages sent from the source host to a destination target that are echoed back to the source.
 
 Ping operates by sending Internet Control Message Protocol (ICMP) echo request packets to the target host and waiting for an ICMP echo reply.
 
-This example implements a simple ping command line util based on the [console component](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/console.html). 
+This example implements a simple ping command line util based on the [console component](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/console.html).
 
 **Notes:** Currently this example only supports IPv4.
 

examples/protocols/l2tap/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP-NETIF L2 TAP Interface Example
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 

examples/protocols/mdns/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # mDNS example
 
 Shows how to use mDNS to advertise lookup services and hosts

examples/protocols/mqtt/ssl/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP-MQTT SSL Sample application
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/protocols/mqtt/ssl_mutual_auth/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP-MQTT SSL Sample application (mutual authentication)
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/protocols/mqtt/ssl_psk/README.md

@@ -1,4 +1,7 @@
-# ESP-MQTT SSL example with PSK verification 
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
+# ESP-MQTT SSL example with PSK verification
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 
@@ -8,11 +11,11 @@ This example connects to a local broker configured to PSK authentication
 
 ### Hardware Required
 
-This example can be executed on any ESP32 board, the only required interface is WiFi (or ethernet) to connect to a MQTT 
+This example can be executed on any ESP32 board, the only required interface is WiFi (or ethernet) to connect to a MQTT
 broker with preconfigured PSK verification method.
 
 #### Mosquitto settings
-In case of using mosquitto broker, here is how to enable PSK authentication in `mosquitto.config`, 
+In case of using mosquitto broker, here is how to enable PSK authentication in `mosquitto.config`,
 ```
 psk_hint hint
 psk_file path_to_your_psk_file

examples/protocols/mqtt/tcp/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP-MQTT sample application
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 

examples/protocols/mqtt/ws/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP-MQTT MQTT over Websocket
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/protocols/mqtt/wss/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # ESP-MQTT MQTT over WSS Sample application
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 

examples/protocols/slip/slip_udp/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # SLIP device client
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/protocols/smtp_client/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # SMTP Client Example
 
 The Example is SMTP client demo. It sends and email with attachment to recipient.

examples/protocols/sockets/non_blocking/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 
 # TCP non-blocking client and server examples
 
@@ -8,7 +11,7 @@ It could be configured to run either a TCP server, or a TCP client, or both, in
 
 ## How to use example
 
-The example is configured by default as the TCP client. 
+The example is configured by default as the TCP client.
 
 Note that the example uses string representation of IP addresses and ports and thus
 could be used on both IPv4 and IPv6 protocols.

examples/protocols/sockets/tcp_client/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 
 # TCP Client example
 
@@ -9,8 +12,8 @@ The application creates a TCP socket and tries to connect to the server with pre
 
 In order to create TCP server that communicates with TCP Client example, choose one of the following options.
 
-There are many host-side tools which can be used to interact with the UDP/TCP server/client. 
-One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets. 
+There are many host-side tools which can be used to interact with the UDP/TCP server/client.
+One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets.
 Note: please replace `192.168.0.167 3333` with desired IPV4/IPV6 address (displayed in monitor console) and port number in the following command.
 
 In addition to those tools, simple Python scripts can be found under sockets/scripts directory. Every script is designed to interact with one of the examples.

examples/protocols/sockets/tcp_client_multi_net/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Multiple Ethernet Example
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
 

examples/protocols/sockets/tcp_server/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 
 # TCP Server example
 
@@ -9,8 +12,8 @@ The application creates a TCP socket with the specified port number and waits fo
 
 In order to create TCP client that communicates with TCP server example, choose one of the following options.
 
-There are many host-side tools which can be used to interact with the UDP/TCP server/client. 
-One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets. 
+There are many host-side tools which can be used to interact with the UDP/TCP server/client.
+One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets.
 Note: please replace `192.168.0.167 3333` with desired IPV4/IPV6 address (displayed in monitor console) and port number in the following command.
 
 In addition to those tools, simple Python scripts can be found under sockets/scripts directory. Every script is designed to interact with one of the examples.

examples/protocols/sockets/udp_client/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 
 # UDP Client example
 
@@ -9,8 +12,8 @@ The application creates UDP socket and sends message to the predefined port and
 
 In order to create UDP server that communicates with UDP Client example, choose one of the following options.
 
-There are many host-side tools which can be used to interact with the UDP/TCP server/client. 
-One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets. 
+There are many host-side tools which can be used to interact with the UDP/TCP server/client.
+One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets.
 Note: please replace `192.168.0.167 3333` with desired IPV4/IPV6 address (displayed in monitor console) and port number in the following commands.
 
 In addition to those tools, simple Python scripts can be found under sockets/scripts directory. Every script is designed to interact with one of the examples.

examples/protocols/sockets/udp_multicast/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # UDP Multicast Example
 
 This example shows how to use the IPV4 & IPV6 UDP multicast features via the BSD-style sockets interface.

examples/protocols/sockets/udp_server/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 
 # UDP Server example
 
@@ -9,8 +12,8 @@ The application creates UDP socket with the specified port number and waits for
 
 In order to create UDP client that communicates with UDP server example, choose one of the following options.
 
-There are many host-side tools which can be used to interact with the UDP/TCP server/client. 
-One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets. 
+There are many host-side tools which can be used to interact with the UDP/TCP server/client.
+One command line tool is [netcat](http://netcat.sourceforge.net) which can send and receive many kinds of packets.
 Note: please replace `192.168.0.167 3333` with desired IPV4/IPV6 address (displayed in monitor console) and port number in the following commands.
 If want to use this RECVINFO function, please enable LWIP_NETBUF_RECVINFO in menuconfig,this function can only resolve the destination address of IPV4.
 

examples/protocols/static_ip/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 | ESP32-C2 |
+| ----------------- | ----- | -------- | -------- | -------- | -------- |
+
 # WiFi station example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/security/flash_encryption/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Flash Encryption
 
 The example checks if the flash encryption feature is enabled/disabled and if enabled prints the flash encryption mode (DEVELOPMENT / RELEASE) and FLASH_CRYPT_CNT (for ESP32) or SPI_BOOT_CRYPT_CNT (for ESP32-S2 and newer targets) eFuse value.

examples/storage/custom_flash_driver/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Custom Flash Driver Example
 
 This example shows how to override the default chip driver list provided by IDF. Please make sure the SPI_FLASH_OVERRIDE_CHIP_DRIVER_LIST config option is enabled when you build this project (though it should already be enabled by default via `sdkconfig.defaults`). See [the programming guide](https://docs.espressif.com/projects/esp-idf/en/stable/api-reference/storage/spi_flash_override_driver.html) for more details regarding this feature.

examples/storage/ext_flash_fatfs/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # FAT FS on External Flash example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/fatfsgen/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # FATFS partition generation example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/nvs_rw_blob/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Non-Volatile Storage (NVS) Read and Write Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/nvs_rw_value/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Non-Volatile Storage (NVS) Read and Write Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/nvs_rw_value_cxx/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Non-Volatile Storage (NVS) C++ Read and Write Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/partition_api/partition_find/README.md

@@ -1,17 +1,20 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Finding Partitions Example
 
 This example demonstrates how to use the partition API functions `esp_partition_find`  and `esp_partition_find_first` to search the device partition table.
 These functions return the matching partitions given a set of constraints. By constraints we simply mean
-properties that returned results should match - notably partition type, subtype and label/name. In the case of `esp_partition_find_first`, the first matching instance is returned; 
+properties that returned results should match - notably partition type, subtype and label/name. In the case of `esp_partition_find_first`, the first matching instance is returned;
 for `esp_partition_find`, an iterator is returned iterating over matching instances.
 
 # Example Flow
 
-The example uses a [custom partition table](./partitions_example.csv). The first part uses `esp_partition_find_first` to search for partition instances 
-using two constraints - type and subtype. However, the partition table contains partitions with same type/subtype combination. In order to differentiate these partitions, 
+The example uses a [custom partition table](./partitions_example.csv). The first part uses `esp_partition_find_first` to search for partition instances
+using two constraints - type and subtype. However, the partition table contains partitions with same type/subtype combination. In order to differentiate these partitions,
 a third constraint - the label, is specified.
 
-The second part shows how to iterate over partitions that match certain constraints, manually checking the properties of each iterated partition. 
+The second part shows how to iterate over partitions that match certain constraints, manually checking the properties of each iterated partition.
 The iterator is obtained using `esp_partition_find` and is released after its use to avoid memory leaks.
 
 ### Output

examples/storage/partition_api/partition_mmap/README.md

@@ -1,13 +1,16 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Partition Memory Map Example
 
-This example demonstrates how to use `esp_partition_mmap` to configure MMU and map a partition into memory address space for read operations. 
+This example demonstrates how to use `esp_partition_mmap` to configure MMU and map a partition into memory address space for read operations.
 
 # Example Flow
 
-The example uses a [custom partition table](./partitions_example.csv), with a data partition `storage` used for demonstration. Before mapping this partition to memory, 
+The example uses a [custom partition table](./partitions_example.csv), with a data partition `storage` used for demonstration. Before mapping this partition to memory,
 data is written to the partition used for verification.
 
-The partition API function `esp_partition_mmap` is used to get a pointer to the mapped memory region and a handle to the mapping. The pointer is used to transparently read back the 
+The partition API function `esp_partition_mmap` is used to get a pointer to the mapped memory region and a handle to the mapping. The pointer is used to transparently read back the
 verification data written previously. Once the data written and read are verified to be the same, the function `spi_flash_munmap` is used to release the mapping.
 
 ### Output

examples/storage/partition_api/partition_ops/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Partition Read, Write, Erase Example
 
 This example demonstrates how to perform partition read, write and erase operations using API functions `esp_partition_read`, `esp_partition_write` and `esp_partition_erase`.
@@ -7,7 +10,7 @@ This example demonstrates how to perform partition read, write and erase operati
 The example uses a [custom partition table](./partitions_example.csv), with a data partition `storage` used as the demo partition. For the most part the example code is well-commented so users should be able to follow along the code easily. Nevertheless, this section provides an overview of the code flow.
 
 The partition table is searched for the `storage` partition. Once found, the entire partition is erased using `esp_partition_erase_range`. Sample data is written using `esp_partition_write`
-and read back using `esp_partition_read`, verifying the read and written data match. The partition is erased once again using `esp_partition_erase_range`, limited to the sector the sample data was written to. 
+and read back using `esp_partition_read`, verifying the read and written data match. The partition is erased once again using `esp_partition_erase_range`, limited to the sector the sample data was written to.
 
 ### Output
 

examples/storage/parttool/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Partitions Tool Example
 
 This example demonstrates common operations the partitions tool [parttool.py](../../../components/partition_table/parttool.py) allows the user to perform:

examples/storage/sd_card/sdspi/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # SD Card example (SDSPI)
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/semihost_vfs/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Semihosting VFS driver example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -101,9 +104,9 @@ There are two outputs produced by example:
    but they're the best we can do in text.  A graphics file illustrating
    the character set should be available from the same archive as this
    file.
-   
+
    Hex Description                 Hex Description
-   
+
    20  SPACE
    ...
    7D  RIGHT CURLY BRACKET         FD  SMALL LETTER Y WITH ACUTE

examples/storage/spiffs/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # SPIFFS example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/spiffsgen/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # SPIFFS Image Generation on Build Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/storage/wear_levelling/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Wear levelling example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -36,7 +39,7 @@ See the Getting Started Guide for full steps to configure and use ESP-IDF to bui
 
 ## Example output
 
-Here is a typical example console output. 
+Here is a typical example console output.
 
 ```
 I (280) example: Mounting FAT filesystem

examples/system/base_mac_address/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Base MAC Address
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/system/console/advanced/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Console Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -36,7 +39,7 @@ See the Getting Started Guide for full steps to configure and use ESP-IDF to bui
 
 ## Example Output
 
-Enter the `help` command get a full list of all available commands. The following is a sample session of the Console Example where a variety of commands provided by the Console Example are used. Note that GPIO15 is connected to GND to remove the boot log output. 
+Enter the `help` command get a full list of all available commands. The following is a sample session of the Console Example where a variety of commands provided by the Console Example are used. Note that GPIO15 is connected to GND to remove the boot log output.
 
 ```
 This is an example of ESP-IDF console component.
@@ -44,13 +47,13 @@ Type 'help' to get the list of commands.
 Use UP/DOWN arrows to navigate through command history.
 Press TAB when typing command name to auto-complete.
 [esp32]> help
-help 
+help
   Print the list of registered commands
 
-free 
+free
   Get the total size of heap memory available
 
-restart 
+restart
   Restart the program
 
 deep_sleep  [-t <t>] [--io=<n>] [--io_level=<0|1>]
@@ -99,7 +102,7 @@ This is an example of ESP-IDF console component.
 Type 'help' to get the list of commands.
 Use UP/DOWN arrows to navigate through command history.
 Press TAB when typing command name to auto-complete.
-[esp32]> 
+[esp32]>
 
 ```
 
@@ -124,7 +127,7 @@ esp32>
 
 ### Configuring UART
 
-The ``initialize_console()`` function in the example configures some aspects of UART relevant to the operation of the console. 
+The ``initialize_console()`` function in the example configures some aspects of UART relevant to the operation of the console.
 
 - **Line Endings**: The default line endings are configured to match those expected/generated by common serial monitor programs, such as `screen`, `minicom`, and the `idf_monitor.py` included in the SDK. The default behavior for these commands are:
     - When 'enter' key is pressed on the keyboard, `CR` (0x13) code is sent to the serial device.

examples/system/console/basic/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Basic Console Example (`esp_console_repl`)
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -70,13 +73,13 @@ Type 'help' to get the list of commands.
 Use UP/DOWN arrows to navigate through command history.
 Press TAB when typing command name to auto-complete.
 [esp32]> help
-help 
+help
   Print the list of registered commands
 
-free 
+free
   Get the total size of heap memory available
 
-restart 
+restart
   Restart the program
 
 deep_sleep  [-t <t>] [--io=<n>] [--io_level=<0|1>]
@@ -125,7 +128,7 @@ This is an example of ESP-IDF console component.
 Type 'help' to get the list of commands.
 Use UP/DOWN arrows to navigate through command history.
 Press TAB when typing command name to auto-complete.
-[esp32]> 
+[esp32]>
 
 ```
 

examples/system/efuse/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # eFuse Example
 
 ## Overview

examples/system/esp_event/default_event_loop/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Default Event Loop Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)
@@ -101,12 +104,12 @@ I (3398) default_event_loop: TASK_EVENTS:TASK_ITERATION_EVENT: deleting task eve
 
 ### Setting of Event Sources
 
-This example uses two event sources: 
+This example uses two event sources:
 
 - A periodic timer. An event is raised when (1) the timer is started (2) the timer period expires and (3) the timer is stopped
 - A task with a loop inside. An event is raised for the when (1) the loop iterates.
 
-All of the events mentioned above have their own specific handler, however there are the following additional handlers. 
+All of the events mentioned above have their own specific handler, however there are the following additional handlers.
 
 - One handler executes when **any** event under the periodic timer event is posted
 - The other handler executes if **any** event is posted.

examples/system/esp_event/user_event_loops/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # User Event Loops Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/system/eventfd/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # eventfd example
 
 The example demonstrates the use of `eventfd()` to collect events from other tasks and ISRs in a

examples/system/freertos/real_time_stats/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # FreeRTOS Real Time Stats Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)

examples/system/gdbstub/README.md

@@ -1,24 +1,27 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # GDBstub example
 
-This example shows how to use gdbstub and it's functionality at runtime to debug an application with GDB. 
-With the gdbstub component it is possible to run GDB from IDF Monitor by pressing Ctrl+C and debug  
-the application using GDB. It is also possible to read/modify memory values, interrupt and continue 
+This example shows how to use gdbstub and it's functionality at runtime to debug an application with GDB.
+With the gdbstub component it is possible to run GDB from IDF Monitor by pressing Ctrl+C and debug
+the application using GDB. It is also possible to read/modify memory values, interrupt and continue
 the application, set breakpoints, make steps and so on.
 Upon exit from GDB, the application will continue to work in IDF Monitor as before.
 
 ## How to use example
 ### Hardware Required
 
-The example can run on any commonly available ESP32 development board.  
+The example can run on any commonly available ESP32 development board.
 There are two possible ways to execute gdbstub with GDB: from IDF Monitor and as standalone application.
-gdbstub support ESP32, ESP32-S2 and ESP32-S3 chips. 
+gdbstub support ESP32, ESP32-S2 and ESP32-S3 chips.
 
 ### Configure the project
 
 By default, the example is already pre-configured, but the user can change configuration options with the following command:
 ```
 idf.py menuconfig
-``` 
+```
 Current example is pre-configured. The user can scroll through the system parameters and see the settings.
 Most important one is:
 -> Component Config -> ESP System Settings -> Panic handler behaviour -> GDBStub on runtime
@@ -46,16 +49,16 @@ This will execute GDB and GDB will connect to your Esp32 by serial port COM10 wi
 
 ## Example Output
 
-The example demonstrates how to switch to GDB, watch values, change values, continue to run, and exit from GDB to the application.  
+The example demonstrates how to switch to GDB, watch values, change values, continue to run, and exit from GDB to the application.
 To switch to GDB, the user presses Ctrl+C. This will stop the application and run the GDB.
 In GDB, the user can print values "print call_count" and "print update_log_level" and then
 change them  "set call_count 100" and "set update_log_level = ESP_LOG_WARN".
 The user can continue running the application in GDB by entering "continue" and then interrupt the application by pressing Ctrl+C.
 The user can check again that the application has worked by checking variable "print call_count".
-The user can exit from GDB to continue seeing the trace from IDF Monitor by pressing "quit" and then "y".  
+The user can exit from GDB to continue seeing the trace from IDF Monitor by pressing "quit" and then "y".
 The user will see in IDF Monitor that call_count and logging level have changed.
 The user can add breakpoint to the label test_point2 by entering "break test_point2" and then enter "continue" or "c". The application will break at this line.
-If user will continue again, the application will break at this line again. 
+If user will continue again, the application will break at this line again.
 Also, user can try to step application by entering "si".
 A typical console output for such a scenario is shown below:
 ```
@@ -160,7 +163,7 @@ task4test (param=0x0) at ../main/gdbstub_main.c:38
 To reproduce this scenario run the application by: idf.py -P PORT flash monitor
 Then:
 1. Interrupt the application by pressing Ctrl+C
-2. In GDB, print the application values by typing in GDB command line "print call_count" or "print update_log_level"  
+2. In GDB, print the application values by typing in GDB command line "print call_count" or "print update_log_level"
 3. Modify the application values by typing in GDB command line "set call_count = 100" or "set update_log_level = ESP_LOG_WARN"
 4. Continue the application by typing in GDB command line "continue"
 5. Interrupt application by pressing Ctrl+C
@@ -170,7 +173,7 @@ Then:
 9. Add breakpoint by typing in GDB command line "break test_point2" or break 40 (break at line 40).
 10. Continue the application by typing in GDB command line "continue"
 11. After application stop at label "test_point2".
-12. Make stepping by typing "si" 
+12. Make stepping by typing "si"
 13. To exit from GDB to monitor type "exit" and press "y"
 
 To exit from monitor please use Ctrl+]

examples/system/heap_task_tracking/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Heap Task Tracking Example
 
 ## Overview

examples/system/light_sleep/README.md

@@ -1,3 +1,6 @@
+| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
+| ----------------- | ----- | -------- | -------- | -------- |
+
 # Light Sleep Example
 
 (See the README.md file in the upper level 'examples' directory for more information about examples.)