I've got the beginnings of an I2C comms routine between a pair of MSP430 devices: F5529 as master and an F2013 as slave. Ultimate design goal: The slave is to both receive parameter settings from the F5529, as well as report (for debugging purposes) SD16_A values.
For starters I grabbed the I2C Scanner sketch on the F5529 side, and I have a TI sample program (msp430x20x3_usi_15.c) running on the F2013. Running the F5529 code in CCS 6, and the F2013 code in IAR I see that there is communication between the two devices with the F2013 ISR called multiple times and stepping through its switch/case structure. The two state machines communicate until the F2013 goes into LPM0 waiting for an interrupt from the F5529.
I suspect that the F2013 is responding in an unexpecte fashion and at that point the F5529 goes into an endless loop waiting for a response, and the F2013 is also waiting for a response.
So, clearly written tutorial suggestions on I2C would be appreciated. I'll figure out my coding problems, but I'm still not quite clear on the overall structure of the call/response transactions in I2C.
TIA!
bob
PS - I'm seeing that after altering the state for the F2013 USICTL0 the comm stops. So, reading to do on the USI control, which is far less sophisticated than the controller for the F5529. 