Hi Toby, Thank you for looking at MSP for your solution. Regarding your questions: Devices with eUSCI can implement multiple addresses by using 4 address registers (UCBxI2COA0-UCBxI2COA3), and/or by using the address mask functionality (UCBxADDMASK). However, the module doesn't check for arbitration when responding as a slave. As you probably know, the I2C spec requires arbitration when acting as a Master, but not as a slave; so the eUSCI was designed for I2C compliance and it doesn't support this feature. We are fully aware of this limitation and we are planning to fix it in future devices, but we don't have anything in the MSP roadmap today. One workaround could be to bit-bang the response for those particular addresses (i.e. when the device detects an ARP request). Unfortunately, we don't have any examples as of today. I hope this helps and please let us know if you have any additional comments or questions. Regards, Luis R
↧