embedded-systemslisted

# Purpose Produce and review Python code for Raspberry Pi 5 edge devices running the edge service. Covers UART serial communication, picamera2 camera streaming, GPIO control, resource monitoring, and systemd service configuration. All generated code passes `mypy`, handles `MOCK_MODE` for CI, and releases hardware resources on exit. For MAVLink protocol parsing (message IDs, dialects, command sequences), compose with `mavlink-integration`. Success criteria: generated code imports without hardware attached (`MOCK_MODE=true`), passes `mypy` with zero errors, and releases every acquired resource in a `finally` block. # When to use - Writing or reviewing Python code that interfaces with RPi5 hardware (UART, GPIO, camera) - Configuring systemd services for the edge service on edge devices - Debugging hardware communication issues (serial port, camera initialization) - Implementing resource monitoring (CPU temperature, memory, throttling) on edge devices # When NOT to use - Web portal server-side TypeScript code (use `api-integration` or `code-standards`) - Infrastructure or Helm chart work (use the project's deployment workflow) - MAVLink message parsing, dialect selection, or command sequencing (use `mavlink-integration`) - Docker image building for the edge service (use `docker-build`) - Python dependency auditing (use `deps-check`) - Any Python code in the edge service that is purely MAVLink protocol without hardware driver concerns (use `mavlink-integration`) # Required