LP-CC1352P7: LP-CC1352P7: I2C problem with some slave devices

Eden Cohen

Prodigy 60 points

Part Number: LP-CC1352P7
Other Parts Discussed in Thread: CC1352P7, LP5562

Hi,

We upgraded from 1352P1 to 1352P7 and some devices stopped responding to I2C transactions.

Details

I am working with SDK 6.20 and a proprietary board. There are several I2C slave devices connected to the MCU.

Some of the devices answer to I2C requests without a problem.
Other devices do not answer - we get I2C_STATUS_ADDR_NACK from I2C_transfer() API.
The results are consistent and repeatable

The same board with 1352P1 (and older SDK) worked fine.

What happened in 1352P7? Please, I need an urgent solution.

over 2 years ago

0 Marie H over 2 years ago

TI__Guru* 82431 points

Hi Eden,

1) Are you using the same SDK for CC1352P1 and CC1352P7?

3) What kind of devices are the I2C slaves?

Cheers,

Marie H

0 Eden Cohen over 2 years ago in reply to Marie H

Prodigy 60 points

Hi,

On CC1352P1 I was using a very old SDK (3_40_00_02)

We are using all kinds of slave devices. Some examples: LIS2MDL, PCAL6408A, LP5562, MAX17260, BQ25890A, LSM6DSO

I think the problem is with the MCU, not the slave devices.

I attach waveforms

'bad' I2C transaction on CC1352P7

and good I2C transaction on CC1352P1

0 Eden Cohen over 2 years ago in reply to Eden Cohen

Prodigy 60 points

As you can see in the waveforms, in the 'bad' transaction there is a little toggle of SCL and SDA a long time before the actual transaction (this 'glitch' is not seen on older MCU).

Thanks,

Eden

0 Arthur R☑️ over 2 years ago in reply to Eden Cohen

TI__Mastermind 25906 points

Hi Eden,

This is a known issue, as documented here: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1102080/cc1312r-glitch-on-i2c-lines-after-upgrading-to-sdk-6-10-removal-of-pin-driver

It is now fixed in version 6.30 of the SDK.

Regards,

Arthur

0 Eden Cohen over 2 years ago in reply to Arthur R☑️

Prodigy 60 points

Hi Arthur,

With SDK 6.30 there is still a glitch on the lines when we call I2C_open().

But we were doing open/close for every I2C transfer. Now we open only one time, and the problem is resolved (without upgrading the SDK).

Thank you very much for the quick response and support.

Regards,

Eden.

Sub-1 GHz

Sub-1 GHz forum

LP-CC1352P7: LP-CC1352P7: I2C problem with some slave devices