ADAU1467 I2C parameter memory basic question

David@IA Question

Nov 1, 2023 00:00

Ahoy there,

I have a project that has a stereo mux in it, with three inputs, on my own board in selfboot mode.

I have selfboot working fine, tested with a simple s/pdif through and a few controls.

I want to switch between the inputs on the mux. Now when I do it in SigmaStudio, capture shows an address of 0x0060, and data of 0x00 0x00 0x00 0x00, with the last two changing between 0x00, 0x02 and 0x04

So I do an I2c start, then send 0x00, 0x60, then 0x00 0x00 0x00 0x00 (or 02 or 04) then an i2c stop, and it's having no effect.

Is the capture a direct reflection of the i2c commands I need to send? According to the .params file, the address is 96, which translates to 0x60, so that seems correct.

Or are there other steps that aren't reflected in the capture window?

Oh, and I'm successfully communicating with other devices on the I2C bus.

Thanks

~David

Edit Notes
Corrected some info

[edited by: David@IA at 3:48 AM (GMT -4) on 2 Nov 2023]

Thread Notes
Moved from How to Use EngineerZone to SigmaDSP Processors & SigmaStudio Dev. Tool on Thursday, November 2, 2023 1:22:53 PM

Report

Harishgowtham Reply

Nov 2, 2023 00:00

Hello David,

Make sure that the I2C device address is given correctly. Below is the table.

The ADDR0 and ADDR1 are those pins who choose the device address. It has different combinations.

If you are using our Eval board, then please note this. In our ADAU1467 Eval board, the ADDR0 is tied to IOVDD. which represents a binary one (HIGH) always. So, by connecting ADDR1 to GND ('0' - LOW) OR connecting ADDR1 to 3.3v ('1' - HIGH), You can get the addresses 0x72 (ADDR1 - LOW) and 0x76 (ADDR1 - HIGH) respectively.

If you are using your own hardware, then make sure the correct address is given.

If addresses are correct and still facing an issue, then if you have a scope then try capturing the I2C signal and send it over. Attach your hardware schematic if possible.

Regards,

Harish

Report

David@IA Reply

Nov 21, 2023 00:00

Ahoy there.

I did eventually find my problem, the data address in my code wasn't sending correctly. Seems like I was using the correct information. The chip address was working fine. Cheers for the reply.

~D

Report