Scope and project conditions
Adapt boot, pins, power and peripherals for a target vision board, establishing a buildable, flashable and diagnosable Linux system base.
Use third-party BSPs and binary components under their applicable rights; identify deliverable source code and dependency versions at handover.
Development and delivery process
Requirements and interfaces
Schematics, board revision, BSP sources, boot media and peripheral list.
Design and implementation
Adapt boot, pins, power and peripherals for a target vision board, establishing a buildable, flashable and diagnosable Linux system base.
Integration and validation
Validate boot logs, pin and power configuration, peripherals, reboot and upgrade behavior, and system recovery.
Versioned delivery and handover
BSP changes, device trees, build and flashing scripts, system images and debug records.
Deliverables and version records
Project deliveryBSP changes, device trees, build and flashing scripts, system images and debug records.
At project kickoff, agree prototype quantities, source-file scope, build environment, third-party components and handover method. Deliverables identify their hardware and software revisions for maintenance and future changes.
Validation and acceptance
Service-specific checksValidate boot logs, pin and power configuration, peripherals, reboot and upgrade behavior, and system recovery.
Define the configuration, test objects, operating conditions and decision method before testing. Acceptance records include the setup, raw evidence, issue resolution and retests; performance values come from the corresponding test conditions.
Project questions
What is included in the delivery?
BSP changes, device trees, build and flashing scripts, system images and debug records.
What needs to be agreed before the project starts?
Use third-party BSPs and binary components under their applicable rights; identify deliverable source code and dependency versions at handover.