Reading the AD5696R

Kevin_at_Vubiq

on Mar 7, 2018

I am investigating a problem we are having with reading from the AD5696R. When following the "read operation" procedure, the value returned is nearly always 0x91. I attached a Corelis BusPro-I I2C monitor to the EVAL-AD5696RSDZ and performed a read, and noticed that it did not seem to be following the procedure. When reading from DAC C, the command following the first address byte was 14, not 04 as I understood from the datasheet. Can you explain why I am seeing a different read operation than is described in the datasheet?

Parents

0 musach

on Mar 9, 2018 1:22 AM
Hi,

the date code #713 refers to a unit before the device was fixed.

http://www.analog.com/media/en/PCN/ADI_PCN_16_0138_Rev_-_Form.pdf

This may explain why you cannot communicate with the device.

The faster option to get latest silicon is by requesting samples thru the ADI web page.

Answering your question, the DS recommends a NOP command BUT, as the command is just to point to the register, and the restart condition aborts the command, the command transmitted is irrelevant.

Best Regards,

Miguel
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 musach

on Mar 9, 2018 1:22 AM
Hi,

the date code #713 refers to a unit before the device was fixed.

http://www.analog.com/media/en/PCN/ADI_PCN_16_0138_Rev_-_Form.pdf

This may explain why you cannot communicate with the device.

The faster option to get latest silicon is by requesting samples thru the ADI web page.

Answering your question, the DS recommends a NOP command BUT, as the command is just to point to the register, and the restart condition aborts the command, the command transmitted is irrelevant.

Best Regards,

Miguel
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

No Data