facab8c5a7
This updates the minimal supported version of CMake to 3.16, which in turn enables us to use more CMake features and have a cleaner build system. This is the version that provides most new features and also the one we use in our latest docker image for CI. |
||
---|---|---|
.. | ||
main | ||
CMakeLists.txt | ||
README.md |
README.md
LEDC Fade Example
(See the README.md file in the upper level 'examples' directory for more information about examples.)
This example shows how to control intensity of LEDs using selected SoC's on-board hardware LED PWM Controller module.
How to use example
Hardware Required
- A development board with any Espressif SoC (e.g., ESP32-DevKitC, ESP-WROVER-KIT, etc.)
- A USB cable for power supply and programming
Connect four LEDs to the following LEDC channels / individual GPIOs:
Channel 0 | Channel 1 | Channel 2 | Channel 3 | |
---|---|---|---|---|
ESP32 | GPIO18 | GPIO19 | GPIO4 | GPIO5 |
All other chips | GPIO8 | GPIO9 | GPIO4 | GPIO5 |
Configure the project
idf.py menuconfig
Build and Flash
Build the project and flash it to the board, then run the monitor tool to view the serial output:
Run idf.py -p PORT flash monitor
to build, flash and monitor the project.
(To exit the serial monitor, type Ctrl-]
.)
See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects.
Example Output
Running this example, you will see each ledc's brightness changes differently
- LEDC 1: Fade up / increase intensity
- LEDC 2: Fade down / decrease intensity
- LEDC 3: Keep a stable intensity
- LEDC 4: LED is not on
you can also see the following output log on the serial monitor:
1. LEDC fade up to duty = 4000
2. LEDC fade down to duty = 0
3. LEDC set duty = 4000 without fade
4. LEDC set duty = 0 without fade
...
Troubleshooting
-
Programming fail
- Hardware connection is not correct: run
idf.py -p PORT monitor
, and reboot your board to see if there are any output logs. - The baud rate for downloading is too high: lower your baud rate in the
menuconfig
menu, and try again.
- Hardware connection is not correct: run
For any technical queries, please open an issue on GitHub. We will get back to you soon.