DCM Array
- Modules
- 6, a timer and 5 peripherals
- MCU
- STM32C071C, one per module
- Bus
- I2C, fixed addresses
- Central module
- Timer and bus controller
- Board
- v6, USB-C
The Dynamic Challenge Module Array is a hardware puzzle game in the style of Keep Talking and Nobody Explodes, spread across six physical modules. Each module runs its own STM32C071C, and they talk over a shared I2C bus. A central module counts down the timer and controls the bus, and each of the other five has a fixed I2C address. I skipped dynamic enumeration on purpose: the set is fixed at six modules, so there wasn’t much reason to build addressing logic I didn’t need.
The board is on its sixth revision, with USB-C, debug, reset and boot buttons, two analog headers, and eight RGB-capable expansion connectors along its edges.
Bus faults
The failure that mattered most in practice was a module dropping off the bus mid-game and locking up the whole I2C line. One unresponsive peripheral holding SDA or SCL low, or just failing to acknowledge, can stall every other module on the bus, and an I2C topology with no dynamic recovery has nothing built in to get out of that.
So the central timer module handles faults at the bus level. It detects a stalled transaction and recovers the bus, either by clocking through the stuck peripheral or by resetting the affected line, instead of letting one module’s fault take the whole game down.
It’s a hobby build, not part of the accumulator work, but the problem underneath is the same one: keeping a shared bus reliable when any node on it can misbehave, just at hobby stakes instead of vehicle-safety stakes.