EVAL-ADAU1467 I2C communication

Should it be possible to use i2c instead of spi when programming the eval board with USBi?

There are no problems using spi. However, in my final application, an mcu will program the dsp using i2c, so it would be great to test that out on the eval board. I have tried to set the dsp address in the USBi tool to i2c 0x70. Executing the program generates usb communication failure, suggesting either missing hardware, or cable failure (none of it is correct since spi works). Is there some switch on the eval-board that must be activated in order to switch from spi to i2c?

If possible, my next move would be to attach the mcu i2c lines to the Control Port header on the eval board.



Additional info 2018-11-22:

Have successfully been able to communicate using i2c with the dsp on my eval board. Connected header J1:5,7,10 as data, clock and ground to an mcu. i2c address to use is 0x76 (probably the unused pull-ups on the spi lines). i2c lines (some times) require additional pull-ups in order to function properly. I have also an RPi connected on the same i2c lines. So far, the dsp does only respond (answer with ACK) when the RPi is turned on. Therefore, I have concluded that it's the pull-ups on the RPi i2c lines that do the "magic". I'm puzzled - have disconnected the RPi and the i2c still worked this morning. 

Have used soft reset as test command. Also successfully dowloaded the firmware using default_download() (as explained in here). All delay requests were implemented with the dealy function of the mcu. Used 10ms as default delay (the PLL max lock time).

Also connected my logic analyzer to the output from the USBi. Wanted to see what the board sends when requested to use i2c in SigmaStudio (4.2). However, did not detect any signals, not even a clock on any of the lines.

some additional notes about i2c
[edited by: alexjaw69 at 8:57 AM (GMT -5) on 23 Nov 2018]