MissionLab provides a first-class environment for embedded development and robotics:
Goal: Plug in a board, CARINA recognizes it, tooling works, no fighting permissions.
CLI-first toolchain for embedded development.
Packages: arduino-cli, PlatformIO, avrdude, dfu-util, openocd, minicom, screen, picocom, cmake, ninja-build
sudo carina profile apply missionlab-embedded
Minimal ROS2 development tooling.
Packages: ros-dev-tools, colcon, python3-rosdep, python3-vcstool
sudo carina profile apply missionlab-robotics
Note: ROS2 is NOT auto-sourced. See
/etc/carina/ros2-setup-hint.shfor setup instructions.
carina missionlab status
Reports toolchain availability, user group membership, serial port access, and udev rules status.
carina missionlab devices
Scans serial ports, USB development devices, video capture devices, and GPIO/I2C/SPI interfaces.
MissionLab uses udev rules for non-root device access:
/dev/ttyUSB*, /dev/ttyACM*)Two rule files installed:
/etc/udev/rules.d/99-carina-serial.rules — Serial device permissions/etc/udev/rules.d/99-carina-usb.rules — USB device permissionscarina missionlab status to verifycarina missionlab devicesarduino-cli board list
# or
platformio device list
"Permission denied" on serial port:
groupssudo usermod -aG dialout $USERcarina missionlab statusDevice not detected:
lsusbls -la /dev/ttyUSB* /dev/ttyACM*ls /etc/udev/rules.d/99-carina-*sudo udevadm control --reload-rules && sudo udevadm triggerarduino-cli not finding boards:
arduino-cli core update-indexarduino-cli core install arduino:avrarduino-cli board listRelated: Embedded/Robotics Guide, Features