I'm still also unclear if I'm doing something wrong on the slave=20
(PIC1825K42) side, but that's MCC-generated code, which is very=20
undocumented.  I was told that I pretty much need to figure that out=20
from the header file comments.
Either way, nothing that the slave does should cause the master to=20
crash/reset.

My local FAE has tried to convince me that the MCC/harmony/libraries=20
would save me time and aggravation, but I'm far from convinced at this=20
point.  At least with my own code, I know where to look for issues.

Cheers,
-Neil.



On 10/15/2018 3:49 PM, Harold Hallikainen wrote:
> I have always talked directly to the I2C port instead of using the
> library. Also, for me to get I2C to work, I generally need a logic
> analyzer to watch the bus and a debugger for the PIC. It's very difficult
> for me to get I2C working without the debugger and logic analyzer (may be
> impossible... never tried!).
>
> Not much help...
>
> Good luck!
>
> Harold
>
>
>

--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.