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

Issue with DRV8313 Evaluation Module Software

Hartaj Singh
Prodigy 50 points
Other Parts Discussed in Thread: DRV8313EVM

The software has abruptly started giving error. A pop-up screen shows following information while we try to connect the EVM

Member: .Name

Function: GetValue

Error In: InternalInvokeV

Error: Type mismatch.

Code: 80020005

Source: Application

Please advice

  • 0
    TI__Guru** 114905 points
    Hi Hartaj,

    Was the software previously working? If so, what has changed? Was there an update of the operating system?

    What OS are you using?
  • 0
    Prodigy 40 points

    I've got the same issue... out of the box error.  This is a new install. Just purchased a DRV8313EVM, hooked up a power supply, downloaded the software from TI website, installed the USB driver, (which failed) Ran the TI GUI and could never could past the error window with the code 80020005.  Went to the FTDI website and downloaded the D2xxx Driver (CDM for windows) - same error; no resolution.

    OS: Windows 10

    HW: Dell XPS13 Intel i5

    USB 3.0

  • 0 in reply to Christian Landry72
    TI__Guru** 114905 points
    Hi Christian,

    Sorry to hear you have the same issue.

    Are there any file logs that you can share?
  • 0 in reply to Rick Duncan
    Prodigy 40 points

    Rick,

    The comm error is consistent on more than one computer.  Both computers are running Windows 10 and USB 3.0 ports.  The FTDI driver I am using is the latest from FTDI (See below)

    /********

    FTDI Info file

    [Version]
    Signature="$Windows NT$"
    DriverPackageType=PlugAndPlay
    DriverPackageDisplayName=%DESC%
    Class=Ports
    ClassGUID={4d36e978-e325-11ce-bfc1-08002be10318}
    Provider=%FTDI%
    CatalogFile=ftdiport.cat
    DriverVer=09/28/2016,2.12.24
    *********/

    Also, I changed the comm port to COM4 per the Readme file and it made no difference.  Basically, this development kit is DOA and useless to me right now.