• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 943 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

PCM186X EVM problem connecting to PurePath Console

James Kent31
Prodigy 70 points
Other Parts Discussed in Thread: PCM1860EVM

Hi,

I am using a PCM1860EVM board with USB-I2XC interface board. This pair of boards used to work for me, at least in "mode 2" for playing audio out of my PC via USB by injecting audio from a sig. gen. into the EVM board. Recently however, it has stopped working; possibly ESD?...

Now, when I connect the USB cable to the PC, the USB-LOCK LED does not illuminate and PurePath Console warns that "Device found has no FWID". Proceeding anyway leads to PurePath attempting to connect briefly then always saying "Disconnected[]" in the bottom left corner.

If I connect the USB cable to the USB-I2X board alone (without the USB-I2X connected to the EVM board) then the USB-LOCK LED does illuminate. PurePath then shows that "Device found as unexpected FWID [FWIDUSB-I2X]". If I then plug the USB-I2X to the EVM, the USB-LOCK LED remains illuminated but the system shows the same behaviour as before (no FWID -> disconnected). If I press "reset" on the USB-I2X board, USB-LOCK is lost.

I have tried uninstalling the drivers, but now Windows 7 will only install the system as "Unknown".

I have read this forum post but found no suggestions that helped in my case: "e2e.ti.com/support/data_converters/audio_converters/f/64/t/356716"

Any help would be much appreciated.

Thanks!

  • 0
    TI__Mastermind 28020 points
    Hi James,

    Is there anything holding down the I2C lines on the EVM? Check the I2C lines on the PCM186X board itself with the USB-I2X attached. The USB-LOCK usually doesn't illuminate when the TAS1020B cannot initialize, and this usually happens when the I2C bus is not available. Another symptom of the I2C communication not working is that the GUI will not be able to identify/talk to the board, and therefore will say disconnected.

    Justin
  • 0 in reply to Justin Bohr
    Prodigy 70 points
    Thanks so much for your help Justin!

    I had fitted pull-down jumpers on J7 corresponding to MD2 and MD3, in an attempt to configure the Analog MUX and Gain as well as select the FIR Decimation Filter (see pg 5 of SLASE55A). On closer inspection, these pins are also used as SDA and SCL I2C lines - as you mentioned, there was indeed 'something' holding down the I2C lines!

    After removing the pull-down on MD2 & MD3 (SDA & SCL), USB-LOCK can be achieved with the USB-I2X plugged into the EVM and PurePath can now connect to "device FWIDPCM1860EVM".

    I like to think that the datasheet and EVM user guide may have led me astray but I also feel a bit silly for not more closely inspecting the EVM schematic!

    Thanks again!