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.

TPA6130A2EVM driver installation issues

Other Parts Discussed in Thread: TPA6130A2EVM

Hello:

I just got the TI TPA6130A2EVM kit.  I'm having difficulty with driver installation to interface with the EVM.  I tried four different computers with no results.  We have tried Windows XP, Windows 7 64-bit, Windows 7 32-bit and a second Windows XP computer.  All of them produce the same results.  We tried all these different computers to rule out different variables.  We keep coming back to there is no driver file in the folder that seems to pair with the device.  We got the files from the TI website and downloaded the user guide and the software files.  The user guide states there should be a CD in the box, there was no CD in the box.
I have attached screen shots of the driver procedure and the final result of no driver found.
Can you help us find some assistance to get the EVM kit drivers installed and working so we can connect with the windows software that talks I2C to the board?
Thanks,
Paul
  • We were able to get this resolved with the latest installer package on the TPA6130 product page.

  • Hi, Paul,

    Sorry we missed your post! I'm glad y'all figured it out.

    Basically, we stopped shipping CDs with most, if not, all of our EVMs and want customers to download the s/w from the web so they get the latest version. Of course, we did not go back and update every document that refers to the CD in the box...

    -d2

  • TPA6130A2EVM Did not work on my systems - have downloaded the latest software twice, no USB driver.

    XP machine, SP2.  No driver found where instructions say it is, no driver found by wizard.

    Can not get software to work. Frustrating.  Can not find driver on WEB to download?

    Help

    Thanks

    Mark

  • I am having the same issue as Mark.  Has this been resolved?

  • Hi, Adam,

    Sorry about that!

    Please check this post: http://e2e.ti.com/support/amplifiers/audio_amplifiers/f/6/p/193261/886584.aspx#886584

    I saw you also posted something about PurePath Studios. if you didn't get that resolved, please reply to that thread again.

    -d2

    http://e2e.ti.com/support/amplifiers/audio_amplifiers/f/6/p/193261/886584.aspx#886584

  • Im having trouble with the TPA6130 EVM as well. No good on 2 different computers. There seem to be several problems.

    If the JP4 jumper is on the device appears as USB-MODEVM . When like this, the drivers cant be loaded. (already got the new drivers as per previous comments in thread). Every time attempts to load drivers just results in 'cant find the driver' message despite the correct path and drivers. Are the drivers corrupted or need to be updated? This occurs with the original 'dfudriver' and the updated drivers

    With JP4 off as required in the instructions for firmware update the device appears as DFUUSB which is what it says should be the case. Running the DFUTEST for firmware update does not progress according to the instructions. On the step requiring the JP4 to be put on causes the code to not update, multiple error messages are displayed.
    If the JP4 jumper is left off (against the instructions advice), the code load appears to proceed. But even when this is done, the device will not function correctly.
    After the programming firmware update, the device still does not display as USB audio device as advised in instructions.
    The same responses occur still - the device still comes up as USB-MODEVM with JP4 on or DFUUSB with JP4 off.

    The EVAL GUI is installed, but any attempts to use functions from it brings an error message about no drivers. Any idea what is going on here? Not getting any results on 2 different machines. Both Windows 7.
    Thanks
    Dan
  • Hi Dan,

    Have you modified the EVM board firmware? The EVM should appear as USB-AudioEVM.

    Best regards,
    -Ivan Salazar
    Texas Instruments
  • I attempted to update the firmware as per the instructions in the eval board PDF. It does not work per the instructions. I made a description of this in the original report.
    At the step 13 “13. A screen should open stating, “Set EEPROM’s I2C Address to 1010000b”. Now insert JP4 jumper and” – If the jumper is put back on when instructed, the update fails.
    If the jumper is left off for this step, the programming appears to complete.
    Either way, it does not appear to have updated – it never gets to USB-AudioEVM. It is always stuck on DFUUSB or USB-MODEVM depending on whether JP4 is off or on. Have attempted to get this to update several times but it does not work
    Thanks
    Dan
     
  • Hi Dan,

    I currently have a couple EVM boards that are working normally. I'll try to recreate the problem that you're having to find a solution.

    Best regards,
    -Ivan Salazar
    Texas Instruments
  • Hi Dan,

    I have repeated the process described in the user's guide on one of my boards and it seems to work fine.
    Are you using firmware V0304 from www.ti.com/.../tpa6130a2evm ?
    What are your jumper settings? Do you see any possible hardware problem on your board? U4 is correctly placed/soldered?

    Best regards,
    -Ivan Salazar
    Texas Instruments
  •  
    Yes, Im using the firmware directly from the TI website. V0304 which is downloaded as slac563b.zip
    I cant see any problems with the board. In fact I have 2 boards, I ordered a second one as I thought there might be a problem on the first one. They both respond the same way.
     
    The jumpers are set as in the pdf. The SCL/SDA jumpers are going through to the TAS1020, JP5 and JP6 are on, JP1 is set to internal (USB) power supply.
     
    Both boards behave exactly the same way, as follows
    On one computer -
    The board powers up and appears in device manager as USB-MODEVM when the JP4 is on. It comes up as DFUUSB with JP4 off. This is what the pdf for the board says should happen.
    At the step where the code update should occur where it instructs to put JP4 back on, the code load fails if this is done. It appears to complete if JP4 is left off.
     
    On the second computer with the software installed - The board powers up and appears in device manager as USB-MODEVM when the JP4 is on. It comes up as unknown with JP4 off. There is no way to update the code on this computer as the updater always brings up a message ‘no DFU device found’ and any attempt to go through the firmware process just brings errors.
     
    I cant see any problems on either board. They both initially appear to work with the computer in the most basic stage – as in there is USB dialog and it is identified. But nothing further can be done ie driver or firmware updates.
    Do you think there could be some system process interfering with the updating ie is there any background resident software known to cause issues or anything else like that?
    Thanks
    Dan
     
  • Hi Dan,

    I was running into similar issues where I downloaded the GUI file and my TPA6130A2EVM was being recognized as USBMODEVM in the device manager. It took some configuration but hopefully my same process will work for you, too. Note: Completed on Windows 7 OS. 

    1. Download 'TPA6130A2EVM - Graphical User Interface (GUI) Software (Rev. A)' and 'Audio Converter Firmware (TAS1020B) V0304 (Rev. B)' from  site and extract to a known location. 
    2. Connect the EVM to your computer
    3. Open Device Manager
    4. Mine showed "USBMODEVM" with a caution symbol
    5. Remove I2C jumpers, JP2 and JP3, but keep JP4 installed
      1. When I had the I2C jumpers installed it would not update the driver to DFUUSB. I apologize but I can't remember if I power cycled (disconnect and reconnect USB) after I removed I2C jumpers.If just removing them doesn't allow you to complete update driver to DFUUSB then try it with power cycle.
    6. Right click on "USBMODEVM" to update driver
    7. Browse for the 'dfu_driver' folder within the slac563b -> USBfirmware_V0304_Portable folder. Keep the include subfolders box checked and then you should be able to proceed with driver installation.
    8. After Step 7 completion, look in device manager under USB controllers and there should be a DFUUSB. Without getting to this step then you won't be able to complete the rest. The key was the I2C jumpers. 
    9. Unplug USB connection again
    10. Install I2C jumpers and remove JP4
    11. Connect to EVM again via USB port (power cycle)
      1. I tried adding the I2C jumpers immediately after step 8 then proceeding and the USBMODEVM came back. Then I tried with both I2C jumpers and JP4 removed and was able to proceed but ended up getting a failure. I went back and forth several times with certain jumpers installed/removed but it wasn't until I power cycled that I was able to get a successful firmware download in the following steps.
    12. Now that the I2C jumpers are installed and a power cycle was done, navigate to "USBfirmware_V0304_Portable" and run "DFUTEST.exe"
    13. In the DFUTEST window, click on the Program EVM button
    14. The program now opens a browser that should be navigating within the image folder inside the USBfirmware_V0304_Portable folder.
    15. A screen should open stating, “Set EEPROM’s I2C Address to 1010000b”. Now insert JP4 jumper and click Ok. 
    16. After a few seconds Download Complete should display. Click Ok.
    17. Follow the on-screen instructions
    18. A new browser window should automatically open in the same image folder.
    19. Open USB-miniEVM0304_441KHZ.bin to program standard 44.1 kHz USB.
    20. The previously viewed on-screen windows and instructions should display.
    21. After Programming Complete is displayed, the EVM should now be displayed as USB Audio Device in Device Manager under the sound devices drop-down menu.
    22. Run the GUI.

    Please try the above instructions and let us know if you still have issues.

    Thank you,

    Trenton Reed

  • Hi Dan,

    I want to make sure you have a working solution. Have you had a chance to try my instructions?

    Thank you,
    Trenton Reed
  • Hi Trenton,
    I did try it out. It didn’t work too well, there were other unusual errors. After testing out on a second 32bit computer (the 4th computer overall) and more errors something ticked over and the board ended up firing up correctly with one of the original computers we had it installed on, now seems to be working OK, despite nothing we actually tried ever working properly. So we have a working board now, seemingly more due to luck than anything.
    Thanks for your help
    Dan