Engineering guide
For an RK3588 Android board SDK baseline, map costs to work packages, deliverables and external inputs as shown below. This defines scope rather than a lump-sum price, fixed schedule, payment terms or default charging rules.
Work packages and deliverables
Swipe the table horizontally to view all columns.
| Work package | Deliverables to agree | External inputs and scope |
|---|---|---|
| Baseline reproduction | Environment inventory, build steps, logs and known issues | Identify providers of the SDK, vendor support and third-party dependencies |
| Images and recovery | Image checksums, flashing instructions and boot records for the target board | Confirm boards, storage, power supplies and recovery tools separately |
| Toolchain delivery | Tool versions, configuration and repeatable operating instructions | Itemize release signing, OTA, peripheral work and production tests as applicable |
What inputs are needed before starting?
The full board model and revision, Android SDK, build instructions, existing images, peripheral list and serial logs. Check document versions and availability first and retain missing items as unresolved inputs.
How should delivery and acceptance be defined?
Build and boot the target board in the agreed environment using the delivered procedure; verify versions, logs and issues, and agree treatment of blocking defects. A reproducible baseline does not establish peripheral, application, endurance or production readiness; scope Linux and OpenHarmony separately.
Enterprises in Shenzhen, China, can submit these inputs for remote review. Agree prototype integration, sample shipment, site work and associated costs for the specific project.
Review the service scope and submit the project inputs before agreeing on development and delivery. Original Chinese service scope
Online
Phone
WeChat
Top