Back to News & Insights
Frontier Observations

Linux / RK3588 and E6: standard capability boundaries and a customization assessment checklist

Against the delivery package README, clarify standard capabilities for Linux x86_64 (installation, CDC-ACM time sync, DatasetServer) versus RK3588/ARM64, Lin

2026-09-08
Chief News Officer, TOBI Technology
Frontier Observations
E6 integration with a host-side Linux system
Chief Insights Open-Source Frontier 2026-09-13 Chinese original: about 7112 characters

Lead | First distinguish standard capabilities from custom wishes

The delivery package README describes Linux in very restrained terms: the standard environment is Linux x86_64; available capabilities include virtual reality client application installation, CDC-ACM serial port time synchronization, and DatasetServer sharded upload; the mobile application handles network, sharding, and upload configuration as well as preview via Bluetooth. ARM64 platforms such as the RK3588, Linux graphical preview, and recording control are not included in the standard delivery. This article provides a boundary explanation and a customization assessment checklist to help hardware teams avoid commitment-driven detours.

Standard capabilities: the three-piece set, not client-side illusions

The three-piece set is installation, time synchronization, and reception. They address time and data persistence in the production loop; they do not address the expectation of tapping to preview on the board like a phone.

Deploying the three-part toolkit on an industrial PC or workstation is the lowest-risk production default. Edge boards are an enhancement, not the default.

The README does not describe a Linux graphical control client, so its absence cannot be treated as a defect. Product communications must be consistent.

If the algorithm team only cares about the files after upload, the standard three-piece set is usually sufficient to get started.

Why RK3588 requires a separate assessment

Architecture, kernel, USB host implementation, Bluetooth availability, graphics stack, and thermal design all affect behavior. A successful demo board does not mean a production image will succeed.

The assessment must first lock down the target capability: time synchronization and upload only, or preview and camera-group selection. Different targets differ by an order of magnitude in effort.

Providing the distribution, kernel, Python version, interface photos, and reproduction logs is the admission ticket for assessment. A verbal description of the board model is not enough.

Scheduling development before the assessment is complete amounts to treating the unknown as known.

E6 connected to a host system
Figure 1 | E6 host integration uses the README trio as the standard; on-board graphics capability requires separate evaluation.

How to use the compatibility assessment checklist

Checklist items include architecture and system, target capability, verification logs, upload path, and delivery-scope confirmation. Score each item; items that are missing do not proceed to design.

Verification logs must include at least the ttyACM device list, debug bridge device list, script output, and reproduction steps.

The upload path must specify the network segment, reachability of port 9000, and chunk duration. This must be stated clearly when the network namespace on the board side is complex.

Out-of-scope capabilities are quoted separately with their own milestones and are not counted together with standard open-source support in the service level.

Recommended implementation path

Phase 1: get the three-piece set and short recordings working on x86_64. Phase 2: if the business must go edge-native, then initiate a board-side assessment. Phase 3: interface contract and test plan.

Prepare the mobile control plane in parallel as the gold-standard reference. When board-side behavior differs from the mobile app, the written interface specification is the arbiter.

Long-run stability testing covers hot-plug, full disk, wrong address, permissions, and thermal jitter.

Freeze the version after approval; changes go through regression testing.

High-density equipment setup
Figure 2 | Higher-density sensing depends more on stable time synchronization and upload; choose a reliable host topology first.

Coordination Across Documentation, Sales, and Open-Source Issues

Sales talking points must not go beyond the README. If a customer has a strong requirement for Rockchip, route it to an evaluation ticket rather than making a verbal promise.

When an open-source issue involves an on-board requirement, the reply template should point to the evaluation checklist.

The official website's dedicated Linux section and the repository documentation must keep the same revision number.

Write the coordination rules into the customer success handbook.

Acceptance Criteria

Before starting a custom project, all of the following criteria must be met or explicitly waived.

  1. Target capabilities are documented in writing and classified as in-scope versus out-of-scope;
  2. System information and log package are complete;
  3. Time synchronization and upload reproduction are completed on the agreed image, or the failure reason is clearly stated;
  4. The interface contract and test plan draft are ready;
  5. Sales and documentation talking points are aligned;
  6. The path to exiting to the x86_64 trio is viable.
