Engineering Scope
RTOS Low-power task scheduling was developed to solve specific engineering problems in low-power projects. The work starts from the customer's existing design and business requirements, merging scheduled tasks, reducing empty polling, adapting to idle and tickless scheduling; delivering task configurations, patches, build instructions and scheduling event records according to the agreed modules.
Check input with baseline
Check the RTOS version, task and timer list, interrupt source and cycle requirements, and clarify the measurement and modification scope.
Implementation and adaptation
Merge scheduled tasks, reduce empty polling, adapt to idle and tickless scheduling, and record program trade-offs and dependency conditions.
Target environment joint debugging
Check the clock accuracy, task deadline, wake-up frequency and business integrity, and confirm the business behavior after parameter changes.
Document and record delivery
Provide task configuration, patches, build instructions and scheduling event records, describing the version, build or usage method.
Project Workflow
- Enter confirmation: RTOS version, task and timer list, interrupt source and period requirements.
- Implementation method: merge scheduled tasks, reduce empty polling, and adapt to idle and tickless scheduling.
- Phase review: Check clock accuracy, task deadline, wake-up frequency and business integrity.
- Project delivery: task configuration, patches, build instructions and scheduling event records.
Design Conditions and Functional Limits
It is also necessary to check whether the driver, timer, polling and interrupts continue to prevent hibernation, and finally verify it with the task behavior and the overall machine current.
Special services take the agreed module as the implementation boundary. When hardware modifications, third-party agreements, overall platforms or external tests are involved, the interfaces, workload and responsibilities are confirmed separately, and local modifications are not directly used as conclusions on the performance of the complete device.
Project Inputs
- RTOS version, task and timer list, interrupt sources and period requirements.
- Existing prototypes and reproducible problems, or new project functionality and power consumption targets.
- Modified design, source code and third-party dependencies are allowed; functionality and compatibility need to be maintained.
- Delivery list, target environment, sample scope, project milestones and acceptance methods.
Delivery and Acceptance
| Delivery content | Check method |
|---|---|
| Task configuration, patches, build instructions and scheduling event records | Check the editability, version, usage instructions and dependencies by file list. |
| Implementation verification | Check the clock accuracy, task deadline, wake-up frequency and business integrity, and retain the corresponding working conditions and results. |
| Comparison of functions and power consumption | Fixed applicable hardware, software, battery, temperature and business cycles, accounting for changes in conditions and their impact. |
| Reproduction and follow-up maintenance | Provide build or run steps, known limitations, parameter ranges, and uncovered cases. |
Frequently Asked Questions
Can turning on tickless solve all standby problems?+
It is also necessary to check whether the driver, timer, polling and interrupts continue to prevent hibernation, and finally verify it with the task behavior and the overall machine current.
What information do I need to prepare before starting the project?+
This work focuses on the RTOS version, task and timer list, interrupt source and cycle requirements. When the data is incomplete, first determine the scope that needs supplementary testing or sorting out, and then proceed to implementation.
Can it be implemented together with the complete device development project?+
It can be used as a work package in the overall project, or it can be implemented separately for existing products. It is necessary to explain the interfaces with other modules, versions and final machine verification responsibilities.
Engineering References
The configuration of GPIO should be checked together with the external circuit, sleep mode and wake-up status; the actual parameters are subject to the target chip data and the whole board test. GPIO and power state design reference
Online
Phone
WeChat
Top