Other Parts Discussed in Thread: TAS5825P
I am attempting to do end system integration with a TAS5825P design using the exported header file from Pure Path Console and am running into a problem where the dumped config file does not seem to work properly.
I can connect the EVM to my prototype board, communicate to the on board TAS5825P and configure it properly. When done this way I can observe that the Hybrid PWM mode is operating correctly; I can see PVDD being modulated when needed and the power consumption drops.
When I dump the settings to a configuration file and have the application MCU load the settings the amplifier works and plays audio but the Hybrid PWM mode does not work correctly. The boost amplifier swings up to the max PVDD setting (16V) and just stays there.
I've used a logic analyzer to observe that the implementation of the I2C drivers appears correct and that the MCU is outputting the correct I2C commands according to the contents of the dump file. The delays are all correct and the values all match what is defined in the dumped file.
Is there anyway to inspect the dumped header file to verify it's been generated properly? I would really like to have this process flow work where we can export settings direct from Pure Path Console into our MCU firmware but it seems I'm going to have to manually go through the sniffed, "correct" implementation in order to figure out the proper initialization sequence which really makes using this device unattractive.