Timeline for I2C and SPI ,if they share same connection , is there confilict or not
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2012 at 23:36 | comment | added | Scott Seidman | If the SPI needed to be fast, I'd probably go out of my way to find a controller with two MSSP's, or work harder to get peripherals that used the same bus. I just don't like the idea bit banging I2C, especially when the peripheral might be clock stretching (though it shouldn't have much of a reason to if your rate is bit-bang limited) | |
| Nov 28, 2012 at 23:32 | comment | added | Chris Stratton | @ScottSeidman yes, that would be logical, unless the SPI needs to be utilized a lot more or at a higher clock rate. | |
| Nov 28, 2012 at 23:14 | comment | added | Scott Seidman | Bit banging SPI is easier for me than bit-banging I2C, if you need to make that choice. | |
| Nov 28, 2012 at 22:25 | history | edited | Chris Stratton | CC BY-SA 3.0 |
edited body
|
| Nov 28, 2012 at 20:19 | history | answered | Chris Stratton | CC BY-SA 3.0 |