mirror of
https://github.com/espressif/esp-idf.git
synced 2025-11-26 12:50:30 +00:00
ci: partially enable example build for esp32c2
This commit is contained in:
committed by
morris
parent
acd4ca0f6e
commit
f7be540222
@@ -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.)
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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]>
|
||||
|
||||
```
|
||||
|
||||
|
||||
@@ -1,3 +1,6 @@
|
||||
| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
|
||||
| ----------------- | ----- | -------- | -------- | -------- |
|
||||
|
||||
# eFuse Example
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.)
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.)
|
||||
|
||||
@@ -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+]
|
||||
|
||||
@@ -1,3 +1,6 @@
|
||||
| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
|
||||
| ----------------- | ----- | -------- | -------- | -------- |
|
||||
|
||||
# Heap Task Tracking Example
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -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.)
|
||||
|
||||
@@ -1,3 +1,6 @@
|
||||
| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
|
||||
| ----------------- | ----- | -------- | -------- | -------- |
|
||||
|
||||
# OTA Tool Example
|
||||
|
||||
This example demonstrates common operations the OTA tool [otatool.py](../../../../components/app_update/otatool.py) allows the user to perform:
|
||||
|
||||
@@ -1,3 +1,6 @@
|
||||
| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
|
||||
| ----------------- | ----- | -------- | -------- | -------- |
|
||||
|
||||
# Pthread Example
|
||||
|
||||
(See the README.md file in the upper level 'examples' directory for more information about examples.)
|
||||
|
||||
@@ -1,3 +1,6 @@
|
||||
| Supported Targets | ESP32 | ESP32-S2 | ESP32-S3 | ESP32-C3 |
|
||||
| ----------------- | ----- | -------- | -------- | -------- |
|
||||
|
||||
# Synchronous I/O multiplexing example
|
||||
|
||||
The example demonstrates the use of synchronous I/O multiplexing by the select()
|
||||
|
||||
Reference in New Issue
Block a user