esp-idf/tools/test_apps/system/panic
2021-10-27 11:03:35 +08:00
..
main Update tests for assert and abort 2021-09-08 16:32:09 +08:00
test_panic_util CI: Debug GDB issues 2021-07-27 20:03:57 +02:00
app_test.py Update tests for assert and abort 2021-09-08 16:32:09 +08:00
CMakeLists.txt test_apps: add panic test 2020-05-12 22:27:06 +02:00
panic_tests.py test_apps/panic: remove workaround for incorrect GDB backtrace 2021-10-25 20:19:55 +07:00
README.md bugfix/esp-gdbstrub: add missing function for esp32c3/esp32h2. 2021-10-27 11:03:35 +08:00
sdkconfig.ci.coredump_flash_bin_crc Coredump config option rename throughout IDF 2020-09-30 20:22:27 +05:30
sdkconfig.ci.coredump_flash_elf_sha Coredump config option rename throughout IDF 2020-09-30 20:22:27 +05:30
sdkconfig.ci.coredump_uart_bin_crc Coredump config option rename throughout IDF 2020-09-30 20:22:27 +05:30
sdkconfig.ci.coredump_uart_elf_crc Coredump config option rename throughout IDF 2020-09-30 20:22:27 +05:30
sdkconfig.ci.gdbstub test/panic: add gdbstub test configuration 2020-10-13 18:09:22 +02:00
sdkconfig.ci.panic test_apps: add panic test 2020-05-12 22:27:06 +02:00
sdkconfig.defaults system: stack watchpoint support on C3 2021-01-14 17:46:44 +08:00

Supported Targets ESP32 ESP32-S2 ESP32-S3 ESP32-C3

Building

Several configurations are provided as sdkconfig.ci.XXX and serve as a template.

Example with configuration "panic" for target ESP32

idf.py set-target esp32
cat sdkconfig.defaults sdkconfig.ci.panic > sdkconfig
idf.py build

Running

All the setup needs to be done as described in the test apps README, except that the test cases need to be specified when running the app:

python app_test.py test_panic_illegal_instruction

Multiple test cases are passed as additional arguments:

python app_test.py test_panic_illegal_instruction test_panic_int_wdt test_panic_storeprohibited

Note that you need to pick the correct test cases at run time according to the configuration you built before. The above examples are for configuration "panic"