Software I2C for 36 channels - Will it work?
Posted: Thu Oct 19, 2017 12:22 pm
Good day gentlemen.
In dealing with 36 simple I2C devices with conflicting base addresses, I need to assign each to a dedicated I2C port.
I can do this in software mode, though unsure of any gotcha's if configuring a PIC33EP512MU814 running full-smoke, to serve 36 separate ports/devices? Incidentally, the PIC need serve no other purpose other than as slave I2C interface to a driving master.
I'm aware of mux switches (etc), each adding line capacitance that I'd prefer to avoid, though just as-well to throw an on-hand PIC at it - if it will work? I can also add that transactions with each target device will be performed and completed separately, so no need to handle asynchronous messages from targets (etc).
All comments appreciated.
Thanks and all the best,
Brendan
In dealing with 36 simple I2C devices with conflicting base addresses, I need to assign each to a dedicated I2C port.
I can do this in software mode, though unsure of any gotcha's if configuring a PIC33EP512MU814 running full-smoke, to serve 36 separate ports/devices? Incidentally, the PIC need serve no other purpose other than as slave I2C interface to a driving master.
I'm aware of mux switches (etc), each adding line capacitance that I'd prefer to avoid, though just as-well to throw an on-hand PIC at it - if it will work? I can also add that transactions with each target device will be performed and completed separately, so no need to handle asynchronous messages from targets (etc).
All comments appreciated.
Thanks and all the best,
Brendan