On the chipKIT Uno32, uC32, DP32 and WF32, the interrupt is raised for every byte in I²C slave mode. The corresponding MCUs are the PIC32MX320F128, PIC32MX340F512H, PIC32MX250F128B and PIC32MX695F512L. I don't know for other boards / MCUs as I've only tested with those I own.
This bug/feature was confirmed at chipKIT forum and there's a related issue at the GitHub repository
Unfortunately, the question hasn't received any official answer yet. The suggested work-around isn't reliable as it requires to be set for every I²C master.
Question
ReiVilo
On the chipKIT Uno32, uC32, DP32 and WF32, the interrupt is raised for every byte in I²C slave mode. The corresponding MCUs are the PIC32MX320F128, PIC32MX340F512H, PIC32MX250F128B and PIC32MX695F512L. I don't know for other boards / MCUs as I've only tested with those I own.
This bug/feature was confirmed at chipKIT forum and there's a related issue at the GitHub repository
Unfortunately, the question hasn't received any official answer yet. The suggested work-around isn't reliable as it requires to be set for every I²C master.
Is it a bug?
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.