Decision summary
Define an RK3588 integration project through actual application workloads, display and I/O needs, BSP responsibilities, measured acceptance criteria and controlled documents. Treat the result as approval of a recorded configuration, not every variant in a product family.
Describe the complete workload
State which display, media, camera, compute, network and peripheral functions run together. Agree measurable latency, throughput and stability requirements for that setup rather than quoting an unrelated benchmark.
Control hardware and software variants
Record the exact board, memory/storage configuration, PCB revision and software/toolchain baseline. Keep known limitations and changes visible during sample evaluation.
Plan the handover
Agree images, interfaces, release notes, source/build scope where applicable, recovery instructions and maintenance ownership. Define how changes and replacement components are qualified before deployment.
What evidence should be requested?
- Current model specification, drawings and interface definitions.
- Board revision, software release and connected-equipment list.
- Test procedures, conditions, results and known limitations.
- Applicable model-specific compliance documents.
- Written deliverables, support, quotation and change-control terms.
No customer deployment, certification or test result is established by this guide. Review document availability, read the source policy, or send the project requirements.
