mikkeli
f49af26898
Two units with different jobs: one builds and runs CI, the other is the deployment target. Building on the target architecture makes the glibc constraint structural rather than configured. The remaining risk is version parity between the two units, not architecture. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013kj58Jugkic783b8ZrtTVZ
type
| type |
|---|
| reference |
Project Yukart
Making a 2008 Mitsubishi Colt Ralliart (Z27AG) a bit smarter with modern technologies. What the system is meant to do is described in OVERVIEW.md.
This repository is the overview and roadmap only — it holds no code. Every application or application cluster lives in its own repository and is indexed here.
Documents
- Overview — what the system is meant to do
- Architecture — system shape, services, message bus, display contract
- Orin runtime — what runs on the board: memory budget, startup tiers, audio
- Repositories — repo layout, naming, template-repo policy
- Roadmap — phases and current status
Repository index
| Repository | Role | Status |
|---|---|---|
| project-yukart | This hub — overview, roadmap, cross-cutting design | Active |
| orin-nano-env-setup | Jetson host bring-up: drivers, kernel modules, OS-level setup | Active |
Planned repositories and the reasoning behind the split are described in docs/REPOS.md.
Hardware at a glance
| Part | Role |
|---|---|
NVIDIA Jetson Orin Nano Super (mikkeli-orin-nano-2) |
Main compute, JetPack r36.4 / Ubuntu 22.04 |
| PEAK PCAN-USB | Car CAN bus access (can1, 500 kbps) |
| Onboard MTTCan | Second CAN interface (can0) |
| Waveshare SIM7600G-H-M.2 | LTE Cat 4 + GNSS |
Details and rationale live in the environment repo's bill of materials.