This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TAS5825PEVM: Not connecting to PPC3

Part Number: TAS5825PEVM
Other Parts Discussed in Thread: TAS5825P, CDCE913, TCA6408

Tool/software:

I have a new TAS5825PEVM that won't connect to PPC3. USB enumerates correctly for audio and it appears under the headings: Texas Instruments USB Audio Devices: TI USB Audio UAC2.0 and Sound, video, game controllers: TI USB Audio UAC2.0. There are no other connections or unmatched devices that appear when the EVM is connected.

I can send audio via the XMOS chip and it appears on the I2S outputs feeding into the TAS5825P. SPDIF if selected by the hardware toggle switch also appears when I send to it from our AP. Looking at the I2C traffic on the board during startup (when USB is connected to the EVM), the only device that gets written to is U15 the CDCE913 frequency synth. U18 the TCA6408 GPIO is never touched and the TAS5825P is held in power down.

Looking at PPC3 running the TAS5825P app, the device indicator shows it as offline. There is no settings page in the app, just "Timing and Audio Processing", "End System Integration" and "Register Map" pages. The I2C bus master on this EVM is the XMOS chip. It as if there is no connection to it from PPC3 via USB. I'm not sure if you use the XMOS as a bridge to I2C or have an API and local code running on the XMOS device, but it's definitely not talking. All hardware settings look good and supply rails are all present and correct. I am using PPC3 v3.2.1 platform build 306, I2C Master 3.0.1-alpha.3 and TAS5825P: 3.0.10. These are the latest versions available from TI. The workstation I'm using is x64 windows 10 Pro version 10.0.19045. It looks like a I2C bus master issue to me. Do you have any suggestions that might help?

  • Hi Dean,

    Can you send me a screenshot of your board when it is powered on?

    Regards,

    Ramsey

  • Hi Ramsey,

    Thanks for your help with this. Please see the snips and description in the following link:

    TAS5825PEVM - PPC3 Connection Issue snips

    Regards,

    Dean.

  • Hi Dean,

    There are a few things I want you to try. First, since you have I2C Master, try to read register 0x71 (device address is 0x98 by default) and let me know the result or if the read fails. In addition, I would try to use another micro-USB cable as a sanity check. If you have a different audio EVM that is known good, I would check to make sure the cable can communicate to that as well. I would also like you to do these tests without the I2C cables that you have plugged in. This is just to make sure there isn't another device with address 0x98 on the bus.

    Regards,

    Ramsey

  • Hi Ramsey,

    On the TAS5825PEVM board, the XMOS device enumerates as a composite USB device (Audio and HID). The HID provides the control interface / I2C bus master. In my case running this on my normal workstation, which is Dell Precision running Windows 10 pro, both devices enumerate but the HID is not visible to PPC3. Running it up on another machine today, it's all working as advertised.

    I would suggest improving the documentation so that users understand how the I2C bus master is connected and how to test it. I expect the composite device approach is used for all supported dev boards that have control and audio interfaces. There may also be boards with separate USB connections for each. I'm not sure if XMOS is your goto approach for USB audio now or not, but I can fully recommend it from our testing.

    One thing I did find frustrating today was the time it took to download the PPC3 applications onto the new machine. It was severely throttled at your end. I almost gave up after a couple of hours, yet I could download a large (7MB) reference manual from TI in less than a second. I haven't got to the bottom of the issue with the Dell Precision yet but have added snips of the device properties and events to the end of the document linked above. When I work out why it doesn't work, I'll let you know.

    Thanks again for your support and I'll let you close this thread. From my perspective it's resolved. I don't mind using another machine and this allows me to continue working on the project at hand.

    Kind Regards,

    Dean.