sl-jetson cea3eaff97 cleanup: Remove all Mamba/STM32/BlackPill references — ESP32-S3 only

- Renamed mamba_protocol.py → balance_protocol.py; updated all importers
- can_bridge_node.py rewritten to use balance_protocol.py API (ESP32-S3 BALANCE)
- test_can_bridge.py rewritten to test actual balance_protocol.py constants/functions
- All STM32/Mamba references in Python, YAML, Markdown, shell scripts replaced:
  * Hardware: MAMBA F722S → ESP32-S3 BALANCE/IO
  * Device paths: /dev/stm32-bridge → /dev/esp32-io
  * Node names: stm32_serial_bridge → esp32_io_serial_bridge
  * hardware_id: stm32f722 → esp32s3-balance/esp32s3-io
- C/C++ src/include/lib/test files: added DEPRECATED header comment
- Covers: saltybot_bridge, saltybot_can_bridge, saltybot_can_e2e_test,
  saltybot_bringup, saltybot_diagnostics, saltybot_mode_switch, and all
  chassis, docs, scripts, and project files

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-04 08:56:09 -04:00

2.4 KiB

Raw Blame History

SaltyLab Firmware — Agent Playbook

Project

Self-balancing two-wheeled robot: Orin Nano Super, 2x VESC (IDs 68 left / 56 right), ESP32-S3 BALANCE, ESP32-S3 IO.

Team

Agent	Role	Focus
sl-firmware	Embedded Firmware Lead	ESP32-S3/ESP-IDF, USB CDC debugging, SPI/UART, Arduino/ESP-IDF, esptool.py
sl-controls	Control Systems Engineer	PID tuning, IMU sensor fusion, real-time control loops, safety systems
sl-perception	Perception / SLAM Engineer	Jetson Nano, RealSense D435i, RPLIDAR, ROS2, Nav2

Status

USB CDC TX bug resolved (PR #10 — DCache MPU non-cacheable region + IWDG ordering fix).

Repo Structure

projects/saltybot/SALTYLAB.md — Design doc
USB_CDC_BUG.md — USB peripheral conflict details
TEAM.md — Team roles specification

Branch Strategy (issue #28)

Variant branches

Branch	Purpose
`saltylab`	Stable — SaltyLab 2-wheel balance bot (promoted from saltylab-dev)
`saltylab-dev`	Integration — SaltyLab balance bot; agents target this branch
`saltyrover`	Stable — 4-wheel rover variant
`saltyrover-dev`	Integration — rover variant
`saltytank`	Stable — tracked tank variant
`saltytank-dev`	Integration — tank variant
`main`	Shared code only (IMU drivers, USB CDC, balance core, safety)

Rules

Agents branch FROM <variant>-dev and PR back TO <variant>-dev
Shared/infrastructure code (IMU drivers, USB CDC, balance core, safety) goes in main
Variant-specific code (motor topology, kinematics, config) goes in variant branches
Stable branches get promoted from -dev after review and hardware testing
Current SaltyLab team works against saltylab-dev

Git Workflow

Branch naming: <agent>/<slug> (e.g., sl-firmware/usb-cdc-fix)
For shared code targeting main: <agent>/bd-<id>-<slug>
Before every push: git fetch origin && git rebase origin/<base-branch>
Gitea: gitea.vayrette.com/seb/saltylab-firmware

Communication

Report progress to max via MQTT: AGENT_NAME=<agent> ~/agent-mqtt/agent-send max "<message>"
Check inbox: ~/agent-mqtt/agent-read 2>/dev/null | tail -15
Prioritize messages from max (PM)

Beads (Task System)

cd /Users/seb/AI/saltylab-firmware
br list                    # List open beads
br update <id> --claim     # Claim a bead
br close <id> --reason "Done. PR #N"
br comment <id> "message"

2.4 KiB Raw Blame History