CDCE6214-Q1: I2C communication is not working

Francisco Moya

Prodigy 10 points

Part Number: CDCE6214-Q1

Tool/software:

I have the CDCE6214-Q1 device in one board and I can not access by I2C to any register to configure it.

When I start the I2C communication the CDCE6214-Q1 returns a NACK for the first start with the slave address.

I test with the default address (0x68) and with the fallback address (0x67) without success.

I have configured the device like:

HW_SW_CTRL set to High
REFSEL set to ground with a resistor of 10K
PDN set to High
PRIREF not connected
SECREF connected to an oscilator
GPIO1 and GPIO4 not connected
GPIO2 and GPIO3 connected to an I2C, with PullUps connected to VDD_REF
OUT0 not connected
OUT1, OUT2, OUT3 and OUT4 connected to different devices of the board.
DAP connected to Ground.

3 months ago

0 vicente flores prado 3 months ago

TI__Genius 17451 points

Hi Francisco,
To enter fall back mode REFSEL must be left floating as well as HW_SW_CTRL

Regards,

Vicente

0 Francisco Moya 3 months ago in reply to vicente flores prado

Prodigy 10 points

Hi Vicente,

That means that the only way to use the I2C is in fall back mode?

I want to configure the device without enters in fall back mode, is this possible?

Regards.

0 vicente flores prado 3 months ago in reply to Francisco Moya

TI__Genius 17451 points

Hi Francisco,

Francisco Moya said:
That means that the only way to use the I2C is in fall back mode?

No - the device has two intended modes of usage which are Pin mode & I2C mode.

You can accidentally disable the I2C interface when you program the EEPROM to be in pin mode which effectively leaves the user with no way to to communicate with the IC via I2C - this is why fall back mode exists. It allows users to force enable I2C communication to overwrite the EEPROM. Thus you to summarize you can have the I2C interface enabled (I2C mode) without having to enter fall back mode.

Regards,

Vicente

Clock & timing

Clock & timing forum

CDCE6214-Q1: I2C communication is not working