dual-controller-sync

I2C debugging between dual ESP32 controllers involves checking 7-bit addressing consistency, verifying wiring, and monitoring timing synchronization. This Skill provides step-by-step verification checks and side-by-side monitoring of both the main controller and ESP32-CAM module to diagnose address conflicts, timing issues, and handshake failures.

Build and monitor both controllers using dedicated make commands: build main with `make robocar-build-main` and camera with `make robocar-build-cam`, then monitor each on separate ports using `make robocar-monitor-main` and `make robocar-monitor-cam`. This allows you to compare output side-by-side and identify synchronization problems.

Synchronization relies on consistent 7-bit I2C addressing, verbose logging from both devices, and handshake/timing mechanisms that enforce reliable command and data exchange. The Skill guides you through configuring these mechanisms to resolve timing conflicts and address mismatches across the dual-ESP32 setup.

Yes. This Skill applies to any dual-ESP32 setup requiring I2C diagnosis. It enforces consistent addressing, provides monitoring workflows, and includes handshake verification steps applicable beyond robocar projects to general ESP32-to-ESP32 communication troubleshooting.

The deployment workflow sequences building both controllers, flashing each to its respective module, then running dual monitors on separate serial ports to verify end-to-end operation. This ensures both the main controller and camera module initialize correctly and exchange data without I2C conflicts.