GitLab

This PR brings updates according to the latest changes in the Arduino core:
- Bootloader binaries are now generated from elf files
- Updated CI scripts
- Updated esptoolpy to v4.2.1
- Minor clean-up by removing obsolete code

Resolves #7572

* Add support for Arduino IDE 2.0 Debug

* Update platform.txt

* Add SVD support

* Update configs for IDE 2.0.3

* Update esp32c3.json

* Added log errors + returns
* Update LEDC docs

* Fix hostByName to avoid asking DNS when valid IP is passed via hostname param
* Fix hanging in send_ssl_data

* Implements seekDir and getNextFileName on FS lib to improve performance
* getNextFileName return String directly

This commit addes an example showing how to receive messages using the TWAI
driver interface and a CAN transceiver. Specifically, the example demonstrates:

- How to configure and install the TWAI drvier
- How to poll for TWAI events (i.e., alerts) using twai_read_alerts()
- How to handle the various events (such as TWAI_ALERT_RX_DATA)

Closes https://github.com/espressif/arduino-esp32/pull/7430Co-authored-by: Stephan Martin <designer2k2@gmail.com>

* Add new board: RedPill ESP32S3.

* Change LED definition to keep compatibility.

* Add I2C and SPI pin definitions to wt32-eth01 pins

Added missing pins based on testing using a RTC (I2C) and SD card reader (SPI).

* Remove define macros
Co-authored-by: Rodrigo Garcia <rodrigo.garcia@espressif.com>
Co-authored-by: Jan Procházka <90197375+P-R-O-C-H-Y@users.noreply.github.com>

These instructions are based on esp32-arduino-lib-builder's build process, including https://github.com/espressif/esp32-arduino-lib-builder/blob/master/tools/update-components.sh which explains how to clone tinyusb.

* Added enableScenes API

* Added enableScenes API documentation

* Added enableScenes API to example
Co-authored-by: Jan Procházka <90197375+P-R-O-C-H-Y@users.noreply.github.com>

* ESP-IDF v4.4.3

Improves WiFi reconnection

* Add new board (Deneyap Kart 1A)

* Update pins_arduino.h

* Add newly  board (Deneyap Kart G)

New Deneyap Family member, wearable development board

* updated Deneyap boards pin_arduino.h files

* Update boards.txt

* Update pins_arduino.h

* updated deneyap boards pins_arduino.h

* updated Deneyap boards variants files

* updated Deneyap boards pins_arduino.h
Co-authored-by: Jan Procházka <90197375+P-R-O-C-H-Y@users.noreply.github.com>

which prevent changing to other partition scheme

* add touch.rst

* update touchRead comment in header file

* Edited examples

* typo changes + updates

* about edit

* Add ESP32S3 to libraries support list

* Update libraries.rst

* Add the Partition Scheme Menu to HELTEC LoRa32 V1

This is missing from many boards, i may add that to all of them

* reordered heltec_wifi_lora_32 partition options
Co-authored-by: Jan Procházka <90197375+P-R-O-C-H-Y@users.noreply.github.com>

* added test for touch peripheral

* removed cfg.json

* pass test for unsupported chips

* fixed condition

* changed released value for S2

* add new chip error

* Update RMakerDevice.h

Changer spelling of addTemprature

* Update RMakerDevice.cpp

Cahnge Spelling of add TempratureParam

* Update README.md

Update documentation addTemperatureParam

... while readValue

* Added OTA Event Handlers

* Overrided verifyRollbackLater Method
Co-authored-by: Rodrigo Garcia <rodrigo.garcia@espressif.com>

Update:
* actions/checkout
* actions/setup-python
* actions/cache

https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

Fixed #7406 . The "reason2str" macro in WiFiGeneric.cpp tries to read memory from index "-1"  in "system_event_reasons" array when handling STA_DISCONNECTED event with reason 0. Dealing with reason 0 as a reason 1 (WIFI_REASON_UNSPECIFIED) will solve the problem (the reason for this event to arrive with reason 0 is unknown). #7406

The original code assumes 100Hz FreeRTOS tick rate and just supplies vTaskDelay with the assumed number of ticks required for the wanted delay. This patch simply fixes it to use portTICK_PERIOD_MS, thereby working correctly regardless of what tick rate FreeRTOS has been configured to run at.

Co-authored-by: Pedro Minatel <pedro.minatel@espressif.com>

Somehow the fix #7129 was not applied to NORA-W10 probably both changes were happening at around the same time, this PR fixes this.
Co-authored-by: Jan Procházka <90197375+P-R-O-C-H-Y@users.noreply.github.com>