oRT5Zephyr RTOS Programming
Comprehensive Hands-On Zephyr OS Training
|
Objectives
|
- Theoretical course
- PDF course material
- Course dispensed using the Teams video-conferencing system
- The trainer to answer trainees' questions during the training and provide technical and pedagogical assistance through the Teams video-conferencing system
- Practical activities
- Practical activities represent from 40% to 50% of course duration
- The trainer has access to trainees' Online PCs for technical and pedagogical assistance.
- Example code, labs and solutions
- VSCode with Zephyr Workbench
- Simulated STM32 or NXP board using Zazu Simulator
- Good C programming skills (see our oL2 - C Language for Embedded MCUs course)
- Total: 30 hours
- 5 sessions, 6 hours each (excluding break time)
- From 40% to 50% of training time is devoted to practical activities
- Some Labs may be completed between sessions and are checked by the trainer on the next session
- Any embedded systems engineer or technician with the above prerequisites.
- The prerequisites indicated above are assessed before the training by the technical supervision of the traineein his company, or by the trainee himself in the exceptional case of an individual trainee.
- Trainee progress is assessed in two different ways, depending on the course:
- For courses lending themselves to practical exercises, the results of the exercises are checked by the trainer while, if necessary, helping trainees to carry them out by providing additional details.
- Quizzes are offered at the end of sections that do not include practical exercises to verifythat the trainees have assimilated the points presented
- At the end of the training, each trainee receives a certificate attesting that they have successfully completed the course.
- In the event of a problem, discovered during the course, due to a lack of prerequisites by the trainee a different or additional training is offered to them, generally to reinforce their prerequisites,in agreement with their company manager if applicable.
Course Outline
- Zephyr Ecosystem
- Why use Zephyr
- Drivers’ API abstraction
- Hardware-agnostic configuration
- Modular Architecture
- Host tools dependencies
- Install and Use Zephyr
- Overview
- West
- CMake
- Toolchains and Zephyr SDK
- Development environment
- VSCode Configuration
- Workbench for Zephyr
- Debugging Tools and runners
- Components of a Zephyr application
- Application structure
- Application types
- Samples & Tests
- Code structure
| Exercise: | Getting started with Zephyr | |
- Overview
- Kconfig
- Default configuration
- Interactive configuration tools
- Config fragments
- Devicetree
- Syntax
- Standard properties
- DeviceTree node structure
- Devicetree bindings
- Initial devicetree source
- Access devicetree from source code
- Overlays
- Best practices
- Snippets
| Exercise: | Write a devicetree overlay | |
- Operations without Threads
- Common subsytems
- GPIOs
- DeviceTree specification structures dt_spec
- I2C
- Utilities
- Preprocessor meta-programming macros
- Data Structures
- Single-linked List
- Double-linked List
- Ring Buffers
- Shell
| Exercise: | Using X-Macros in Zephyr and understanding CONTAINER_OF | |
| Exercise: | Writing custom shell commands | |
- Why West? Problems solved
- Alternatives and limitations
- West structure
- West manifest
- West workspace
- Anatomy of west.yml
- West topologies
- Writing custom manifests
- Specific commands and common extensions
- Init, update, list, config
- Build, debug, attach, flash
- Other common commands
- Extending West with custom commands
- Thread Fundamentals
- Thread Control Block
- Creating Threads
- Threads Priorities
- Main and Idle Threads
- System Initialization
- SYS_INIT
- Initialization levels
- Initialization order
- Delays and timeout
- Scheduling
- Kernel Timing
- States
- Scheduler Backends
- Thread Custom Data
| Exercise: | Create and manage threads | |
| Exercise: | Create periodic threads | |
- Runtime Statistics
- Scheduling Traces
- User-Defined Tracing
- Percepio Tracealyzer
| Exercise: | Create config overlay for visual trace diagnostics using Tracealyzer | |
- Memory Overview
- Dynamic memory managers
- K_heap
- System heap
- Memory Slabs
- Memory Blocks
- Heap Listeners
- Thread Resource Pools
- RAM/ROM reports
- Stack information
- Stack analysis
- Puncover
- High watermark
- Stack overflow detection
| Exercise: | Understand dynamic memory allocation in Zephyr | |
| Exercise: | Display threads information and detect stack overflow | |
- Overview
- Memory Domains
- Partitions
- Logical apps
- Syscalls
- Kernel objects
- Permissions
- Mutual Exclusion
- Mutexes
- Gatekeeper threads
- Critical Sections
- Atomic
- SpinLocks
- Semaphores
- Events
- Polling
| Exercise: | The producer-consumer problem, synchronize and avoid concurrent access problems | |
| Exercise: | Understanding event bit group by synchronizing several threads | |
- Data passing
- Message Queues
- Queues (FIFOs & LIFOs)
- Mailboxes
- Pipes
- Stacks
- Zephyr Bus (Zbus)
- Zbus overview
- Elements
- Usage
| Exercise: | Create a print gatekeeper thread using message queue | |
| Exercise: | Synchronous communication using mailboxes | |
- Threads and Interrupts
- Interrupts in zephyr
- Interrupts on ARM Cortex-M
- Handler thread
- Queue within an ISR
- Workqueue Threads
| Exercise: | Understand how to wait on multiple events and interrupt safe APIs | |
| Exercise: | Understand how to pass data using Queues from an interrupt to a thread | |
| Exercise: | Create and submit work items from interrupts to custom WorkQueue | |
- Message Queues
- Queues
- FIFOs
- LIFOs
- Mailboxes
- Pipes
- Stacks
- Zephyr Bus (Zbus)
- Zbus overview
- Elements
- Usage
| Exercise: | Create a print gatekeeper thread using message queue | |
| Exercise: | Synchronous communication using mailboxes | |
- Why to use modules?
- Module structure
- Out-of-tree module
- Module’s YAML
- Module CMakeLists.txt
| Exercise: | Create a basic module | |
- Advantages
- Kconfig Options in Zephyr RTOS
- Configuration System
- Writing custom Kconfig Options
- Kconfig extension
- Using Kconfigs
| Exercise: | Create and configure a module that uses custom Kconfig options | |
- Zephyr Device Driver Model
- Overview and its role
- Standard Drivers
- The struct device
- Subsystems
- Device definition
- API Extensions
- Devices allocation and initialization
- Using drivers in application
- Initialization Levels
- Dependencies between device drivers
| Exercise: | Create a driver that respects the Zephyr Device Driver Model and define devices | |
- Introduction to Device Drivers
- Overview of the Zephyr device driver model
- Standard Drivers
- The struct device
- Subsystems
- API Extensions
- Initialization Levels
- Dependencies between device drivers
- Define devices programmatically
| Exercise: | Create a driver that respects the Zephyr Device Driver Model and define devices | |
- Overview of Device Tree (DT) and its role in Zephyr
- Device Tree VS Kconfig
- Device Tree node structure
- Device Tree bindings
- Overlay and yaml files
- APIs to access device tree properties
- Write device drivers using device tree APIs
- Device Tree in Zephyr VS Linux
- Adding In-Tree Code to Zephyr Source Code
- Common properties
- compatible
- reg
- interrupts
| Exercise: | Create a driver that uses custom device tree and Kconfig | |
| Exercise: | Writing in-tree drivers | |
- Overview
- System Power Management
- Device Power Management
- System-Managed
- Runtime
- Power domains
| Exercise: | Write a driver compatible with power management subsystem | |
- Zephyr Board Architecture Overview
- Understanding SoC vs Board
- Role of a Board in Zephyr
- Structure and components of a board port
- Creating a New Board Definition
- Qualifiers and Revisions
- Integration and Creation Workflow
- Hardware Adaptation and Configuration Tuning
| Exercise: | Write a custom board | |
- Testing Fundamentals
- Zephyr test infrastructure overview
- Zephyr Test Framework (Ztest)
- Test Runner (Twister) overview
- Creating a test suite
- Timers
- Defining a Timer
- Using a Timer Expiry Function
- Timer types
- One-shot timers
- Auto-reload timers
- Timer Commands
| Exercise: | Understand the use of one-shot and auto-reload timers | |
More
To book a training session or for more information, please contact us on info@ac6-training.com.
Registrations are accepted till one week before the start date for scheduled classes. For late registrations, please consult us.
You can also fill and send us the registration form
This course can be provided either remotely, in our Paris training center or worldwide on your premises.
Scheduled classes are confirmed as soon as there is two confirmed bookings. Bookings are accepted until 1 week before the course start.
Last update of course schedule: 23 February 2026
Booking one of our trainings is subject to our General Terms of Sales