* [Docs] Added the guideline for documentation
* [Docs] Added more descriptions about the API documenting process
* [Docs] PR review
* [Docs] PR review and minor typos and grammar fixes
Summary
The examples demonstrate how to create a WPA2 Enterprise connection, but it requires using various direct esp_idf functions. This patch is intended to create another overloaded version of the WiFi.begin() function that allows a user to create a WPA2 Enterprise connection in much the same way as different kinds of connections.
My only question for the core maintainers is whether I should leave those #ifdef's in there. I added them so that it was easy to disable all the code I added via defines from my platformio.ini file, but they technically aren't necessary.
Impact
This should make it easier for novice users to create WPA2 Enterprise connections. For my university, I didn't need a root certificate or the client certificate or client key, so I haven't been able to debug those scenarios, but I built the begin functions to allow any one of those to be used, if needed.
I can confirm that eduroam-style WPA2 Enterprise networks that only require authentication with a username and password works as expected.
In my project I'm getting the error
```
In file included from lib/Discovery/Discovery.cpp:2:
C:/Users/David/.platformio/packages/framework-arduinoespressif32/libraries/AsyncUDP/src/AsyncUDP.h:47:1: error: expected class-name before '{' token
```
Adding a reference to Stream.h fixes it.
1. Don't run the publish test result workflow on the master
branch.
2. Run only on Pull Requests to be able to publish the result as a PR comment.
3. Avoid running when the triggering workflow was skipped, this will
cause a failure as no file will be uploaded.
Signed-off-by: Abdelatif Guettouche <abdelatif.guettouche@espressif.com>
Summary
Updated documentation describing the usage of Arduino-esp32 core as ESP-IDF component.
Impact
Removed confusing mentions of advanced menuconfig options.
Extended process of installation, setup, and usage.
Related links
Closes#5833
Summary
The M5Core2 and the very similar M5Tough have 40 digital pins
See reference here: https://docs.m5stack.com/en/core/core2 as well as the constant declarations in the bottom part of the file.
Impact
Without this, Code that needs the total number of pins (e.g. firmata) doesn't show the higher pin numbers correctly.
* fixes setPins and begin to keep rx/tx unmodified
* adds Hardware Flow Control mode and CTS/RTS pin setting
* adds Hardware Flow Control mode and CTS/RTS pin setting
* adds Hardware Flow Control mode and CTS/RTS pin setting
* adds Hardware Flow Control mode and CTS/RTS pin setting
* Code Review
* Added the Tools Options into the docs.
* Added more options
* Deleted wrong file.
* [Docs] Added image to show the MSC and some grammar fixes
* [Docs] Added more information about the core selection
* Deleted wrong file.
* [Docs] Added more information about the core selection
* [Docs] Changes according to the PR review
* GPIO refactoring
GPIO now using ESP-IDF API on all chips.
LEDC interrupt fix removed - no longer needed.
Edited pins_arduino.h in variants according to changes in gpio.
* Edited analog channels functions