On-site data capture
Figure 3 | On-site, only the reproduction chain is accepted as valid; the evaluation checklist is more useful than a verbal compatibility claim.

Risk Register and Exit Mechanism

If the evaluation fails, retain the standard three-part solution as an exit path to avoid the project stalling completely.

The risk register includes kernel defects, Bluetooth instability, and data loss caused by thermal throttling.

On exit, the verified x86_64 documentation and scripts are still delivered, protecting the value the customer has already paid for.

The open-source community can absorb general fixes, but board-level adaptation may not be upstreamed; this must be stated in the contract.

One-Page Conclusions for the Hardware Lead

The standard open-source path serves most data loops; edge boards are a productization option. Closing the loop first, then going edge, is the optimal cost curve.

Use the evaluation checklist to protect the engineering team, boundary statements to protect customer expectations, and the exit mechanism to protect the business relationship.

TOBI documents capabilities clearly — that is not negativity, it is professionalism.

After reading this article, bring your board information and target capabilities to the alignment discussion — it is far more efficient than coming with a wish list of "we need support for everything."

Engineering Deep Dive, On-Site Access Control, Q&A and Appendix Requirements

Regarding the "x86_64 trio," it is recommended to list progress and risks separately in the project weekly report: write one sentence each for verified facts, unverified assumptions, and next-step experiments. This way, open-source integration will not stop at feeling good, but will stop at inspectable evidence. The same format can also be used to sync with external collaborators, reducing idle meetings.

During change windows involving "RK3588", freeze parallel large-scale changes: complete small-scope regression first, then allow multi-person submissions. Hardware open source is most vulnerable when multiple variables change at once. The regression package should include a shortest-path success example and known failure examples to ensure failures are reproducible.

Add "ARM64" to the first-week tasks for new hires: not reading slogans, but hands-on completion of one operation and submission of a screenshot or log summary as proof. A low pass rate indicates a documentation gap, not merely a gap in the new hire's ability. Documentation gaps must flow back into the repository or the materials ledger.

Build a counterexample library for the "kernel": every correct practice must be accompanied by the incorrect practice and its consequences. Field personnel remember counterexamples more deeply than rules. The counterexample library is pruned and updated once per quarter to stay in sync with the current firmware and toolchain.

If metrics related to "ttyACM" drift, perform layered diagnosis first: device, host, network, procedure, human factors. Jumping directly to changing the model or hardware selection is prohibited. Layered diagnostic records are retained for ninety days for audit and retrospective review.

When demonstrating "Bluetooth" externally, prioritize showing access control and logs rather than only the final output. Decision-makers trust repeatable processes more. Version the demo script to avoid inconsistent commitments caused by improvisation each time.

Owners responsible for the "graphics stack" must have explicit veto authority and an escalation path. A quality role without veto authority is mere decoration. The escalation path must be written into the support manual so it can be executed even during holidays.

When measuring the "evaluation checklist", do not rely solely on a binary pass/fail; retain the distribution: the 50th percentile, the 95th percentile, and the extreme tail. The tail determines production pain. Distribution charts brought to weekly meetings drive resource allocation better than averages.

When the "interface contract" requires cross-team collaboration, first write a one-page interface: inputs, outputs, timeouts, failure codes, owner. An interface is cheaper than a consensus meeting. Interface changes go through a short review to prevent private-chat decisions from affecting the whole system.

When reviewing historical incidents related to "hot-plug", use a unified template: symptom, affected sessions, root cause, fix, whether re-collection is required. The template forces a distinction between sporadic and systemic issues. Systemic issues must flow back into firmware, documentation, or procedures, not rely on individual heroics.

In budget discussions, break down the cost of "full disk" into tool time, human-factor time, and rework time. Looking only at the tool purchase price underestimates total cost of ownership. The broken-down figures better support investment in open-source governance.

Keep the minimal runnable example for the "exit path" runnable at all times: a broken example equals broken documentation. Continuous integration runs the examples nightly, and any failure blocks the merge. The examples are also the fastest path for customer onboarding.

Regarding "sales talking points," it is recommended to list progress and risks separately in the project weekly report: write one sentence each for verified facts, unverified assumptions, and next-step experiments. This way, open-source integration will not stall on a good feeling, but on inspectable evidence. The same format can also be used to sync with external collaborators, reducing idle meeting time.

During change windows involving "Issue templates", freeze parallel large-scale changes: complete small-scope regression first, then allow multi-person submissions. Hardware open source is most vulnerable when multiple variables change at once. The regression package should include a shortest-path success example and known failure examples to ensure failures are reproducible.

Add "thermal throttling" to the first-week tasks for new hires: not reading slogans, but hands-on completion of one operation and submission of a screenshot or log summary as proof. A low pass rate indicates a documentation gap, not merely a gap in the new hire's ability. Documentation gaps must flow back into the repository or the materials ledger.

Build a counterexample library for "image freezing": every correct practice must be accompanied by the incorrect practice and its consequences. Field personnel remember counterexamples more deeply than rules. The counterexample library is pruned and updated once per quarter to stay in sync with the current firmware and toolchain.

If metrics related to "gold-standard phone control" drift, perform layered diagnosis first: device, host, network, procedure, human factors. Jumping directly to changing the model or hardware selection is prohibited. Layered diagnostic records are retained for ninety days for audit and retrospective review.

When demonstrating "milestones" externally, prioritize showing access control and logs rather than only the final frame. Decision-makers trust repeatable processes more. Version the demo script to avoid inconsistent commitments caused by improvising each time.

The standard capability boundary is written into the README to protect both parties' time. On Linux x86_64, what you can expect is the VR-side application installation script, CDC-ACM time synchronization, and DatasetServer ingestion — not an on-board graphical preview client.

What makes the RK3588 attractive is its edge compute capability and deployment form factor, but the kernel, USB host, Bluetooth stack, graphics stack, and thermal design can all alter behavior. Promising "it works just like a laptop" without evaluation is the standard recipe for a project incident.

The evaluation checklist should request: CPU architecture, distribution, kernel, Python version, available interfaces, whether the target capability is sync-only upload or requires preview control, reproduction logs, and network topology. If any one item is missing, do not schedule development time.

If only time synchronization and upload are needed, prioritize deployment on an x86_64 industrial PC, with the on-board platform reserved for later expansion. Get the standard pipeline working first, then discuss customization — the cost curve is better this way.

Custom clients require a separate interface contract: how configuration items are delivered, the preview stream protocol, camera array switching, and failure codes. Defaulting mobile app behavior to be isomorphic with Linux is a design shortcut.

The test plan must cover at least: hot-plug, long-duration stable time sync, full-disk upload, invalid addresses, insufficient permissions, intermittent Bluetooth. On-board field conditions are dirtier than the lab; tests must be dirty.

Documentation and sales talking points must be consistent. If sales says "supports Rockchip" while the engineering documentation says "out of scope", customer trust will collapse within a week.

When on-device requirements surface in open-source issues, they should be routed to the evaluation ticket template rather than debated as product roadmap on GitHub.

For the algorithm team: on-board latency differs from a laptop, but the dataset timeline should still be based on device time synchronization — do not substitute the on-board display clock.

Milestone payments should be discussed only after evaluation: evaluation, prototype, small-batch, frozen version. Open source lowers the cost of getting started, but does not reduce architectural risk.

The evaluation project proposal template has five fixed sections: target capabilities, system profile, success criteria, test plan, and exit path. No section, no budget approval.

If on-board graphical preview involves proprietary codecs, licensing and performance must be additionally evaluated. Open-source host scripts do not substitute for codec licensing.

Even validating only time sync plus upload on the RK3588 is closer to honest engineering than claiming support for everything. A small-scope success can be written up as a phase report.

If kernel customization disables cdc_acm, it must be blocked in the image build check. A silently missing module wastes an entire week on-site.

Test the antenna and coexistence issues of Bluetooth on the board separately. Being able to connect in the lab does not mean being able to connect next to a metal enclosure.

If a customer insists on an all-in-one form factor, offering a compromise topology of "on-board plus bypass x86_64 time-dissemination box" often reaches mass production earlier than a purely on-board solution.

Full-disk test cases in the test plan should use real large shards, not small files pretending to be.

The warning color blocks in the documentation are updated in sync with the sales presentation deck to avoid the deck still stating "full ARM support."

Lessons learned from failed evaluations are captured in the internal knowledge base to prevent repeated evaluation of the same board model.

If the open-source community submits an ARM patch, label it experimental in nature until it enters the written support matrix.

For algorithms, the on-board clock jitter distribution may differ; the dataset still uses device timekeeping as the authoritative source, and display-link latency is measured separately.

The project manager manages evaluations with a red-amber-green board: a red light prohibits committing to delivery dates.

When falling back to an industrial PC solution, reuse the same DatasetServer and time-stamping scripts to reduce sunk cost.

The hardware procurement contract specifies: for boards not listed in the support matrix, compatibility work is billed by person-day.

Place the evaluation checklist near the Linux dedicated section on the official website; customer self-service pre-filling can accelerate the process.

Q: What is the standard three-piece set? A: Installation, CDC-ACM time synchronization, and DatasetServer reception.

Q: Why is there no Linux preview? A: The README does not define one; the preview is in the mobile app.

Q: What are the minimum materials for evaluation? A: System profile, target capabilities, log package, network topology.

Q: Does time-synchronization upload alone count as success? A: If that is the objective, it counts as a phase success, and written confirmation is required.

Q: The kernel does not have cdc_acm? A: The build check should block; fix the image first.

Q: What if sales has already committed to on-board capabilities? A: Escalate to evaluation and change management; stop handling it as a standard defect.

Q: What is the exit path? A: Fall back to the x86_64 industrial PC three-piece set.

Q: Why is the full-disk test important? A: Small files cannot reveal real sharding failure modes.

Q: Bluetooth fails near the equipment rack? A: This is a coexistence and antenna issue that requires on-site testing.

Q: Does a patch entering the community mean it is supported? A: It is experimental until it enters the written matrix.

Q: What about an all-in-one topology compromise? A: A board-level bypass timing box is usually brought to production earlier.

Q: Should algorithms care about the on-device clock? A: Display latency is accounted separately; data time still depends on device time synchronization.

Q: Who maintains the traffic-light dashboard? A: The project manager; a red light prohibits committing to a delivery date.

Q: How are person-days billed? A: Work outside the support matrix is billed by evaluation person-days.

Q: Is there a self-service pre-fill checklist? A: It is placed in a dedicated documentation section to speed up pre-review.

Q: Does thermal throttling cause data loss? A: It is recorded in the risk register along with thermal mitigation measures.

Q: When is the interface contract written? A: Draft before the prototype; finalize before the freeze.

Q: Do we debate the roadmap in Issues? A: No; route it to the evaluation template.

Q: Who is responsible for reproducing a failure? A: First ensure the materials are complete; if materials are missing, return them for completion.

Q: Do all distributions need to be tested? A: Test according to the customer matrix; claims of support must be backed by evidence.

Q: What if the Python version is too old? A: Upgrade per the README requirements or use a separate interpreter policy.

Q: What do we evaluate in the graphics stack? A: Licensing, performance, latency, and failure codes.

Q: How should a phase report be written? A: Clearly state what has and has not been verified; implying full support is prohibited.

Q: The customer wants a development schedule? A: No hard dates are given before the evaluation is complete.

Q: Why is the knowledge base important? A: To prevent repeated evaluation of the same model.

Q: What is the gold-standard comparison? A: Phone control-plane behavior as comparison arbitration.

Q: Who signs off on regression after changes? A: Embedded and support jointly.

Q: What is the boundary between open source and customization? A: Open source preserves the standard; customization is tracked as a separate milestone.

When implementing capabilities related to "rk3588", project initiation without a defined exit path must not be approved. Likewise, if the on-device side only verifies time-synced uploads, the stage boundaries must be documented. It is recommended to add these requirements to the weekly checklist and review at the next stand-up whether they have been properly executed; any gaps should be recorded as process deficiencies rather than individual attitude issues. The same checklist can also be shared with external collaborators to reduce memory discrepancies about "what was already said", ensuring that open-source integration and delivery acceptance always have a verifiable record.

When implementing "rk3588"-related capabilities, the image build check fails immediately if cdc_acm is missing. At the same time, Bluetooth testing next to the rack is included in the on-site checklist. It is recommended to add these requirements to the weekly checklist and review at next week's stand-up whether they were properly executed; if not, record it as a process defect rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what was already said" on both sides, keeping open-source integration and delivery acceptance always traceable.

When implementing capabilities related to "rk3588", the sales deck and the warning color block must be updated in sync with the revision number. At the same time, repeated evaluations of the same model should be blocked by the knowledge base. It is recommended to write the above requirements into the weekly checklist and review at the next stand-up whether they have been properly executed; if not, record it as a process deficiency rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what has already been said," ensuring that open-source integration and delivery acceptance always have a documented basis.

When implementing "rk3588"-related capabilities, the compromise topology solution library provides optional configurations. At the same time, full-disk test cases use real sharding volumes. It is recommended to add these requirements to the weekly checklist and review at next week's stand-up whether they were properly executed; if not, record it as a process defect rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what was already said" on both sides, keeping open-source integration and delivery acceptance always traceable.

When implementing capabilities related to "rk3588", no external delivery dates may be promised while the status is red. Work outside the matrix should be quoted in person-days and written into the contract. It is recommended to add the above requirements to the weekly checklist and review at the next stand-up whether they have been implemented; if not, record it as a process deficiency rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias on both sides about "already communicated", keeping open-source integration and delivery acceptance always traceable.

When implementing "rk3588"-related capabilities, self-service pre-fill reduces pre-review back-and-forth. At the same time, thermal risks are registered separately with countermeasures. It is recommended to add these requirements to the weekly checklist and review at next week's stand-up whether they were properly executed; if not, record it as a process defect rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what was already said" on both sides, keeping open-source integration and delivery acceptance always traceable.

When implementing "rk3588"-related capabilities, the interface contract draft is completed before the prototype. At the same time, the Issue template automatically attaches the evaluation link. It is recommended to add these requirements to the weekly checklist and review at next week's stand-up whether they were properly executed; if not, record it as a process defect rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what was already said" on both sides, keeping open-source integration and delivery acceptance always traceable.

When implementing "rk3588"-related capabilities, any claimed supported distribution must have an evidence package. At the same time, the separate interpreter policy for outdated Python versions must be clearly documented. It is recommended to add these requirements to the weekly checklist and review at next week's stand-up whether they were properly executed; if not, record it as a process defect rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what was already said" on both sides, keeping open-source integration and delivery acceptance always traceable.

When implementing "rk3588"-related capabilities, graphics stack license review must not be done verbally. At the same time, phase reports must not imply full support. It is recommended to add these requirements to the weekly checklist and review at next week's stand-up whether they were properly executed; if not, record it as a process defect rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what was already said" on both sides, keeping open-source integration and delivery acceptance always traceable.

When implementing "rk3588"-related capabilities, the gold-standard mobile control plane is used for arbitration. At the same time, custom milestones and open-source support are accounted for separately. It is recommended to add these requirements to the weekly checklist and review at next week's stand-up whether they were properly executed; if not, record it as a process defect rather than an individual attitude issue. The same checklist can also be shared with external collaborators to reduce memory bias about "what was already said" on both sides, keeping open-source integration and delivery acceptance always traceable.

Additional requirements: An evaluation project without an exit path must not be approved. Bluetooth testing next to the rack should be included in the on-site checklist. Full-disk test cases should use real shard volumes. If conflicts are discovered during execution, the written specification and the current frozen version take precedence, and a documentation revision should be raised within twenty-four hours to avoid relying on ad-hoc verbal explanations on site for long-term operation.

Supplementary requirements: if the on-board side only verifies time-synced upload, stage boundaries must also be written. Sales demo decks and warning color blocks must be updated in sync with revision numbers. Red-light status prohibits external date commitments. If conflicts are found during execution, the written specifications and the current frozen version take precedence, and a documentation revision must be raised within twenty-four hours, avoiding long-term operation relying on ad-hoc verbal explanations on site.

Additional requirements: Missing cdc_acm in the image build check results in immediate failure. Repeat evaluations of the same model are blocked by the knowledge base. Out-of-matrix work is quoted by person-day and written into the contract. If conflicts are discovered during execution, the written specification and the current frozen version shall prevail, and a documentation revision shall be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations during on-site long-term operation.

Additional requirements: Bluetooth testing next to the rack is included in the on-site checklist. The compromise topology solution library provides optional configurations. Self-service pre-fill reduces pre-review back-and-forth. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: sales demo decks and warning color blocks must be updated in sync with revision numbers. Full-disk test cases must use real shard volumes. Thermal risks must be logged separately along with countermeasures. If conflicts are discovered during execution, the written specification and the current frozen version take precedence; a documentation revision must be submitted within twenty-four hours to avoid relying on ad-hoc verbal explanations on site for long-running operations.

