• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 33 subscribers
  • Views 873 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:

CCS/MSP-EXP430G2ET: Can't install MSP430_FET_Drivers 1_0_1_1

DP83TD510E-EVM: MSP430_FET_Drivers are not installing

Mike Strauser
Intellectual 370 points
Part Number: DP83TD510E-EVM
Other Parts Discussed in Thread: USB-2-MDIO,

I have tried installing, uninstalling, and reinstalling the 

MSP430_FET_Drivers

as instructed in the user guide, but when I connect a USB cable, I get no COM port showing up - and no indication that a USB device was connected/disconnected from my computer.

I looked in the install logs and it does appear to be getting an error - even though none is shown in the GUI.  The last part of the log is below:

Script stderr:

Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC"
Script exit code: 256

Script output:

Script stderr:
Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC": Program ended with an error exit code
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 12/28/2020 at 11:08:04

Mike.

  • 0
    TI__Genius 11725 points

    Hi Mike,

    Can you kindly confirm which MSP430 Driver is being installed?

    Thank you,

    Nikhil

  • 0 in reply to Nikhil Menon
    Intellectual 370 points

    There is a link to the driver in the User Guide for the EVM - that is what I am using (see below).  I also tried it on a different Win10 computer and had the same results.

    MSP430_FET_Drivers 1_0_1_1 - TI.com

    MIke.

  • 0 in reply to Mike Strauser
    TI__Genius 11725 points

    Hi Mike,

    This driver is not unique to the Ethernet team, it should install the drivers necessary for communication with the MSP to your computer. Can you again kindly confirm the installer been extracted from the zip folder and run as an administrator?

    Thank you,

    Nikhil

  • 0 in reply to Nikhil Menon
    Intellectual 370 points

    Well, first of all, there are no instructions for installing these drivers - with a GUI there shouldn't need to be.  It is a self extracting Zip file so the average user won't have a clue how to run as administrator.

    I put a folder on my computer and used Winzip to extract the EXE from the ZIP into the empty folder.  I then right clicked on the EXE and ran as administrator.  It made no difference.  There is still an error in the Log file with no error shown on the GUI (so the user thinks it installed fine).

    We're really wasting a lot of time with only one email a day.  And you are giving me only one thing to try.  Did you try installing this on a computer to see if it works for you?

    Mike.

  • 0 in reply to Mike Strauser
    TI__Genius 11725 points

    Hi Mike,

    We have installed this driver on our own devices without an issue. As you mentioned, this should be a fairly straightforward process.

    I have reviewed my old install logs from 2019 and see the same error, I assume this error does not effect communication with MSP as I have not run into issues with communication. If we need to dive deeper into the workings of the driver, I may suggest reaching out to the processor forum, as this is no longer a Physical Layer issue. See attached install log:

    Fullscreen ti_msp430driver_setup_1.0.1.1_install.log Download 
    Log started 10/23/2019 at 15:24:53
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
Preparing to Install
[15:25:10] eclipsedir = 
Preparing to Install
Creating directory C:\ti\fetdrivers\emulation
Creating directory C:\ti\fetdrivers\emulation\drivers
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\DPInst
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPInst64.exe
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPInst.exe
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC\msp430tools.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC\msp430tools.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC\USB_CDC_CERT.p7b
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC\installCerts.bat
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF\430CDC.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF\430cdc.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF\installCerts.bat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF\USB_eZ_RF.p7b
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64\WdfCoInstaller01009.dll
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64\difxapi.dll
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64\usbuart3410.inf
Directory already exists: C:\ti\fetdrivers
Unpacking files
Unpacking C:\ti\fetdrivers\MSP430_USB_Drivers_Software Manifest_WIN.pdf
Executing C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF\installCerts.bat 
Script exit code: 0

Script output:
 
C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF>certutil -addstore -f "TrustedPublisher" "USB_eZ_RF.p7b" 
TrustedPublisher "Trusted Publishers"
Certificate "VeriSign Class 3 Code Signing 2010 CA" added to store.
Signature matches Public Key
Certificate "VeriSign Class 3 Public Primary Certification Authority - G5" added to store.
Related Certificates:

Exact match:
Element 4:
Serial Number: 39ad63d2f5c9efdc46d734ae5e381b8f
Issuer: CN=VeriSign Class 3 Code Signing 2010 CA, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O=VeriSign, Inc., C=US
 NotBefore: 2/25/2014 5:00 PM
 NotAfter: 2/25/2017 4:59 PM
Subject: CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US
Non-root Certificate
Cert Hash(sha1): ee0c8ba018ce926432c3cc23523a34073d01954a

