Shared communication buses
I2C panic: one bus can contain several possible causes
An I2C reference says communication on a named bus became invalid or unavailable. A bus number does not map to one universal component across models.
Log fields to extract
- I2C bus number and full panicString.
- Every endpoint or sensor named nearby.
- Exact model identifier and any simultaneous missing channels.
Build the bus map
Use authorized schematic or board information for that precise model to list the devices, pull-ups, supplies and connectors sharing SDA and SCL.
Safe isolation sequence
- Inspect external connectors and flexes.
- Measure line resistance and expected voltage using the correct reference.
- Disconnect or substitute peripherals one at a time where the model permits.
Alternative fault locations
- A peripheral holding the shared line.
- Missing pull-up voltage or damaged filter.
- Open trace, connector damage or controller-side fault.
Interpretation limit
The panic narrows the communication route; it cannot distinguish every device on the bus without model-specific isolation and measurement.