Each transition shown in the following state diagram is caused by either an API call being made by your code or an action being taken by the scheduler. This is a simplified graphical overview of the possible states and transitions, along with a description of each:
Let's look at them one by one.
Get Hands-On RTOS with Microcontrollers now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.
Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.
Start your free trial Become a member now