![]() ![]() ![]() In most cases, interrupts occur during thread execution (or in the thread scheduling loop). This predefined program area is commonly called an Interrupt Service Routine. On detection of an interrupt, the processor saves key information about the current program execution (usually on the stack), then transfers control to a predefined program area. Without interrupts it would be extremely difficult to respond to changes in the external world in a timely manner. Interrupts are the cornerstone of real-time systems. This process of continually executing and scheduling threads is the most common type of program execution in ThreadX applications. After the thread is finished (or another higher-priority thread becomes ready), execution transfers back to the thread scheduling loop to find the next highest priority ready thread. When a ready thread is found, ThreadX transfers control to it. The scheduling loop looks for an application thread ready for execution. Thread ExecutionĪfter initialization is complete, ThreadX enters its thread scheduling loop. Initialization includes all program execution between processor reset and the entry point of the thread scheduling loop. InitializationĪs the name implies, this is the first type of program execution in a ThreadX application. More detailed information about each of these types is found in subsequent sections of this chapter. There are four types of program execution within a ThreadX application: Initialization, Thread Execution, Interrupt Service Routines (ISRs), and Application Timers.įigure 2 shows each different type of program execution. Each functional component is presented in an easy-to-understand manner. This chapter contains a description of the high-performance Azure RTOS ThreadX kernel from a functional perspective. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |