CoM260_Kit: add OpenHarmony test report

[DuoQilai]

Add the bilingual OpenHarmony 6.1 normal test report for CoM260 Kit. Record the default boot failure caused by the missing /k3_com260_ifx.dtb, and separately document the temporary boot with /k3_com260.dtb that reached a shell and desktop; the report remains CFH.

Includes the same board overview as #399 so this report can be reviewed independently.

Validation

• Bilingual report structure and local image references
• Scoped board and OS metadata check
• English and Chinese documentation included
• Commit scope reviewed and DCO sign-off verified
• SVG table generation (not run locally: pycairo is unavailable)

Summary by Sourcery

Document the CoM260 Kit’s OpenHarmony 6.1 test results and hardware context, including its failed default boot and temporary boot verification.

New Features:

• Add bilingual OpenHarmony 6.1 test documentation for the CoM260 Kit, including installation, serial access, boot results, and evidence.
• Add standalone bilingual CoM260 Kit board overview and technical specifications.

Enhancements:

• Document the default boot failure caused by the missing /k3_com260_ifx.dtb and the temporary successful boot using /k3_com260.dtb, including shell and desktop verification.

Documentation:

• Add English and Chinese user-facing test reports and board documentation with local images and relevant download and hardware references.

[sourcery-ai]

Reviewer's Guide

Adds a standalone bilingual CoM260 Kit board profile and an OpenHarmony 6.1 normal test report, including reproducible installation and serial-console procedures, evidence of the default missing-DTB boot failure, and a separately documented temporary boot that reaches the shell and desktop while retaining a CFH conclusion.

Sequence diagram for CoM260 OpenHarmony boot outcomes

sequenceDiagram
    participant UBoot
    participant BootFS
    participant Kernel
    participant OpenHarmony
    UBoot->>BootFS: load /k3_com260_ifx.dtb
    BootFS-->>UBoot: Failed to load
    UBoot->>UBoot: bootcmd
    UBoot-->>Kernel: Device tree not found
    Kernel-->>UBoot: Boot failure
    UBoot->>BootFS: load /k3_com260.dtb
    BootFS-->>UBoot: Device tree loaded
    UBoot->>UBoot: booti ${kernel_addr_r} ${ramdisk_combo} ${fdt_addr_r}
    UBoot->>Kernel: Start kernel
    Kernel->>OpenHarmony: Boot with temporary DTB
    OpenHarmony-->>Kernel: Shell and desktop available

Loading

File-Level Changes

Change	Details	Files
Adds an independent bilingual OpenHarmony 6.1 normal test report documenting both the default boot failure and temporary successful boot path.	Defines report metadata and CFH status. Documents flashing, serial-console setup, expected and actual results. Captures the missing /k3_com260_ifx.dtb failure and associated boot log. Records U-Boot commands used to select /k3_com260.dtb, explicitly boot the loaded images, and verify OpenHarmony, root shell access, and desktop output. Adds local references to board and test screenshots.	CoM260 Kit/OpenHarmony/README.md CoM260 Kit/OpenHarmony/README_zh.md
Adds bilingual standalone CoM260 Kit board overview and hardware metadata.	Adds product, CPU, core, RAM, storage, vendor, and power specifications. Links the K3-CoM260 datasheet for additional hardware information.	CoM260 Kit/README.md CoM260 Kit/README_zh.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="CoM260 Kit/OpenHarmony/README.md" line_range="46" />
<code_context>
+
+Prepare 1 female-to-female jumper wire. Orient the board as shown below, with the USB and Ethernet ports at the bottom and the button header at the top. Count positions from the left end of the header toward the right in this orientation.
+
+![CoM260 Kit button header](./boot-pins.png)
+
+| Positions counted from the left | Signals to short | Purpose |
</code_context>
<issue_to_address>
**nitpick:** All eight local image references point to PNG assets that are not included by this diff, so the board-pin diagram, flashing screenshots, and desktop screenshot render as broken images in both reports.

**Suggested fix:** Add the referenced PNG files under `CoM260 Kit/OpenHarmony/`, or change the links to the paths of the committed assets.
</issue_to_address>

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook