felias-fogg
commented
8 years ago Hi Scott,
I wrote the lib mainly to be a very light weight solution for ATtinys which run on a 1MHz clock. So it it uses the minimal amount of code and all the ports are hardcoded (through defines). Lifting this to multiple buses is probably very difficult. For two buses, I would just duplicate the code with different identifiers.
But why would you like to do it? Since everything is based on polling the I/O lines, there won’t be any advantage for serving parallel buses. Do you have chips that have identical I2C addresses that you cannot change?
If you have more memory to spare, you might probably want to play around with the high-level libraries implementing I2C in software. I believe, they also do not support multiple buses, but it might be easier to extend them to cater for that.
Best, Bernhard
Am 28.06.2016 um 21:23 schrieb Scott C. Lemon notifications@github.com:
Thank you for the great library ... it works as advertised! :-)
I'm now looking at a situation where I need to support multiple I2C buses ... so I need multiple "masters". Have you at all considered what changes would have to be made to support multiple instances? What could remain shared, and what has to be renamed, or changed in definitions?
Looking at the code, I can see it's not trivial ... however I need to make this work. I've started to review the code and attempt to determine all of the places that would require changes. I am also not sure if there is an easy way to define "arrays" of pins ... or some other method that might be the best direction to attack this?
Thoughts? Suggestions?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
MarkJeronimus
Thank you for the great library ... it works as advertised! :-)
I'm now looking at a situation where I need to support multiple I2C buses ... so I need multiple "masters". Have you at all considered what changes would have to be made to support multiple instances? What could remain shared, and what has to be renamed, or changed in definitions?
Looking at the code, I can see it's not trivial ... however I need to make this work. I've started to review the code and attempt to determine all of the places that would require changes. I am also not sure if there is an easy way to define "arrays" of pins ... or some other method that might be the best direction to attack this?
Thoughts? Suggestions?