Hi Murat,
On 02/09/15 18:46, Murat CAKMAK wrote:
Threads looks like working as blocking. In general, led3Thread is
started before and only led3Thread is working. Never switch to
Led4Thread (I could not see changes on Led4).
If I dont create thread3, I can see changes on Led4.
So, Why am I not able to observe context switching? Is it normal
behaviour or not?
RIOT will only interrupt a running thread if an ISR occurs or a higher
priority thread becomes runnable. So what you see is expected behaviour.
Using vtimer_usleep should put the calling thread to sleep (if the delay
is high enough to not cause spin-locking). Could you try that with a
fairly high sleep time (e.g., a second)?
Kaspar
_______________________________________________
devel mailing list
[email protected]
http://lists.riot-os.org/mailman/listinfo/devel