Additional requirements: Repeated evaluation of the same model is blocked by the knowledge base. A red-light status prohibits committing to dates externally. The interface contract draft is completed before the prototype. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: the compromise topology solution library provides optional configurations. Out-of-matrix work is quoted per person-day and written into the contract. Issue templates automatically attach evaluation links. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be raised within twenty-four hours, avoiding reliance on ad-hoc verbal explanations on site for long-term operation.

Additional requirements: Full-disk test cases use real sharding volumes. Self-service pre-fill reduces pre-review back-and-forth. Any claimed supported distribution must have an evidence package. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: A red-light status prohibits committing to dates externally. Thermal risks are registered separately with countermeasures. The separate interpreter policy for outdated Python versions must be clearly documented. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: Work outside the matrix is quoted by person-day and written into the contract. The interface contract draft is completed before the prototype. Graphics stack license review must not be done verbally. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: self-service pre-filling reduces pre-review back-and-forth. Issue templates automatically attach evaluation links. Stage reports must not imply full support. If conflicts are discovered during execution, the written specifications and the current frozen version shall prevail, and a documentation revision shall be proposed within twenty-four hours to avoid relying on ad-hoc verbal explanations for long-term operation on site.

Additional requirements: Thermal risks are registered separately with countermeasures. Any claimed supported distribution must have an evidence package. The gold-standard mobile control plane is used for arbitration. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: The interface contract draft is completed before the prototype. The separate interpreter policy for outdated Python versions must be clearly documented. Custom milestones and open-source support are accounted for separately. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: Issue templates should automatically attach evaluation links. Graphics stack license review must not be conducted verbally. An evaluation project without an exit path must not be approved. If conflicts are discovered during execution, the written specification and the current frozen version shall prevail, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on on-site verbal improvisation for long-term operation.

Additional requirements: Any claimed supported distribution must have an evidence package. Phase reports must not imply full support. Even if the device side only verifies time-synchronization upload, the phase boundary must be documented. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: The separate interpreter policy for outdated Python versions must be clearly documented. The gold-standard mobile control plane is used for arbitration. The image build check fails immediately if cdc_acm is missing. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: Graphics stack license review must not be done verbally. Custom milestones and open-source support are accounted for separately. Bluetooth testing next to the rack is included in the on-site checklist. If conflicts are found during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, avoiding reliance on ad hoc verbal explanations on site for long-term operation.

Additional requirements: Phase reports must not imply full support. An evaluation project without an exit path must not be approved. Sales demonstration decks and warning color blocks must carry synchronized revision numbers. If conflicts are discovered during execution, the written specification and the current frozen version take precedence, and a documentation revision must be submitted within twenty-four hours, avoiding reliance on ad hoc verbal explanations in the field for long-term operation.

Additional requirements: the gold-standard mobile control plane is used for arbitration. Even if the on-board side only verifies time synchronization upload, the phase boundary must be written down. Repeated evaluations of the same model are blocked by the knowledge base. If conflicts are discovered during execution, the written specification and the current frozen version take precedence, and a documentation revision must be proposed within twenty-four hours, to avoid relying on ad hoc verbal explanations on site for long-term operation.

Additional requirements: Custom milestones and open-source support must be accounted for separately. Image build checks that are missing cdc_acm fail directly. The compromise topology solution library provides optional configurations. If conflicts are discovered during execution, the written specification and the current frozen version take precedence, and a documentation revision must be submitted within twenty-four hours, avoiding reliance on ad hoc verbal explanations in the field for long-term operation.

Next Step: Moving from an Open-Source SDK to an Acceptable Joint Integration

If your team is evaluating Linux/RK3588 and E6 integration, first complete cloning, package verification, and host-side integration based on the GitHub README and the delivery package, then document synchronization, upload, calibration, and licensing boundaries in the project acceptance annex. The open-source repository helps you get started quickly; the written specification determines the delivery scope.

Go to Developer Docs · E2 / E6 Device SDK Get the clone command, Drive / Baidu materials, and Linux integration instructions, or directly Contact Technical Integration Align versions, samples, and acceptance fields.