Certificate "Texas Instruments Incorporated" already in store.
CertUtil: -addstore command completed successfully.

Script stderr:
 

Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe  /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe  /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF": Program ended with an error exit code
Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_8_10_64": Program ended with an error exit code
Executing C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC\installCerts.bat 
Script exit code: 0

Script output:
 
C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC>certutil -addstore -f "TrustedPublisher" "USB_CDC_CERT.p7b" 
TrustedPublisher "Trusted Publishers"
Related Certificates:

Exact match:
Element 8:
Serial Number: 5200e5aa2556fc1a86ed96c9d44b33c7
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU=(c) 2006 VeriSign, Inc. - For authorized use only, OU=VeriSign Trust Network, O=VeriSign, Inc., C=US
 NotBefore: 2/7/2010 5:00 PM
 NotAfter: 2/7/2020 4:59 PM
Subject: CN=VeriSign Class 3 Code Signing 2010 CA, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O=VeriSign, Inc., C=US
Non-root Certificate
Cert Hash(sha1): 495847a93187cfb8c71f840cb7b41497ad95c64f

Certificate "VeriSign Class 3 Code Signing 2010 CA" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 7:
Serial Number: 18dad19e267de8bb4a2158cdcc6b3b4a
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU=(c) 2006 VeriSign, Inc. - For authorized use only, OU=VeriSign Trust Network, O=VeriSign, Inc., C=US
 NotBefore: 11/7/2006 5:00 PM
 NotAfter: 7/16/2036 4:59 PM
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU=(c) 2006 VeriSign, Inc. - For authorized use only, OU=VeriSign Trust Network, O=VeriSign, Inc., C=US
Signature matches Public Key
Root Certificate: Subject matches Issuer
Cert Hash(sha1): 4eb6d578499b1ccf5f581ead56be3d9b6744a5e5

Certificate "VeriSign Class 3 Public Primary Certification Authority - G5" already in store.
Related Certificates:

Exact match:
Element 2:
Serial Number: 39ad63d2f5c9efdc46d734ae5e381b8f
Issuer: CN=VeriSign Class 3 Code Signing 2010 CA, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O=VeriSign, Inc., C=US
 NotBefore: 2/25/2014 5:00 PM
 NotAfter: 2/25/2017 4:59 PM
Subject: CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US
Non-root Certificate
Cert Hash(sha1): ee0c8ba018ce926432c3cc23523a34073d01954a

Certificate "Texas Instruments Incorporated" already in store.
CertUtil: -addstore command completed successfully.

Script stderr:
 

Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe   /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst64.exe   /q /se /sa /lm /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC": Program ended with an error exit code
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 10/23/2019 at 15:25:20

    The MSP430 on-board the EVM should already be flashed with the correct firmware to support the USB-2-MDIO software. Assuming both the on-board EZFet and MSP430 are powered correctly, and the driver is installed correctly (the driver does appear to be installed correctly), you should notice a new Com port appear when the USB is plugged in. I will confirm MSP functionality again on the DP83TD510E-EVM in lab tomorrow. 

    Thank you,

    Nikhil

  • 0 in reply to Nikhil Menon
    TI__Genius 11725 points

    Hi Mike,

    Is the 5V USB supply also being used to power the PHY, is a jumper placed on J9? After testing in lab, we have seen that using the 5V USB supply to power both the MSP and PHY by placing J9 may lead to the COM port not showing up. This can be solved by replacing R24 with a 0 ohm resistor. The 33 ohm resistor may cause a grounding issue, causing the device to not be recognized.

    While leaving the 33ohm resistor placed for R34, does the COM port show up after removing J9 (disconnecting 5V from powering PHY), and plugging in the USB cable? We have seen this setup work. Else, please replace R24 with a 0 ohm resistor and let me know if you see the COM port.

    Thank you,

    Nikhil

  • 0 in reply to Nikhil Menon
    Intellectual 370 points

    Well, I can't believe you didn't tell me this when I first wrote in about this.  I also can't believe they actually put a 33 ohm resistor in series with Ground on the USB connection - and expected it to power the board!  I don't see how anyone could get this to work if powering from USB.  Why is there not information about this in the manual?

    So yes if J9 is open, then the COM port is enumerated.  When I replace R24 with a zero ohm resistor, then it works with J9 closed.

    Mike.  

  • 0 in reply to Mike Strauser
    TI__Genius 11725 points

    Hi Mike,

    Apologies for the inconvenience. I am glad we could find a solution and the board is working now. Thanks for your feedback, this shall be fixed in the next revision of the EVM and User Guide.

    Thank you,

    Nikhil