esp-idf/tools/unit-test-app/configs/single_core

# This config is split between targets since different component needs to be included (esp32, esp32s2)
CONFIG_IDF_TARGET="esp32"
TEST_COMPONENTS=freertos esp_hw_support esp_system esp_timer driver soc spi_flash vfs
CONFIG_MEMMAP_SMP=n
CONFIG_FREERTOS_UNICORE=y
CONFIG_ESP32_IRAM_AS_8BIT_ACCESSIBLE_MEMORY=y
CONFIG_ESP32_RTCDATA_IN_FAST_MEM=y
Add build_unit_test.sh to do find_apps and build_apps to unit_tests modify unit-test-apps config files, use CONFIG_IDF_TARGET to set target. if not set, then treat them as supported both targets. 2020-04-28 22:38:05 -04:00			`# This config is split between targets since different component needs to be included (esp32, esp32s2)`
			`CONFIG_IDF_TARGET="esp32"`
heap: migrate unit tests to pytest 2022-09-19 05:46:55 -04:00			`TEST_COMPONENTS=freertos esp_hw_support esp_system esp_timer driver soc spi_flash vfs`
unit-test-app: new targets for building different configurations 2017-09-12 13:40:54 -04:00			`CONFIG_MEMMAP_SMP=n`
esp32: Add option to place.rtc_data and .rtc_rodata into the RTC_FAST segment Changes: KConfig: The option CONFIG_ESP32_RTCDATA_IN_FAST_MEM is added in Kconfig file for esp32 component. esp32.common.ld: added support of RTC_DATA_ATTR, RTC_RODATA_ATTR data placement into appropriate segment according to Kconfig option. esp32.ld: linker script is modified to set alias for memory segment selected by Kconfig option to place data. The segments for force placement are added for RTC_FAST_ATTR, RTC_SLOW_ATTR attributes. esp_attr.h: added new attributes RTC_FAST_ATTR, RTC_SLOW_ATTR for force placement into fest/slow memory. test_rtc_fast.c: Added unit test cases to check data placement into appropriate memory segment. Updated documentation for RTC_DATA_ATTR, RTC_FAST_ATTR, RTC_SLOW_ATTR in deep_sleep_stub.rst file. TW#18001 Closes https://github.com/espressif/esp-idf/issues/1553 2018-03-22 09:39:19 -04:00			`CONFIG_FREERTOS_UNICORE=y`
Exception handlers for LoadStoreError and LoadStoreAlignmentError Configurable option to use IRAM as byte accessible memory (in single core mode) using load-store (non-word aligned and non-word size IRAM access specific) exception handlers. This allows to use IRAM for use-cases where certain performance penalty (upto 170 cpu cycles per load or store operation) is acceptable. Additional configuration option has been provided to redirect mbedTLS specific in-out content length buffers to IRAM (in single core mode), allows to save 20KB per TLS connection. 2020-02-26 07:21:59 -05:00			`CONFIG_ESP32_IRAM_AS_8BIT_ACCESSIBLE_MEMORY=y`
esp32: Add option to place.rtc_data and .rtc_rodata into the RTC_FAST segment Changes: KConfig: The option CONFIG_ESP32_RTCDATA_IN_FAST_MEM is added in Kconfig file for esp32 component. esp32.common.ld: added support of RTC_DATA_ATTR, RTC_RODATA_ATTR data placement into appropriate segment according to Kconfig option. esp32.ld: linker script is modified to set alias for memory segment selected by Kconfig option to place data. The segments for force placement are added for RTC_FAST_ATTR, RTC_SLOW_ATTR attributes. esp_attr.h: added new attributes RTC_FAST_ATTR, RTC_SLOW_ATTR for force placement into fest/slow memory. test_rtc_fast.c: Added unit test cases to check data placement into appropriate memory segment. Updated documentation for RTC_DATA_ATTR, RTC_FAST_ATTR, RTC_SLOW_ATTR in deep_sleep_stub.rst file. TW#18001 Closes https://github.com/espressif/esp-idf/issues/1553 2018-03-22 09:39:19 -04:00			`CONFIG_ESP32_RTCDATA_IN_FAST_MEM=y`