OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/portability/cmsis_rtos_v2/prj.conf

20 lines
540 B
Plaintext
Raw Normal View History

tests/cmsis_rtos_v2: Introduce tests to make use of Thread APIs Some test programs to illustrate the usage of thread APIs. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:15:29 +08:00
CONFIG_ZTEST=y
CONFIG_CMSIS_RTOS_V2=y
CONFIG_NUM_PREEMPT_PRIORITIES=56
tests: cmsis_rtos_v2: Dynamic memory pool tests Implemented a second set of memory pool tests that function on a dynamically allocated memory pool. Abstracted some of the common functionality to a common function. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:19:01 +08:00
CONFIG_HEAP_MEM_POOL_SIZE=1024
tests/cmsis_rtos_v2: Introduce tests to make use of Thread APIs Some test programs to illustrate the usage of thread APIs. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:15:29 +08:00
CONFIG_POLL=y
CONFIG_THREAD_NAME=y
CONFIG_THREAD_STACK_INFO=y
CONFIG_THREAD_MONITOR=y
CONFIG_IRQ_OFFLOAD=y
CONFIG_INIT_STACKS=y
tests: set CONFIG_MAX_THREAD_BYTES for a few tests Some tests instantiate a lot of thread objects. These were not tagged with __kernel, and CONFIG_APPLICATION_MEMORY was enabled, so the kernel was not adding them to the kernel object database. However, with CONFIG_APPLICATION_MEMORY disabled, this overflowed the default max number of thread objects (16). Increase the max to 32 for these particular tests. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-02-01 07:09:41 +08:00
CONFIG_MAX_THREAD_BYTES=4
tests/cmsis_rtos_v2: Use CONFIG_SCHED_SCALABLE Using multi-queue scheduler doesn't work for cmsis_rtos_v2 as it supports a max of only 32 priority levels which is less than the total priority levels required by cmsis_rtos_v2 (which is 56). Hence explicitly asking the tests to use the scalable scheduler. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-11-21 12:35:03 +08:00
CONFIG_SCHED_SCALABLE=y
tests: cmsis_rtos_v2: Dynamic thread stack tests Added a set of tests that use the default thread stacks to ensure they work the same as the passed in stacks. Abstracted the common functionality into functions. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:39:43 +08:00
CONFIG_CMSIS_V2_MEM_SLAB_MAX_DYNAMIC_SIZE=128
tests: cmsis_rtos_v2: Join and detach tests Implemented tests for the new join and detach features. - The first tests multiple join operations. - The second tests trying to join a detached thread. - The third tests abandoning a join when the thread is detached after creation. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-07 06:03:56 +08:00
CONFIG_CMSIS_V2_THREAD_MAX_COUNT=23
CONFIG_CMSIS_V2_THREAD_DYNAMIC_MAX_COUNT=10
lib/cmsis_rtos_v2: Update to newer timeout API Mostly simple. Note that the CMSIS RTOS2 API specifies timeout values in system ticks instead of milliseconds, so the conversions here are able to elide a conversion that the original code had to do. That's a good thing, but does mean that in practice runtime behavior will not be 1:1 identical. Also note that the switch away from legacy timeouts involved a change to 64 bit timeouts by default, which pushed tests/portability/cmsis_rtos_v2 over the limit on qemu_xtensa. Unfortunately CMSIS stacks have a fixed limit we can't increase, so I turned off 64 bit timeouts (CMSIS apps won't need them by definition anyway -- their API is 32 bit). Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2020-05-05 07:00:08 +08:00
CONFIG_TIMEOUT_64BIT=n
tests: cmsis_rtos_v2: Fix stack overflow Increase the stack to avoid overflow problems. Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
2020-09-18 07:28:45 +08:00
CONFIG_CMSIS_V2_THREAD_MAX_STACK_SIZE=1024
CONFIG_CMSIS_V2_THREAD_DYNAMIC_STACK_SIZE=1024
tests: cmsis_rtos_v2: limit number of CPUs to 1 Some of the thread tests are hard-coded with assumption that there is only one CPU. So limit the number of CPUs to 1 via kconfig. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-12-11 10:09:23 +08:00
CONFIG_MP_NUM_CPUS=1