• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 255 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LAUNCHXL-CC1352P: I2C issues

jonathan bondzie
Intellectual 260 points
Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P, BP-BASSENSORSMKII

Hi,

I'm using a LaunchXL-CC1352P-2 board to talk to an HMC5883L (3 axis digital compass)

and noticed an odd behavior with the i2c interface.

1. The initial read/write operation always returns bus busy

2. All reads/write to/from the registers succeed after the initial failure but the reads are garbage.

I hooked up the HMC5883L to an arduino and wrote quick code to see if

I can get data and that works so the compass works correctly.

I then decided to use the example app from ti i2ctmp116_CC1352P_2_LAUNCHXL

to see if I can read from the board temperature, below is the result from the output terminal.

Starting the i2ctmp116 example

I2C Initialized!

I2C Bus fault.
I2C Bus fault.
I2C Bus fault.
I2C Bus fault.
I2C Bus fault.
I2C Bus fault.
I2C Bus fault.

So basically the default example that comes with the board doesn't work either.

Question:

Is there something I need to do on the board (jumpers etc) to enable the I2C lines.

Thanks

  • 0
    TI__Guru* 82431 points

    Hi,

    Regarding the i2ctmp example, it's intended to be used with a boosterpack. (BP-BASSENSORSMKII Building automation sensors BoosterPack module)

    I'm not familiar with the compass you are using, I would recommend reading the documentation for this part to  double-check that you configured the i2c and sent all the necessary commands.

  • 0 in reply to Marie H
    TI__Guru**** 317180 points

    I would also recommend monitoring the I2C line with a scope to see what happens on the actual interface. A common issue problem I have seen with I2C is that the slave address in not provided correctly to the driver. Search the forum and look into other posts covering the I2C interface. 

  • 0 in reply to TER
    Intellectual 260 points

    I know the address is correct because I had the device working using an Arduino board. I'll hook it up to a scope and see what the lines look like as far as the clock and data.

    Thanks