RAU6 Dokuwiki

User Tools

Site Tools

Trace: • STM32 Control of built-in LEDs with buttons • ID MRZ RECOGNITION • Programming in Assembler Laboratory • Laboratory on ESP 8266 • Laboratory on LEGO Mindstorms - EV3 C# Programming Theory & Practice • STM32 Control of built-in LEDs with PWM • STM32 Introduction
No ACL setup yet! Denying access to everyone.
en:edu:zmitac:s2:aih:lab:nrf52threads

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:edu:zmitac:s2:aih:lab:nrf52threads [2023/11/23 16:51] – ktokarzen:edu:zmitac:s2:aih:lab:nrf52threads [2023/12/01 13:52] (current) – ktokarz
Line 5: Line 5:
   * cooperative   * cooperative
   * preemptive   * preemptive
-In the cooperative method, the thread is executed until it gives the control back to OS. Thus thread can starve others while not releasing resources. This method is often used in embedded systems due to its low complexity and system overhead. Cooperative threads in Zephyr have a negative priority value (thus they have a relatively higher priority).+Zephyr OS implements both methods of thread switching. In the cooperative method, the thread is executed until it gives back the control to OS. Thus thread can starve others while not releasing resources. This method is often used in embedded systems due to its low complexity and system overhead. Cooperative threads in Zephyr have a negative priority value (thus they have a relatively higher priority).
 In the preemptive method, the thread is automatically suspended by the operating system when it decides to do so. Usually, the thread is given some period and is interrupted at the end of this period if there exists another thread to be executed. This method is implemented in general-purpose operating systems like Windows or Linux. It is much safer but more complicated and resource-consuming. In Zephyr preemptive threads have a positive priority number (thus they have a relatively lower priority). In the preemptive method, the thread is automatically suspended by the operating system when it decides to do so. Usually, the thread is given some period and is interrupted at the end of this period if there exists another thread to be executed. This method is implemented in general-purpose operating systems like Windows or Linux. It is much safer but more complicated and resource-consuming. In Zephyr preemptive threads have a positive priority number (thus they have a relatively lower priority).
-Zephyr OS implements both methods of thread switching. + 
-===== Cooperative thread switching =====+===== Thread switching example =====
 A cooperative thread gives control to the operating system in a few situations: A cooperative thread gives control to the operating system in a few situations:
   * if it decides to terminate by returning from its main function or by calling the k_thread_abort().   * if it decides to terminate by returning from its main function or by calling the k_thread_abort().
Line 17: Line 17:
 While implementing the thread with the infinite loop it is recommended to call the k_yield() or some sleep function every pass of the loop. While implementing the thread with the infinite loop it is recommended to call the k_yield() or some sleep function every pass of the loop.
  
-As the first example, we'll show the one available within the Nordic Developer Academy ((https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-7-multithreaded-applications/topic/exercise-1-7/)) because the sample provided in the Zephyr framework is a little more advanced and complex for the beginning. This example creates two threads writing to the console simple text identifying the thread. +A preemptive thread can be stopped by the operating system at any time if it finds the higher-priority thread ready to operate. 
 + 
 +As the first example, we'll show the one available within the Nordic Developer Academy ((https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-7-multithreaded-applications/topic/exercise-1-7/)) because the sample provided in the Zephyr framework is a little more advanced and complex for the beginning. This example creates two threads writing to the console simple text identifying the thread. Notice that in the original program, both threads have a positive value of the priority which makes them the preemptive threads.
  
 <code> <code>
Line 68: Line 70:
  
 </code> </code>
 +
 +===== The tasks for the laboratory =====
  
 To go through the lab please follow the steps: To go through the lab please follow the steps:
Line 73: Line 77:
   - If you experience a problem with the include paths delete "zephyr/" from paths of *.h files   - If you experience a problem with the include paths delete "zephyr/" from paths of *.h files
   - Compile and execute the program, observe the behaviour of threads in the terminal   - Compile and execute the program, observe the behaviour of threads in the terminal
-  - Make some experiments observing results in the terminal +  - Make some experiments as described below observing results in the terminal 
-  * change the priority of one thread +  * modify the priority of one thread 
-  * change the priority of both threads to negative numbers+  * modify sleep periods in k_msleep() functions 
 +  * change the priority of one and later of both threads to negative numbers making them cooperative
   * change the method of passing control to OS - comment k_msleep() function call, uncomment k_yield()   * change the method of passing control to OS - comment k_msleep() function call, uncomment k_yield()
-  * change version of k_msleep() to k_usleep(), k_sleep() - the latter one requires +  * change version of k_msleep() to k_usleep(), k_sleep() - the latter one requires the k_timeout_t type structure as the parameter 
  
en/edu/zmitac/s2/aih/lab/nrf52threads.1700754682.txt.gz · Last modified: by ktokarz