• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 152 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC1310: CC1310 I2C, start & stop bits manually control

YZ
Intellectual 1980 points
Part Number: CC1310

Hi Team,

My customer has a requirement to control I2C start & stop bits manually by themselves, because they have a special I2C peripheral needs to get a stop bit during its initialization. 

While by I2C_transfer() it is not possible to send a stop bit first. So is there anyways they can try manually to send a stop bit first?

BTW, what does "void* I2C_Params::custom" do since I can't find any examples?

And how does I2C_control() work, also not so many information?

Are above two related some customization I2C functionalities customer can use?

Thanks!

  • 0
    TI__Guru 58425 points

    Hi Yan,

    The I2C driver does not have this flexibility today, your customer would likely need to revert to using the DriverLib APIs to write their own custom routines. The I2C driver could serve as a good template on the steps required.

    In regards to the "custom" parameter, this is a way for the device specific implementations to support features on top of that defined in the top-level API description (I2C.h), Same goes for I2C_control(), What you can do with this is up to the device specific implementation which means it is part of the I2CCC26XX.h documentation. In this case, I2C_control() has no functionality at all and there is really no custom parameters either.