• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 301 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.

Original question:

TLV320AIC3104EVM-K: No communication from AIC310x EVM GUI to the dev board via USB

TLV320AIC3104EVM-K: AC-MODEVM "connect USB" after drivers installed

Andrew Hepp
Prodigy 10 points
Part Number: TLV320AIC3104EVM-K

Tool/software:

Hello,

I have followed the procedure in SLAU855A to install the AIC310x GUI on my Windows 11 laptop. When I connect a USB cable to the AC-MODEVM carrying the AIC3104 EVM, I see the USB ready (D1) and power (D3) LEDs illuminate. Despite this, when I launch the GUI I get an error message telling me to connect a USB device.

I see a "TI USB Audio" device appear in Windows device manager. I also see that NI Labview software seems to have successfully been installed.

I've attempted removing and re-installing the TI and NI software several times now, without successfully connecting to the UI. I have tested out a second AC-MODEVM and AIC3104 EVM and observe no differences.

A coworker of mine has this setup working on Windows 10, are there known issues with the GUI on Windows 11?

Any assistance would be appreciated. Pictures of jumpers, device manager, and NI package manager attached.

Thanks,

Andrew

  • 0
    TI__Mastermind 46805 points

    Hi Andrew,

    The GUI does work on Windows 11. Since the TI USB Audio Driver is working, it might be an issue with NI. Could you check the package manager on your Windows 10 machine for any differences?

    Best regards,
    Jeff McPherson

  • 0 in reply to Jeff McPherson
    Prodigy 10 points

    Hi Jeff,

    Do you know of any Labview packages necessary for Windows 11 that aren't installed by the GUI installer?

    My coworker and I tried this a couple days ago without success, but I've cleaned the packages off and reinstalled a couple times now so I'll re-install all their packages again to be thorough. The windows 10 machine is on the left, the windows 11 machine is on the right.

    I see the "labview 2017 runtime" on the windows 10 machine, but when I tried installing labview 2017 runtime through NI package manager, it seems to have installed something different. I doubt that is the source of the problem, since the GUI installer installs a 32 bit runtime for 2019.

    One thing I noticed is that on the windows 10 machine, the device shows up in device manager as something like "TI DFU whatever", and says it has a driver error. Again, this is on the working version. On windows 11 (not working) the device shows up as a TI USB Audio device with a working driver. I'm not sure what's going on there, maybe it's a red herring.

  • 0 in reply to Andrew Hepp
    TI__Mastermind 46805 points

    Hi Andrew,

    The "TI DFU whatever" means that the TI USB Audio Driver isn't able to find the motherboard so the GUI is probably not working correctly at all on the Windows 10 machine even though it claims it's detecting it.

    I have the GUI installed on my Windows 11 machine and double checked that it works. My NI manager is full of stuff from other TI GUIs so I can't quite point to what the missing package may be (if that's the issue). My understanding is that the 2019 runtime is the critical piece. The only other thing I would try to add is the certificates installer that's on the Windows 10 machine.

    Best regards,
    Jeff McPherson

  • 0 in reply to Jeff McPherson
    Prodigy 10 points

    Hi Jeff,

    I updated the certificates installer to the most recent version without any luck. Are there any other steps I can take to debug this? I've verified the USB cable works with other devices. Happy to double check anything on my end, and I should be able to tap the AC-MODEVM I2C lines if needed, I'm just a bit stumped about where to go from here.

    Thanks,

    Andrew

  • 0 in reply to Andrew Hepp
    TI__Mastermind 46805 points

    Hi Andrew,

    I just tried this on a colleague's fresh Windows 11 PC with no NI products installed and it worked immediately. I think something must've gone wrong in the install and there's some kind of conflict. I also confirmed that the only package necessary is the 2019 32 bit Labview Runtime. Would you be able to erase everything related to the GUI and the 2019 Runtime or have you already tried that?

    Best regards,
    Jeff McPherson