• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 46 subscribers
  • Views 1323 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

ADS1262EVM-PDK: ADC1262 Plug-in complications on ADCPro

Carolus Andrews
Mastermind 19385 points

Part Number: ADS1262EVM-PDK

Team,

I have a customer that is experiencing connectivity issues with the MMB0 motherboard with their ADS1262EVM. They were able to get ADCPro and the NI-VISA driver for the ADS1262 evaluation module, but the issue they are now seeing is the following:

"I connect the MMB0 to the PC with the USB cable and power it on. Then in ADCPro I launch the ADS126XEVM under the EVM tab. From my understanding this is supposed to download a new driver called “Styx” that will replace the VISA driver. However, in the black status bar it reads “DSP not ready…retrying.” 

In addition, we have also tried this with -5V supplied to the MMB0, and this did not remedy the situation. Any additional information or steps to remedy this would be greatly appreciated.

  • 0
    TI__Mastermind 44640 points

    Hi Carolus,

    It sounds like the MMB0 (USBStyx) driver did not get installed correctly...
    I would recommend re-installing this driver from the link below. This driver is suppose to get installed with the ADS126xEVM plugin; however, we've seen that many times this driver is not installing properly. There is a stand-alone driver installer that can be downloaded from here:

    ftp://ftp.ti.com/pub/data_acquisition/ADCPro2/misc/drivers/

    Select the "32bit" or "64bit" version of the installer related to whether the OS is 32- or 64-bits.

    Also note, this driver is not signed. Therefore, for Windows 8+ you may need to disable Windows's driver signature enforcement before installing this driver.

    Let me know if that resolves the problem!

    Best regards,
    Chris

  • 0 in reply to Christopher Hall
    TI__Mastermind 19385 points

    Dear Christopher,

    I had them reinstall from the provided link, and it is still not happy:

    Of note, the driver is being seen by the customer prior to running the EVM, and then after the above happens, the driver is no longer found by device manager. Thoughts?

  • 0 in reply to Carolus Andrews
    TI__Mastermind 44640 points
    Hi Carolus,

    Refer to this E2E post: e2e.ti.com/.../1544138

    The ADS1262EVM will first enumerate as an "MMB0 (NI-VISA)" device. However, once you've loaded the ADS126xEVM plugin from ADCPro, the DSP will be re-flashed and the MMB0 should re-enumerate as a "USBStyx" device. If the later device is not appearing, then likely the driver did not get installed correctly or Windows is not making the association between the device hardware and the USBStyx driver.

    Are they seeing the "USBStyx" device in Device Manager? If not, do they see any unidentified devices in device manager?

    Thanks,
    Chris
  • 0 in reply to Christopher Hall
    TI__Mastermind 19385 points
    Dear Christopher,

    That is the point of disconnect it seems. The customer is able to see the device show up as "MMB0 (NI-VISA)," but attempts to load the firmware result in a timeout and elimination of mmb0 driver from device manager.

    Is there anything more that could be causing the issue? It seems odd that the driver would load incorrectly twice, from two separate links(one from ti.com, one from the link you sent).
  • 0 in reply to Carolus Andrews
    TI__Mastermind 44640 points
    Hi Carolus,

    There are actually two different driver's being used:

    The first driver (for the MMB0 NI-VISA device) appears to be working.
    The second driver (for the USBStyx device) is failing.

    Do you know which version of Windows the customer is using?
    ...Currently ADCPro only officially supports Windows 7, but others have gotten it to work on Windows 8 and Windows 10.

    Did they try disabling Windows driver signature enforcement?

    Occasionally when all has failed, we've recommended trying the software on another computer.

    Best regards,
    Chris