Engineering Scope
Low-power MCU selection and main board adaptation development are used to solve specific engineering problems in low-power projects. The work starts from the customer's existing design and business requirements, checks the reserved resources of each power mode, adapts the driver and target board startup; delivers selection comparison, board-level code, construction instructions and function records according to the agreed module delivery.
Check input with baseline
Check the peripheral list, storage and computing power requirements, wake-up sources, SDK and interface timing, and clarify the scope of measurement and modification.
Implementation and adaptation
Check the reserved resources of each power mode, adapt the driver and target board to start, and record the solution choices and dependency conditions.
Target environment joint debugging
Trigger wake-up one by one in target mode and check peripheral recovery and data to confirm business behavior after parameter changes.
Document and record delivery
Provide selection comparison, board-level code, build instructions and function records, explaining the version, construction or usage method.
Project Workflow
- Input confirmation: peripheral list, storage and computing power requirements, wake-up source, SDK and interface timing.
- Implementation method: Check the reserved resources of each power mode, adapt the driver and start the target board.
- Phase review: Trigger wake-up and check peripheral recovery and data in target mode one by one.
- Engineering delivery: selection comparison, board-level code, build instructions and functional records.
Design Conditions and Functional Limits
First determine the power consumption ratio of the existing main controller and peripherals. If the main consumption comes from sensors or communications, changing the main controller may not be able to achieve the goal, and should be decided based on the complete budget.
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
- Peripheral list, storage and computing power requirements, wake-up sources, SDK and interface timing.
- 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 |
|---|---|
| Selection comparison, board-level code, build instructions and feature records | Check the editability, version, usage instructions and dependencies by file list. |
| Implementation verification | Trigger wake-up and check peripheral recovery and data one by one in target mode, 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
Do I have to change to the low power series MCU?+
First determine the power consumption ratio of the existing main controller and peripherals. If the main consumption comes from sensors or communications, changing the main controller may not be able to achieve the goal, and should be decided based on the complete budget.
What information do I need to prepare before starting the project?+
This work focuses on the peripheral list, storage and computing power requirements, wake-up sources, SDK and interface timing. 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