![]() ![]() The reason I was hoping to do things the way I originally envisioned was to achieve the following characteristics: I think that probably what would need to be done to support this use case is to configure both MCUs as i2c slaves, and then use a bit-banged approach (with some type of arbitration) whenever either of them wanted to initiate an i2c data suggestions guys. It looks like i2c could theoretically work like this, but that the libraries supporting it in Arduino and Particle OS were not designed to account for this use case. I’ve done this before with a CAN communication network (where any node can initiate a transmission asynchronously). I want comms between the Electron and ATtiny to be such that either one of them can initiate communication at an undefined point in time (so that I don’t have to keep polling the ATtiny to see if new data is available). ![]() My use case is that I have an Electron that needs to communicate with an ATtiny over an i2c interface. I’m not sure that the standard i2c implementations (that don’t account for flipping between master/slave roles) will work for me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |