English | 简体中文
Mo Studio and toolchain usage examples for InHand Mo series single-board computers.
This repository will hold Mo Studio, the desktop companion application for Mo boards, and worked examples that show how to use the Mo toolchain (compilers, debuggers, flashing and board bring-up utilities) from a development host.
Related repositories:
- Mo62A — board support package, OS image build and device-side runtime for the Mo 62A board.
- mo-docs — product documentation for the Mo series.
| Repository | Maintained source | Delivery responsibility |
|---|---|---|
| developer · GitLab | Website components, routes, search, integration and contracts | The complete website, release composition and deployment |
| mo-docs | Software/hardware tutorials, specifications, media, design files and training | Versioned content and reference assets |
| mo-tools | Toolchain/SDK selection, environment setup, reusable tools and Studio | Tool metadata and source packages |
| mo-models | Model catalog, compilation resources, compatibility and raw benchmarks | Model references, evidence and artifact status |
| mo-examples | Complete examples with related firmware, clients and configuration | Example sources and their requirements |
| Mo* · product repositories | Each product's BSP, drivers, root filesystem, image build and flashing | Product images and checksummed release metadata |
Mo* covers independently maintained product repositories such as Mo62A, Mo68A, Mo69A, Mo67A, Mo3588 and Mo3568. The framework does not fix their number. Hardware content and maintainer training live in mo-docs; the archived mo-hardware repository is only a migration record, and the pre-release website keeps no legacy /hardware-docs/ routes.
Each source repository publishes ordinary versions. Developer alone has website RC/final channels. The target composition binds developer + mo-docs + mo-tools + mo-models + mo-examples + selected Mo* to exact commits and consumed-asset hashes. A new source release does not change an already frozen website combination. Tutorial applicability, PCB revisions, image versions and actual validation remain distinct.
The directory layout, contribution rules and the CI and release pipelines are in place. products/mo62a/toolchain/ holds the pinned TI edgeai-tidl-tools baseline (versions.json) and the x86 host setup scripts; products/mo62a/board-test/ holds the Mo62A desktop board test tool migrated from the Mo62A repository. Published archives are listed under GitHub Releases; their existence does not establish hardware or production qualification.
Product directories: products.json lists the boards; each board keeps its toolchain selection, host setup, board test and diagnostics under products/<board>/ (products/mo62a/ for Mo62A, products/mo68a/ reserved for Mo68A). These tools are not shared between boards. studio/ stays at the top level: Mo Studio, not yet designed, is the only tool expected to support several boards.
| Path | Purpose |
|---|---|
products/mo62a/toolchain/ |
Pinned TI toolchain versions, official download links and host setup scripts. |
products/mo62a/board-test/ |
Mo62A board test tool (PySide6 GUI over SSH, HTML reports). |
studio/ |
Mo Studio (placeholder; the only tool planned to support several boards, not designed yet). |
scripts/ |
Repository maintenance scripts (commit message check, changelog generation). |
.githooks/ |
Git hooks that run the commit message check locally. |
.github/ |
Issue forms, pull request template and GitHub Actions workflows. |
release-notes/ |
Changelog baseline used by the release workflow. |
Contributions are welcome through pull requests to master. Read CONTRIBUTING.md for the commit message convention, the pull request process and how to enable the local Git hooks:
git config core.hooksPath .githooksEvery pull request must pass the commit-message and ci checks before it can be merged. Use GitHub issues for bugs, reproducible problems and feature requests in this repository.
New releases use annotated ordinary V<major>.<minor>.<patch> tags on checked master commits. Only developer publishes website release candidates. The release workflow validates catalogs, packages source with SPDX SBOM, records the source commit and catalog hashes in release.json, writes SHA-256 checksums, then publishes a complete GitHub Release. Historical RCs remain unchanged. Changelog headings are bilingual; entries retain their English commit summaries.
git switch master
git pull --ff-only
git tag -a V1.0.0 -m "V1.0.0"
git push origin V1.0.0Do not report security vulnerabilities in public issues. Follow SECURITY.md.
This repository is licensed under the terms in LICENSE. Third-party content added later keeps its own license, stated next to the content.
products/mo62a/toolchain/versions.json owns the selected TI toolchain versions and official download references. It includes the documented MCU+ SDK / Arm Clang / SysConfig combination; Linux/A53 cross-compilation remains explicitly unverified. SDK installers stay with TI. Developer reads a pinned source revision, validates the combined data, and renders the website; this repository has no documentation-site frontend or website deployment.
Run node scripts/check-catalog.mjs and node --test tests/*.test.mjs with Node 22. validation/ is exported from a committed developer contract and checked by hash; do not edit it locally. For integrated preview, run developer's npm run preview -- --source mo-tools=/path/to/mo-tools.
Diagrams are generated centrally by developer/scripts/render-architecture.mjs. Regenerate all repository diagrams after changing the common architecture. Diagrams show ownership; the status section and catalog define currently available content and verification.
Regenerate these diagrams from developer with node scripts/render-architecture.mjs --repo mo-tools --out /path/to/mo-tools/architecture. Source releases validate the catalogs and resources; developer separately verifies the combined website release and deployment. Open each diagram to read the original SVG.
products/mo62a/diagnostics/peripherals owns general GPIO, PWM and UART diagnostic scripts. products/mo62a/toolchain/host-setup owns the model-compilation host environment. Mo-docs references these tools in tutorials, and developer generates compatible download URLs from the resource map. Complete R5F applications, firmware and clients belong to mo-examples.