Other Parts Discussed in Thread: MSP-EXP430FR2433
Our customer is evaluating I2C slave function with MSP-EXP430FR2433 LanchPad (sample code: msp430fr243x_eusci_i2c_standard_slave.c or msp430fr243x_euscib0_i2c_11.c). customer is connecting this LanchPad to RaspberryPi3(I2C master). However, it does not seem it worked.
When the 1-byte Read operation is executed by Raspberry Pi, customer said that MSP430 seems to drive Low on CLK line and freeze. Therefore, I received some inquires as follows. (I suppose MSP430 may do "Clock stretching".) Can I have your expert's advice/comments on them, please?
- Does the interrupt affect the judgment of returning ACK?
- Even if the I2C interrupt flag is not cleared, Is it possible to do I2C communication? For example, although customer is referring to msp430fr243x_euscib0_i2c_11.c, Is it not necessary to clear "UCSTPIFG"?
- Regarding the data-stored timing of "UCB0TXBUF", if it is set at the beginning of the main(), does it always return a fixed value?
I'm requesting customer to refer User's Guide(220.127.116.11 Slave Mode) and I'm requesting customer to capture this I2C(SCL/SDA) access