yukart/orin-nano-env-setup
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Pin CAN interface names by udev; document device naming

Browse Source 
mttcan and pcan both load at boot, so the PCAN adapter could take can0
and push the onboard controller to can1. A udev rule now names them
can_onboard (platform c310000.mttcan) and can_pcan (USB 0c72:000c),
both outside the canN pool so a transient canN can never collide.

Also records why the SIM7600 needs nothing more: ModemManager and NM
don't use ttyUSB numbers, and gpsd already uses a symlink.

can_onboard is verified live; can_pcan is checked against the driver
source only (adapter not plugged in).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
mikkeli
2026-10-08 01:38:25 +09:00
parent 4742d4a5bb
commit 2d62d1a4f8
3 changed files with 72 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/impl/reports/PCAN-SETUP.md
+3
View File
@@ -100,6 +100,9 @@ $ ip link show type can
- `can0` = onboard MTTCan
- `can1` = PCAN-USB adapter
> **2026-10-08:** `canN` order is not stable across boots. Interfaces are now pinned to `can_onboard` / `can_pcan`
> by a udev rule; read `can1` below as `can_pcan`. See [device naming](DEVICE-NAMING.md).
### Step 5: Bring Up the Interface
```bash