mirror of
https://github.com/espressif/esp-idf.git
synced 2025-10-23 10:52:09 +00:00
ci: run Example_GENERIC for C3
Add support for running example_GENERIC tests for C3 on label. Fix examples that fail.
This commit is contained in:

committed by
Angus Gratton

parent
c270a9f0b9
commit
8efb2bb1ed
@@ -1,7 +1,7 @@
|
||||
| Supported Targets | ESP32 |
|
||||
| ----------------- | ----- |
|
||||
| Supported Targets | ESP32 | ESP32-S2 |
|
||||
| ----------------- | ----- | -------- |
|
||||
|
||||
# High Resolution Timer Example (`esp_timer`)
|
||||
# High Resolution Timer Example (`esp_timer`)
|
||||
|
||||
(See the README.md file in the upper level 'examples' directory for more information about examples.)
|
||||
|
||||
@@ -15,7 +15,7 @@ The `esp_timer` API also provides the `esp_timer_get_time()` function which retu
|
||||
|
||||
### Hardware Required
|
||||
|
||||
This example should be able to run on any commonly available ESP32 development board.
|
||||
This example should be able to run on any commonly available ESP development board.
|
||||
|
||||
### Configure the project
|
||||
|
||||
@@ -127,7 +127,7 @@ I (5265) example: Periodic timer called, time since boot: 5002476 us
|
||||
|
||||
The one-shot timer runs and changes the period of the periodic timer. Now the periodic timer runs with a period of 1 second:
|
||||
|
||||
```
|
||||
```
|
||||
I (5265) example: One-shot timer called, time since boot: 5002586 us
|
||||
I (5265) example: Restarted periodic timer with 1s period, time since boot: 5005475 us
|
||||
I (6265) example: Periodic timer called, time since boot: 6005492 us
|
||||
@@ -144,7 +144,7 @@ I (10265) example: Periodic timer called, time since boot: 10005492 us
|
||||
### 5. Continuation through light sleep
|
||||
|
||||
To illustrate that timekeeping continues correctly after light sleep, the example enters light sleep for 0.5 seconds. This sleep does not impact timer period, and the timer is executed 1 second after the previous iteration. Note that the timers can not execute during light sleep, since the CPU is not running at that time. Such timers would execute immediately after light sleep, and then continue running with their normal period.
|
||||
|
||||
|
||||
```
|
||||
I (10275) example: Entering light sleep for 0.5s, time since boot: 10011559 us
|
||||
I (10275) example: Woke up from light sleep, time since boot: 10512007 us
|
||||
|
@@ -26,9 +26,9 @@ LIGHT_SLEEP_TIME = 500000
|
||||
ONE_SHOT_TIMER_PERIOD = 5000000
|
||||
|
||||
|
||||
@ttfw_idf.idf_example_test(env_tag='Example_GENERIC')
|
||||
@ttfw_idf.idf_example_test(env_tag='Example_GENERIC', target=['esp32'])
|
||||
def test_examples_system_esp_timer(env, extra_data):
|
||||
dut = env.get_dut('esp_timer_example', 'examples/system/esp_timer', dut_class=ttfw_idf.ESP32DUT)
|
||||
dut = env.get_dut('esp_timer_example', 'examples/system/esp_timer')
|
||||
# start test
|
||||
dut.start_app()
|
||||
groups = dut.expect(STARTING_TIMERS_REGEX, timeout=30)
|
||||
|
Reference in New Issue
Block a user