 Hello. Welcome to this session about 3-year TOS on STM32 devices. Within this session, we will discuss about 3-year TOS and its usage within STM32 devices using STM32 Cube MX application. We will start from the short discussion about the operating system. What is the operating system? What are the main components of it? Then we will switch to the basic features of 3-year TOS. The next point would be the discussion about APIs used within the 3-year TOS. We will shortly discuss 3-year TOS API as 91, and then we will switch into CMC-sized API, which is proposed by ARM, and which is an additional layer on top of 3-year TOS API. Within STM32 Cube MX and our examples, which are available for all STM32 devices, we are using CMC-sized API layer. This is why we will focus more on this part within this session. The next part would be STM32 Cube MX and its usage to generate the code with 3-year TOS on it. Then we will discuss shortly the configuration parameters available for the 3-year TOS. And the longer part would be about the memory allocation schemes and memory allocation techniques used within the 3-year TOS. Then we will slightly go to discuss the main components of 3-year TOS starting from scheduler. Then we will switch to tasks. The next point would be the discussion about the communication between the tasks. So we will touch the Qs, semaphors, signals. The next point would be about resource management. And then next we will switch into the mutexes, software timers. And after all those main components of the operating systems, we will focus a bit on hooks, stackover for protection, and other advanced topics which are related to 3-year TOS. We will demonstrate to you the main components about the debugging which are available within two tool chains IR and GCC based on Atollictro Studio example. And we will discuss low power support which is implemented within the 3-year TOS. At the end you will see some basic information about the footprint of 3-year TOS and its comparison with other operating systems for embedded application without MMU.