esp-idf/components/wear_levelling/test_apps
fl0wl0w 90d1dcfd76 feat(freertos): Introduced new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES
This commit replaces the use of portNUM_PROCESSORS and configNUM_CORES
macros in all of ESP-IDF. These macros are needed to realize an SMP
scenario by fetching the number of active cores FreeRTOS is running on.
Instead, a new Kconfig option, CONFIG_FREERTOS_NUMBER_OF_CORES, has been
added as a proxy for the FreeRTOS config option, configNUMBER_OF_CORES.
This new commit is now used to realize an SMP scenario in various places
in ESP-IDF.

[Sudeep Mohanty: Added new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES]

Signed-off-by: Sudeep Mohanty <sudeep.mohanty@espressif.com>
2024-02-09 09:11:28 +01:00
..
main feat(freertos): Introduced new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES 2024-02-09 09:11:28 +01:00
.build-test-rules.yml fix(ci): change build-test-rules files folder 2023-09-20 19:17:06 +08:00
CMakeLists.txt tools: Increase the minimal supported CMake version to 3.16 2022-06-01 06:35:02 +00:00
partitions.csv wear_levelling: move tests from unit-test-app to a component test app 2021-11-03 09:56:20 +01:00
pytest_wear_levelling.py ci: replace all component ut with pytest-embedded 2022-01-24 16:37:23 +08:00
README.md wear_levelling: move tests from unit-test-app to a component test app 2021-11-03 09:56:20 +01:00
sdkconfig.ci.4k wear_levelling: move tests from unit-test-app to a component test app 2021-11-03 09:56:20 +01:00
sdkconfig.ci.512perf wear_levelling: move tests from unit-test-app to a component test app 2021-11-03 09:56:20 +01:00
sdkconfig.ci.512safe wear_levelling: move tests from unit-test-app to a component test app 2021-11-03 09:56:20 +01:00
sdkconfig.ci.release wear_levelling: move tests from unit-test-app to a component test app 2021-11-03 09:56:20 +01:00
sdkconfig.defaults wear_levelling: move tests from unit-test-app to a component test app 2021-11-03 09:56:20 +01:00

Supported Targets ESP32 ESP32-C3

This is a test app for wear_levelling component. This app is for internal use. In CI, it is sufficient to run this test for one chip of each architecture.

Building

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

Example with configuration "4k" for target ESP32

rm -rf sdkconfig build
idf.py -DIDF_TARGET=esp32 -DSDKCONFIG_DEFAULTS="sdkconfig.defaults;sdkconfig.ci.4k" build

Running

To run locally:

idf.py flash monitor

The tests will be executed and the summary will be printed:

-----------------------
4 Tests 0 Failures 0 Ignored 
OK

Note, when the Python test script is executed in internal CI, it will test each configuration one by one. When executing this script locally, it will use whichever binary is already built and available in build directory.