CC2650:

narasimha reddy gangireddy

Prodigy 95 points

Part Number: CC2650

i2cStart();

i2cTx(0x32); //Slave address with write option

i2cTx(0x0F); //who am i register

i2cRepeatedStart(); //repeated

i2cTx(0x33); //slave address with read option

i2cRxNack(output.o);

i2cStop();

I am using LIS2DE12 ACCELEROMTER SENSOR.In above code i2c status always showing like this state.i2cstatus=0x0001, then what is the problem

over 6 years ago

0 narasimha reddy gangireddy over 6 years ago

Prodigy 95 points

Part Number: CC2650

HI Krishna,

will you share your code(i2c) with me i am facing some problems. if don't mind i will use your code as a reference.

0 YiKai Chen over 6 years ago in reply to narasimha reddy gangireddy

Guru 735685 points

Try to refer to I2C tmp007 example at dev.ti.com/.../

0 IUsedToBeARealPerson (M-W) over 6 years ago in reply to narasimha reddy gangireddy

TI__Guru 58425 points

Hi,

Status 0x0001 means TX_NACK (assuming you are using the Sensor Controller). Have you used a oscilloscope or logic analyzer to look at your I2C bus communication to see if it behaves as you expect it to (lines are pulled high in idle etc.)?

0 narasimha reddy gangireddy over 6 years ago in reply to IUsedToBeARealPerson (M-W)

Prodigy 95 points

Hi M-W,
yes,it working as expected way. state.i2cState=0x0001, receiving no acknowledgement is 1(RxNack())(in Sensor Controller).

0 IUsedToBeARealPerson (M-W) over 6 years ago in reply to narasimha reddy gangireddy

TI__Guru 58425 points

Hi Narasimha,

As per Sensor Controller documentation, 0x001 is TX NACK. As the sensor controller is the bus master, it do not receive RX ACK/NACKs, it sends sends them (thus the i2cRxAck() and i2cRxNack() functions).

As status 0x0001 follows from the TX operation and means that the other device is not responding as expected to what ever you send out. Have you verified that the address of your device is correct?

Bluetooth®︎

Bluetooth forum

CC2650: