9 ms·
(about the number of slaves) > " ...and I'm sorry to say, the answer is way lower than 127" 127 is a really high number that nobody should encounter in real d
by squarefoot 6y ago
(about the number of slaves)
> " ...and I'm sorry to say, the answer is way lower than 127"
127 is a really high number that nobody should encounter in real design situations. I2c was conceived for communications between chips on the same board; it is extremely unlikely that one could fit that many chips on a board, all talking i2c with each other on the same bus. I2c switch chips also can be used to split the bus in multiple parts so that only a few chips at a time are physically connected to the bus. Example: the PCA9548 from TI, NXP and possibly others.
https://www.nxp.com/products/interfaces/ic-spi-serial-interface-devices/ic-multiplexers-switches/8-channel-ic-bus-switch-with-reset:PCA9548A https://www.nxp.com/products/interfaces/ic-spi-serial-interf...
- bagels 6y agoOne person's unlikely is another person's design requirement.
- airhead969 6y agoExactly. "Edge" cases. The arrogance of assumptions about unknown requirements and deployments without asking enough users/customers. Sometimes, there are obscure features and software but damn important (i.e., safety, banking, finance, government, military, healthcare, etc.), which is why apparent popularity is a nearly meaningless when deployment could be unknowingly ubiquitous. --- "No one will ever need that code, so let's remove it." "Aaaah, what did you do!? My SCADA products for a nuclear power plant no longer work!"
- baybal2 6y agoNot so uncommon use case is many identical IC devices, like sensors, or GPIO expanders on the same board.