This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/MSP-EXP432P401R: I2C Sample Code of Driver API is not working

Part Number: MSP-EXP432P401R

Tool/software: Code Composer Studio

Hi,

I am working with the MSP-EXP432P401R developement board and want to test the I2C part using Driver API. I have 2 boards so one i'm configuring as a master and other as a slave. I tried using the available examples of Driver API for I2C and these examples are i2c_master_w_multibyte-master_code in one device and i2c_master_w_multibyte-slave_code in another device. both device SDA and SCL pins are connected with each other using external pull up resistor.

Problem in above experiment is that Master device sending the data and code is going to I2C ISR but Slave device is not receiving anything and keep waiting to receive some data. 

is there any correction in example code which we need to do? or i tried searching all over but couldn't get the solution.

NOTE: i tested without the Driver library, that means i tried with the register level example code for master and slave. that has worked fine for both slave and Master.

  • Hello,
    Can you provide the revision of the hardware and the driverLib that you are using? I will look into the revision history, but there may have been a change associated with this post/thread:

    e2e.ti.com/.../2117452

    Thanks,
    Chris
  • Pritesh,

    I just ran the I2C example between two MSP432 launchpads and it seems to be working fine.   Perhaps you can double check your hardware setup and ensure that:

    GND is connected between both devices.

    the pull-up resistors (about 10kOhm) are in place and the SDA/SCL lines are connected properly:

    I also found that the boot order seems to matter in this particular case, the Master must turn on after the Slave in this example.  Master will stop trying to send after the second NAK is received due to the way the example is written.

**Attention** This is a public forum