Merge branch 'master' into esp-idf-v5.1-libs

Author: me-no-dev

.github/ISSUE_TEMPLATE/Issue-report.yml

@@ -41,6 +41,9 @@ body:
       options:
         - latest master (checkout manually)
         - latest development Release Candidate (RC-X)
+        - v2.0.14
+        - v2.0.13
+        - v2.0.12
         - v2.0.11
         - v2.0.10
         - v2.0.9

boards.txt

@@ -456,6 +456,8 @@ void HardwareSerial::end(bool fullyTerminate)
       // do not invalidate callbacks, detach pins, invalidate DBG output
       uart_driver_delete(_uart_nr);
     }
+
+    uartEnd(_uart);
     _uart = 0;
     _destroyEventTask();
 }

cores/esp32/HardwareSerial.cpp

@@ -135,4 +135,4 @@ Legal Part
 
 Before a contribution can be accepted, you will need to sign our contributor agreement. You will be prompted for this automatically as part of the Pull Request process.
 
-.. _Arduino style guide: https://www.arduino.cc/en/Reference/StyleGuide
+.. _Arduino style guide: https://docs.arduino.cc/learn/contributions/arduino-writing-style-guide

docs/source/contributing.rst

@@ -73,6 +73,8 @@ Installing using PlatformIO
 
 PlatformIO is a professional collaborative platform for embedded development. It has out-of-the-box support for ESP32 SoCs and allows working with Arduino ESP32 as well as ESP-IDF from Espressif without changing your development environment. PlatformIO includes lots of instruments for the most common development tasks such as debugging, unit testing, and static code analysis.
 
+.. warning:: PlatformIO is not officially supported by Espressif. Please report any issues with PlatformIO directly to its developers on the official `PlatformIO repositories <https://github.com/platformio>`_.
+
 A detailed overview of the PlatformIO ecosystem and its philosophy can be found in `the official documentation <https://docs.platformio.org/en/latest/core/index.html>`_.
 
 PlatformIO can be used in two flavors:

docs/source/installing.rst

@@ -8,6 +8,9 @@ OTAWebUpdate is done with a web browser that can be useful in the following typi
 - after deployment if user is unable to expose Firmware for OTA from external update server
 - provide updates after deployment to small quantity of modules when setting an update server is not practicable
 
+For more information about the update process, please refer to the `OTA API reference <https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/ota.html>`_
+section of the ESP-IDF documentation.
+
 Requirements
 ------------
 

docs/source/ota_web_update.rst

@@ -41,9 +41,9 @@ bool        BTAdvertisedDeviceSet::haveRSSI() const { return m_haveRSSI; }
 std::string BTAdvertisedDeviceSet::toString() {
 	std::string res = "Name: " + getName() + ", Address: " + std::string(getAddress().toString().c_str(), getAddress().toString().length());
 	if (haveCOD()) {
-		char val[6];
-		snprintf(val, sizeof(val), "%ld", getCOD());
-		res += ", cod: ";
+		char val[7]; //6 hex digits + null
+		snprintf(val, sizeof(val), "%06x", getCOD() & 0xFFFFFF);
+		res += ", cod: 0x";
 		res += val;
 	}
 	if (haveRSSI()) {

libraries/BluetoothSerial/src/BTAdvertisedDeviceSet.cpp

@@ -18,17 +18,12 @@ Some ESP32 modules have different pin outs!
 ## Default SPI pins:
 Note that SPI pins can be configured by using `SPI.begin(sck, miso, mosi, cs);` alternatively, you can change only the CS pin with `SD.begin(CSpin)`
 
-+--------------+---------+-------+----------+----------+----------+
 | SPI Pin Name | ESP8266 | ESP32 | ESP32-S2 | ESP32-C3 | ESP32-S3 |
-+==============+=========+=======+==========+==========+==========+
+|--------------|---------|-------|----------|----------|----------|
 | CS (SS)      | GPIO15  | GPIO5 | GPIO5    | GPIO13   | GPIO13   |
-+--------------+---------+-------+----------+----------+----------+
 | DI (MOSI)    | GPIO13  | GPIO23| GPIO24   | GPIO14   | GPIO14   |
-+--------------+---------+-------+----------+----------+----------+
 | DO (MISO)    | GPIO12  | GPIO19| GPIO25   | GPIO15   | GPIO15   |
-+--------------+---------+-------+----------+----------+----------+
 | SCK (SCLK)   | GPIO14  | GPIO18| GPIO19   | GPIO16   | GPIO16   |
-+--------------+---------+-------+----------+----------+----------+
 
 ## FAQ:
 

libraries/SD/README.md

@@ -15,7 +15,7 @@ Image source: [Wikipedia](https://upload.wikimedia.org/wikipedia/commons/thumb/a
 Image source: [Wikipedia](https://commons.wikimedia.org/wiki/File:15-04-29-MMC-Karte-dscf4734-e.jpg)
 
 pin number (refer to the picture) | micro SD - SD mode | micro SD - SPI mode | mini SD - SD mode | mini SD - SPI mode | SD - SD mode | SD - SPI mode | MMC (MMC3) - MMC mode | MMC (MMC3) - SPI mode | MMCplus / MMCmobile (MMC4) - MMC mode | MMCplus / MMCmobile (MMC4) - SPI mode
-----------------------------------|--------------------|---------------------|-------------------|--------------------|--------------|---------------|-----------------------|-----------------------|---------------------------------------|
+----------------------------------|--------------------|---------------------|-------------------|--------------------|--------------|---------------|-----------------------|-----------------------|-----------------------------------------|--------------------------------------
 1                                 | D2                 | not used            | D3                | CS                 | D3           | CS            | RES                   | CS                    | D3                                    | CS
 2                                 | D3                 | CS                  | CMD               | DI                 | CMD          | DI            | CMD                   | DI                    | CMD                                   | DI
 3                                 | CMD                | DI                  | VSS1 (GND)        | VSS1 (GND)         | VSS1 (GND)   | VSS1 (GND)    | VSS1 (GND)            | VSS1 (GND)            | VSS1 (GND)                            | VSS1 (GND)

libraries/SD_MMC/README.md

@@ -182,7 +182,7 @@ class WiFiClientSocketHandle {
     }
 };
 
-WiFiClient::WiFiClient():_connected(false),_timeout(WIFI_CLIENT_DEF_CONN_TIMEOUT_MS),next(NULL)
+WiFiClient::WiFiClient():_rxBuffer(nullptr),_connected(false),_timeout(WIFI_CLIENT_DEF_CONN_TIMEOUT_MS),next(NULL)
 {
 }
 
@@ -508,7 +508,9 @@ int WiFiClient::available()
 // Though flushing means to send all pending data,
 // seems that in Arduino it also means to clear RX
 void WiFiClient::flush() {
-    _rxBuffer->flush();
+    if (_rxBuffer != nullptr) {
+        _rxBuffer->flush();
+    }
 }
 
 uint8_t WiFiClient::connected()