mirror of https://github.com/espressif/esp-idf.git synced 2026-10-01 02:30:52 +03:00

Files

T

Fu Hanxi b47f9850c7 ci: apply common-scripts CI refactor

Squashes these original commits for release/v5.4 backport traceability:
- 9b289dc5ad6 ci: apply idf-ci 1.x
- 381df980d57 ci: remove pip-cache and other unused jobs
- 32375a0a15e ci: apply common-scripts CI refactor

2026-08-17 14:13:15 +02:00

expected_output

fix(interrupt): fixed wrongly reserved interrupt for wifi on H2

2025-01-02 16:39:10 +08:00

main

fix(interrupts): fixed flakey intr dump test

2023-12-19 10:36:04 +08:00

CMakeLists.txt

ci(system): add test app for esp_intr_dump

2023-07-19 16:47:41 +02:00

pytest_esp_intr_dump.py

ci: apply common-scripts CI refactor

2026-08-17 14:13:15 +02:00

README.md

ci(esp32c61): remove c61 support from readme on 5.4

2025-06-17 15:09:40 +08:00

README.md

Supported Targets	ESP32	ESP32-C2	ESP32-C3	ESP32-C6	ESP32-H2	ESP32-P4	ESP32-S2	ESP32-S3

Test for esp_intr_dump

This test app serves two purposes:

Sanity-checking esp_intr_dump function. These tests run in QEMU and make sure that esp_intr_dump produces expected output when e.g. a shared interrupt is allocated.
Making unintended changes to the default interrupt allocations more visible in MRs. The way this works is, the output of esp_intr_dump is compared to the expected output, for example expected_output/esp32.txt. If you change IDF startup code so that it allocates an additional interrupt, you will need to update the expected output file. MR reviewers will see the modification of the expected output file and will evaluate the impact of the change.

When adding support for a new chip target

Build the test app for the new target, flash it to the board.
Enter intr_dump command in the console.
Copy the output and save it in expected_output/<target>.txt.