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.

I2C / TWI Issue with TLV320AIC3107

Other Parts Discussed in Thread: TLV320AIC3107

I'm using the Atmel SAMG53 along with the TLV320AIC3107 Codec. The 3107 has been attached to a custom breakout board, and I have verified all of its connections are sound. 

The TWI interface, which is Atmel's equivalent of I2C, seems to be doing it's job, and timings are within the tolerances stated in the 3107 datasheet, however - I am not getting an ACK on the line when I use Atmels twi_probe, nor anything but errors with master reads/writes.

The Reset has been drawn low for longer than required by the datasheet, prior to performing any reads/writes.

The only variable that may be a problem, although I don't see why it would be is that the Speaker SS/DD are not hooked up, since I don't plan on using them. The rest of the core and I/O are powered.

The data and clock lines have been verified using a scope, and everything is working from that perspective.

Any suggestions? 

I have also contacted Atmel. 

  • Hello Donald,

    It seems like you are doing everything right here. As long as the I2C lines meet the spec of the datasheet and the device is properly powered the device should ack. You are correct that you don't need speaker SS/DD as that is just for the class-D output.

    My only suggestion would be to try to take the I2C lines from the atmel chip and connect them to an EVM and see if it works. If it doesn't then this suggests that it would be an issue on the atmel side when writing the I2C lines. If it does, then it would be an issue on the AIC3107 side.

    Do you have access to an EVM?

    Please let me know if you continue to experience this issue and after you hear back from atmel to see if I can find some alternative suggestions,

    Thank you for the post,

    Nate

  • Hi Nate, 

    thanks for the swift response. The problem was with my GPIO on the Atmel not truly pulling the RESET back up.

    Thanks!

  • My Pleasure! I'm glad to hear it was a quick any easy debug.

    Best of luck in your development :)