• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 63 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.

TLV320ADC6120: trouble with I2C configuration

Josh Blohm
Prodigy 70 points
Part Number: TLV320ADC6120

I have settled on a final configuration using PurePath Console 3. I used the End System Integration Tab to dump all register configurations to a .H file.

When iterating now through the registers list from a host microcontroller's I2C peripheral, the ADC6120 is not configured in the same way as with PPC3. Are there any additional reads/writes that should be done after sending over the list of register configurations? 

My I2C peripheral settings are:

I2C address = 0x4E (or 0x9C 8-bit address)
I2C clock = 400 kbits/sec

I can see all I2C transactions on the bus using a protocol analyzer so I'm confident the bus is stable. 

  • 0
    TI__Genius 11360 points

    Hi Josh,

    No it is not required for additional writes. What is the difference in configuration specifically?

    Regards,

  • 0 in reply to Daveon Douglas
    Prodigy 70 points

    I resolved my own issue. The header produced by PPC3 has a single configuration array for the combined sequence of rest, wake-up, and configure memory. 


    My initial approach was to trust this output and send the whole of the array in one burst. In doing this the device was resetting and thus did not receive a few subsequent writes while in reset. The header does have an inline comment stating this however it's not very clear that this must be done by the user. 

    My configuration persisted after adding a 1ms delay before and after reset and 16ms delay after configuration.

    Additionally, PPC3 requires user input to activate the device. This step is not included in the generated register output. After adding this step manually also I am now able to begin collecting samples from an external host SOC.