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.

Connectivity problem PCM1865EVM

Other Parts Discussed in Thread: PCM1865

Hello,

I recently received an evaluation kit for PCM1865 DAC to be evaluated for our upcoming product.

Problem is that I can't seem to connect to EVM correctly using Purepath console.

PPC reports that device is not connected, and Windows device manager reports this device as "unknown", and therefore is unable to find proper driver for it.

Purepath console is latest version downloaded today. (7/22/14)

This leads me to wonder, that there is an issue with the USB-I2X board delivered with EVM. To further analyze problem I connected the EVM to linux computer which reported:

idVendor=ffff

idProduct=fffe

This is clearly not correct.

I am using Windows 8.1 pro 64bit system, to use purepath console and EVM.

EVM itself was bought from Mouser Electronics, if this helps tracing the problem.

br,

     Tapio

  • Hi, Tapio,

    It sounds like the USB driver was not loaded correctly.

    Can you try re-loading the USB driver?

    -d2

  •  

    Hi Tapio,

    Try installing the PurePath Console version "rev33210" from the cc.ext.ti.com site. This revision was specific to the PCM1865 EVM.

    If you get an error that says "FWID not found". You can ignore it. This is the auto detection of the PCM1865 EVM. (Since these EVM boards use the separate USB-I2X tag, It doesn’t know what EVM board you have connected since it can be anything; hence the FWID error).

    Next find the target form a list and select PCM1865.

    You should find that the board is now connected based on the green icon on the bottom left of the PurePath screen.

    I should also let you know that there is a new version of software for the PCM1865 EVM we plan to release in about a month. It will have more features and a better, easier, user interface.

    -Matt

     

  • Hi Matt and d2, thanks for quick answers.

    That is the exact version I have been trying to use. It is from cc.ext.ti.com and it is the one listed under PCM186XEVM and is dated 03/19/2014.

    http://cc.ext.ti.com/controlconsole/downloads/setup_PurePath_Console2_2.1_rev33210.zip

    Problem is that I don't get any error message at all when starting Purepath console, it just says "Disconnected" at the bottom of the window.

    Also on the USB-I2X board, usb lock led remains unlit. (don't know if it is supposed to be unlit or lit though)

    I have also now tried this EVM on a second computer, which runs windows 7. On this computer, when EVM was connected, windows tried to find drivers for "unknown device" but did not manage to do so. On this computer the behavior is similar to Windows 8.1 machine I tried earlier today, and Purepath Console is disconnected. (Which is logical since USB-I2X bridge drivers were not installed properly.)

    What I have tried so far is as follows: 

    1. Install the PPC and connect EVM right away => Does not work

    2. Uninstall the installation above, reboot, reinstall PPC, reboot => does not work

    3. Install on second computer (Win7), reboot after installation => does not work here either.

    4. Try to connect EVM to linux computer, since these give loads of more debug data on USB devices than  windows does: 

    dmesg:

    [   59.076080] usb 4-2: new full-speed USB device number 2 using uhci_hcd
    [   59.241110] usb 4-2: New USB device found, idVendor=ffff, idProduct=fffe
    [   59.241115] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [   59.241118] usb 4-2: Product: Unknown
    [   59.241121] usb 4-2: Manufacturer: Unknown

    lsusb -v:
    Bus 004 Device 002: ID ffff:fffe
    Couldn't open device, some information will be missing
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               1.00
      bDeviceClass          254 Application Specific Interface
      bDeviceSubClass         1 Device Firmware Update
      bDeviceProtocol         0
      bMaxPacketSize0        64
      idVendor           0xffff
      idProduct          0xfffe
      bcdDevice            1.00
      iManufacturer           1
      iProduct                2
      iSerial                 0
      bNumConfigurations      1
      Configuration Descriptor:
        bLength                 9
        bDescriptorType         2
        wTotalLength           25
        bNumInterfaces          1
        bConfigurationValue     1
        iConfiguration          0
        bmAttributes         0x40
          (Missing must-be-set bit!)
          Self Powered
        MaxPower              250mA
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        0
          bAlternateSetting       0
          bNumEndpoints           0
          bInterfaceClass       254 Application Specific Interface
          bInterfaceSubClass      1 Device Firmware Update
          bInterfaceProtocol      0
          iInterface              3
          Device Firmware Upgrade Interface Descriptor:
            bLength                             7
            bDescriptorType                    33
            bmAttributes                        7
              Will Not Detach
              Manifestation Tolerant
              Upload Supported
              Download Supported
            wDetachTimeout                    256 milliseconds
            wTransferSize                      64 bytes

    From the lsusb listing I would understand that the bridge is missing its firmware or something similar to that since almost all of the fields seem to be unwritten. (or wiped due to ESD event or similar, which would be curious since device is straight out of it's own packaging and was handled in proper laboratory)

    As a matter of fact it seems, now as I dive deeper to this problem, that TAS1020B in USB-I2X goes to DFU operating mode, which would suggest that EEPROM is empty, or this device is waiting for an firmware update from PC. Is this correct operation, for this device.

    D2 did mention something about USB driver not loading properly, and suggests that I reload it. Of this procedure I do not have a clue how that is supposed to work, since all I have is Purepath installer, and it does not seem to contain drivers for this thing. (or at least it does not tell that it installs such drivers) If this is the problem, how I am supposed to do that on Windows 7/8?

    br,

    Tapio




  • Hi Tapio,

    The USB lock LED and 3.3V LED should be lit on the USB-I2X board as soon as it is connected to a PC, even when it is not plugged into PCM6145EVM. When plugged into the EVM, the EVM has an additional 3.3V LED which should also be lit.

    Non lit 3.3V LED means no power, (which I’m assuming is not the case).

    If just the USB_lock LED is unlit, I need to do more digging.

    In the meantime, I would suggest running the USB-I2X board standalone to see if you can get those LED's lit. There should be no jumpers installed on the USB-I2X board.

    I will do some digging on this and get back to you will more information.

    -Matt

     

     

  • I should also add that if the "reset" button on the USB-I2X board got stuck in the down position, it will not work correctly. Try working that button a few times with the board plugged in.

    -Matt

  • Hi Tapio,

    So I consulted with a colleague who is familiar with the TAS1020. He came to the same conclusion; the USB-I2X board is missing the firmware.

    The USB_lock LED should light when connecting with a computer without additional steps. Then you can use the PurePath software as discussed.

    I would suggest going to the distributor for a new USB-I2X board.

    -Matt

     

  • Okay, I will contact Mouser for RMA procedure to replace this board now.

    Although I did find another problem with USB-I2X board, which we have. I noticed this problem, when I was examining the reset button issue, which you suggested earlier. There was a small rework done to the board, which was actually not done quite correctly. More specifically, the rework had snapped off from the pad it was supposed to be connected to. See pictures below.

    I did resolder the resistor at the end of this lead to the pad it was snapped off, but this obviously did not resolve issue with missing firmware. Although one could speculate that this missing connection could be the reason, that the firmware is missing in the first place.

    Anyway thank you for an excellent customer service on this issue, it was a pleasure working with you.

    With best regards,

    - Tapio

  • Hello Matt,

    i have the very same problem: i bought two weeks ago a 1863EVM directly from TI and i cannot get connected to the PC.

    I tried both under W7 and XP,  but the USB lock led is always off and the board is reported as "unknown device". Checked also the reworking which was broken on Tapio's I2X board, but mine seems ok.

    What can i do now? Other things to check ?

    Thanks

    Tom

  • Hello Tom,

    Sorry to hear you are having issues. I have referred this post to a colleague as I no longer support audio products. He should get back to you soon.

    Best Regards,
    Matt
  • Hi Tom,

    You can try flashing the firmware to the EEPROM on the board with this guide: e2e.ti.com/.../2790.how-to-revive-a-usb-audio-evm

    Justin