Timeline for Strange I2C Behaviour
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2015 at 3:47 | history | tweeted | twitter.com/#!/StackElectronix/status/615003499596791808 | ||
| Dec 7, 2012 at 9:05 | vote | accept | njt | ||
| Dec 6, 2012 at 17:32 | comment | added | Gustavo Litovsky | Just a comment on the signals. Is see crosstalk and ringing. Though the hardware is "proven", I suggest at some point if possible to clean it up. Wouldn't hurt. | |
| Dec 6, 2012 at 16:50 | answer | added | Adam Lawrence | timeline score: 2 | |
| Dec 6, 2012 at 15:45 | history | edited | njt | CC BY-SA 3.0 |
added i2c library call
|
| Dec 6, 2012 at 15:43 | comment | added | njt | @Madmanguruman - i'll post my setup call above, thanks | |
| Dec 6, 2012 at 15:17 | comment | added | Adam Lawrence | Please post the I2C peripheral configuration code, be it your setting of the registers directly or your OpenI2C() library call. ACKing on every address does indeed sound like general call. Is there a way to cut power or otherwise isolate the DSP from the I2C bus? | |
| Dec 6, 2012 at 14:11 | history | edited | njt | CC BY-SA 3.0 |
added 661 characters in body
|
| Dec 6, 2012 at 14:06 | comment | added | njt | @TDL - PIC external clock is at 8mhz, so should be OK as this is an existing hw design. | |
| Dec 6, 2012 at 14:05 | comment | added | njt | @vicatcu - just tried specifically disabling general call in the config bits for the bus.. nothing. | |
| Dec 5, 2012 at 22:44 | comment | added | TDL | Make sure that the processor is running at fast enough. What speed is the PIC running at? | |
| Dec 5, 2012 at 16:38 | comment | added | vicatcu | it sounds like you may inandvertently be doing general call? | |
| Dec 5, 2012 at 16:33 | comment | added | Gustavo Litovsky | Do you have a datasheet of the ICs and maybe a scope grab? | |
| Dec 5, 2012 at 16:29 | history | asked | njt | CC BY-SA 3.0 |