Other Parts Discussed in Thread: PCM1753
Hello TI team,
I have been working with DS90UB949-Q1 and an audio DAC PCM1753. The application is such that, the user's laptop is connected to the serializer using an HDMI connection and the display of the laptop is transferred to the serializer and then to the DeSer via LVDS. Along with the video of the user's laptop, the HDMI is capable of sending out the audio of the laptop to the Serializer and then the Serializer is sending out the HDMI audio to the audio DAC PCM1753.
As, I am able to get the audio from the laptop and from the audio DAC, but the problem is that the audio is too noisy, so I want it to remove the noise.
Here are my points and connections to the system -
1. Using the 0x55 register of the Serializer, I am enabling the bit [6] of this register to get the HDMI audio from the Serializer, then the Serializer audio output is sent to the DAC PCM1753.
2. Pins 33, 34, and 35 of the Serializer are connected to pins 3, 1, and 2 of PCM1753.
3. The PCM1753 is used on the default settings, so the SCK of PCM1753 is 27 MHz, and the sampling frequency is 44.1 kHz.
4. In the EDID of the Serializer, we have enabled the audio part and added the support for 16-bit and 24-bit along with a 44.1 kHz data rate.
5. When the audio is out from the DAC 1753, I used my windows laptop and set the audio of this device to 16-bit and 44.1 kHz, but the problem is that when I see the clock output from Serializer, I noted a few things.
a. The BCK clock is at 2.82 MHz and the LRCK clock is at 44.1 kHz, but according to the audio standards, for 16-bit and 44.1 kHz data rate, the BCK clock should be 1.411 MHz, as stated in the below audio standards given in Serializer datasheet.
Can you please share your thoughts that how can make the Serializer BCK clock at 1.411 kHz instead of 2.82 MHz?
Here are my questions:
1. Is there any registers to set the bit rate/ data rate of HDMI audio in Serializer?
2. Is there any registers to set the BCK clock coming from HDMI audio from Serializer?
Please solve the issue.
Thanks,
Vivek Karna