alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
83d4e8c6ab
esp-idf/tools/test_apps/system/esp_intr_dump
History
Armando 3c5a4f9e8a ci(p4): added todo jira for disabled tests on p4
2024-01-04 09:36:38 +08:00
..
expected_output fix(ci): fix expected intr_dump result 2023-08-22 12:25:53 +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(p4): added todo jira for disabled tests on p4 2024-01-04 09:36:38 +08:00
README.md feat(ci): Enable p4 example, test_apps and unit tests CI build 2023-08-24 12:51:19 +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:

  1. 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.
  2. 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

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