espressif/esp-idf
1
0
Fork 1
mirror of https://github.com/espressif/esp-idf.git synced 2025-10-17 17:25:23 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
e4c81979830efeda9068e01677cb15e20b3f4e55
esp-idf/components/heap/test_apps/heap_tests/sdkconfig.defaults

8 lines
340 B
Plaintext
Raw Normal View History

heap: add check for usage of flash content from iram this commits: - adds build-time test to check that no call to flash regions are done from IRAM functions - resolves problems related to IRAM function using content in flash memory - update heap_caps_alloc_failed to use a default function name in DRAM when necessary instead of creating a function name variable in DRAM for each call of heap_caps_alloc_failed. This allows to save some extra bytes in RAM.
2022-11-04 15:48:09 +01:00
CONFIG_COMPILER_DUMP_RTL_FILES=y
heap: migrate unit tests to pytest
2022-09-19 11:46:55 +02:00
CONFIG_ESP_TASK_WDT_CHECK_IDLE_TASK_CPU0=n
CONFIG_ESP_SYSTEM_MEMPROT_FEATURE=n # memory protection needs to be disabled for certain tests
esp_hw_support: allow writing in IRAM when CONFIG_ESP_SYSTEM_PMP_IDRAM_SPLIT is not set for esp32C2 when CONFIG_ESP_SYSTEM_PMP_IDRAM_SPLIT is not set, the PMP rule for esp32c2 shoud allow write access. Fix esp_cpu_configure_region_protection() in cpu.c accordingly.
2022-12-28 10:25:42 +01:00
CONFIG_ESP_SYSTEM_PMP_IDRAM_SPLIT=n # for c2 and c6 this config must be disabled for certain tests
esp_system: fix placement of __stack_chk_fail from flash to RAM When stack check is enabled, certain functions (sometimes placed in RAM) are being decorated with stack guards and a call to __stask_chk_fail() in case ofr stack corruption. For this reason, __stack_chk_fail() must be placed in RAM too. Add stack check config in heap tests on all targets to find eventual flash to RAM calls due to stack checks when running callgraph_check.py
2022-12-06 09:23:52 +01:00
CONFIG_COMPILER_STACK_CHECK_MODE_ALL=y
CONFIG_COMPILER_STACK_CHECK=y
Reference in New Issue Copy Permalink