The goal is to start up the TAS5751MEVM board from an external I2C master, to control it i.e. change volume settings and so on, to simulate the whole end system, without the purepath daughterboard.
In one situation the external I2C master is connected to connector J3.
According to the documentation the I2C master should write the configuration registers that are retrieved from the Purepath evaluation console to make it boot.
After doing so the error register shows zero's, so it seems that the TAS5751MEVM accepted the configuration, but it does not boot.
Secondly, the TAS5751MEVM has been connected to a break out board, that connects the external I2C master, I2S audio, Reset, PDN, ADR/Fault (to set I2C address to 0x54), to try to simulate the whole end system, without the purepath daughterboard. It's expected that the board starts up when the same configuration which is loaded via the external I2C master, but it does not.
So the TAS5751MEVM in no circumstances starts up, while the error register shows zero's.
Reconnecting the purepath daughterboard again to the TAS5751MEVM , starting up the purepath console, the TAS5751MEVM plays audio again.
Also the volume of the TAS5751MEVM can be controlled via the external I2C master that is connected to connector J3.
Q1: Why can the TAS5751MEVM not be started from an exernal I2C master, since no possible errors can be determined.
When the Purepath console is started the software interface mentions that the TAS5751MEVM is connected (green dot).
How does the daughterboard determines that a TAS5751MEVM is connected? It appears that there is hidden communication.