What problem does it solve? RDK developers often misidentify their board (X3/X5/Ultra/S100/S100P/S600) and receive wrong package names, TROS paths, and toolchain advice, or brick S-series boards by flashing with incorrect xburn settings. This Skill grounds every answer in read-only on-board probes and official D-Robotics documentation instead of guesses. ## Core Features & Use Cases - Board identification & baseline confirmation: Runs a read-only probe (scripts/board_probe.sh) reading /sys/class/socinfo and /proc/device-tree/model to map the board to its BPU march, OS/TROS version, default IP, and power requirements. - Failure diagnosis: Routes 59 documented error symptoms (camera SIGABRT, model/BPU OOM, ros2: command not found, NO_PUBKEY, GPIO permissions, under-voltage, SSH timeouts) to exact commands and official doc links, with safe/moderate/dangerous command risk tiers. - S-series flashing: Guides xburn DFU/Fastboot flashing of S100/S100P/S600 with correct product/media settings (S100=emmc, S600=ufs) and per-board DFU entry sequences. - Use Case: A user reports "ros2 launch fails with /opt/tros/humble/setup.bash missing on my S600" — the Skill corrects the premise (S600 is Ubuntu 24.04/Jazzy) and directs them to source /opt/tros/jazzy/setup.bash. ## Quick Start Ask the agent to identify which RDK board you are connected to and diagnose the error message you are seeing before making any system changes.
