You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Alexandre Abadie b0128f9dd1 tests: remove nucleo32-l031 from memory intensive tests 6 years ago
..
tests tests: mutex_order: added pexpect script 6 years ago
Makefile tests: remove nucleo32-l031 from memory intensive tests 6 years ago
README.md tests: mutex_order: fixed and updated README 6 years ago
main.c tests: mutex_order: remove xtimer dependency 6 years ago

README.md

Expected result

When successful, you should see 5 different threads printing their PID and priority. The thread with the lowest priority should be able to lock (and unlock) the mutex first, followed by the other threads in the order of their priority (highest next). The output should look like the following:

main(): This is RIOT! (Version: xxx)
Mutex order test
Please refer to the README.md for more information

T3 (prio 6): trying to lock mutex now
T4 (prio 4): trying to lock mutex now
T5 (prio 0): trying to lock mutex now
T6 (prio 2): trying to lock mutex now
T7 (prio 1): trying to lock mutex now
T5 (prio 0): unlocking mutex now
T7 (prio 1): unlocking mutex now
T6 (prio 2): unlocking mutex now
T4 (prio 4): unlocking mutex now
T3 (prio 6): unlocking mutex now

Test END, check the order of priorities above.

Background

This test application stresses a mutex with a number of threads waiting on it.