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.

TLV320AIC3111EVM-K: Unable to connect TLV320AIC3111EMV-K to host computer via USB

Part Number: TLV320AIC3111EVM-K
Other Parts Discussed in Thread: TLV320AIC3111

I have been unable to connect the TLV320AIC3111EVM-K target to my host computer.

I have followed instructions in the TLV320AIC3111 EVM User's Guide SLAU285 – July 2009 document, and I have also tried several times to configure the device using steps in this guide: /cfs-file/__key/communityserver-discussions-components-files/6/How-to-Revive-a-USB-Audio-EVM.pdf (How to Revive a USB Audio EVM).

The device enumerates as this device (DFUUSB):

When I follow the directions in the "How to Revive ..." document, I get this error:

Please help me resolve this soon. I purchased this EVM to solve an urgent problem with headset microphone operation.

Also, if there is a Linux version of the CodecControl.exe executable, I would be very interested in using that instead.

Thanks.

--ken

  • Hi,

    Few things to check/try:

    • Can you check the USB-MODEVM SW2 are in the correct position as shown in the user guide below?
    • Ensure board jumpers are in the position as described in the user guide
    • Here is the link to revive the Audio EVM:

    https://e2e.ti.com/support/audio-group/audio/f/audio-forum/773576/faq-tlv320aic-codecs-and-adcs-how-to-restart-revive-a-usb-audio-evm/2861816?tisearch=e2e-sitesearch&keymatch=how%252520to%252520restart%252520%25252F%252520revive%252520a%252520USB%252520audio%252520EVM#2861816

    • Run CodecControl as Administrator

    Regards.

  • pdjuandi,

    Thanks for the response.  Actually position 2 of SW2 was in the wrong state.  I changed it and tried again, but unfortunately this did not help.  I have the same results.

    I followed the link you sent above.  This appears to be the same "How to revive ..." document that I found previously.

    I ran through the procedure again and received the same results as before.

    Along the way a few things raised questions:

    (1)  The "Applies to:" line does not include the EVM that I have (TLV320AIC3111EVM-K).

    (2)  For the USBfirmware files listed in Step 1, I assume that I use the slac563 files archive, which actually resolves to slac563b.zip.  This is correct, right?

    (3)  For Step 3 I am inserting the shunts into J6 across pins 1 -- 2 (SDA) and pins 3 -- 4 (SCL), which are the external I2C signals.  When I do this and then connect the USB cable, the the SCL and SDA signals at the U1 EEPROM are held to zero, which I think is the intention (to disable the I2C bus in order to disable reading configuration from the EEPROM).  When I do this, the USB port still enumerates as a DFUUSB port.  Then, after the device enumerates, (and after 5 seconds, as advised in Step 3), I remove the shunts, but (a) this does not cause the "found new hardware wizard" to appear, and (b) the I2C bus signals do not pull up at the U1 EEPROM as I would expect; instead they stay low (actually at about 0.17 V); this condition is maintained until the USB cable is disconnected and then re-inserted without the shunts in place.

    (4)  At this point (shunts out, I2C signals high again) I can run the DFUTEST.exe executable, but if I attempt to use it to program the EVM, when I select the DFUEE.bin file and begin the download, the UI shows that the download is taking place and I also see activity on the I2C bus, and I get the "Download completed." message; then after the device enumerates I get this message: "Detach call failed.".

    What am I doing wrong?

    Thanks.

    --ken

  • Is it possible that I have a defective EVM?

    --ken

  • Close the DFU test, disconnect and connect back do you see the LED D2 (near the USB connector) light turns on?

    I have ordered a new EVM to crosscheck but has not arrived yet.

    regards.

  • pdjuandi,

    No, this does not work either.  I know I tried this before, but I just went through the process again, in case I missed anything.

    I also tried un-installing the DFUUSB driver from the Device Manager; it completed and indicated this was done, but when I disconnected and then re-connected the EVM board it showed up again.

    I also tried the program "remove-miniEVM.exe that is with the DFUTEST.exe exectuable, and that only pops up a window that disappears again very quickly (in about a tenth of a second, so fast I can't read what's in it).  It appeared to do nothing regarding the problem.

    Is it normal that the I2C bus signals would stay low after the shunts are removed?  They do return to normal again if the USB cable is disconnected and then re-connected.

    I also tried using an external power supply with the JMP6 shunt moved so that the board is already powered up when the USB cable is connected.  Same results.

    --ken

  • The EVM has shipped, let me check it out once it's here and will update you.

    Regards.

  • Hi Ken,

    Just to let you know I'm still waiting for the EVM.

    By the way which OS are you running? Can you try in device manager right click on the DFUUSB, uninstall and then install by manually point it to the folder that has the DFU exe. Now try the revive steps again.

    Regards.

  • Hi Ken,

    I received the EVM late Friday and I can see the USB-AudioEVM in my device manager.

    In your setup, let's try the attached procedure B for programming firmware.

    By the way, did you see DFUUSB the first time you connect the EVM or this DFUUSB is after you have tried to revive?

    Trouble-shooting AIC3111EVM Windows Issue.docx

    If this is still happening, try a different computer.

    Regards.

  • pdjuandi,

    Ok, this document was had additional information and was able to get me past the problem.

    I am now able to connect to the board.

    The key, I think, was removing, and then re-inserting the W20 jumper.  It is puzzling to me why this information was not included in the documentation that was referenced by the user manual pointed to by the information that came with the hardware.

    Thanks.

    --ken

  • Hi Ken,

    Good to know.

    We will add that to the user guide.

    Regards.