• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 53 subscribers
  • Views 1385 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.

CCS/CCSTUDIO-MSP: CCS/CCSTUDIO-MSP

Vitaly Andrianov
Prodigy 260 points

Part Number: CCSTUDIO-MSP

Tool/software: Code Composer Studio

Hello All,

I tried to install the ccs_7.3.0.00019 on a Windows 10 PC. Only MSP430 support. I couldn't get debugger working. The ti_msp430pack7.3.0_install.log shows several errors. I reinstalled ccs several times.

Does anybody know what might be wrong?

Thanks,

Vitaly

-------------------------------------------- from install.log ---------------------------------

Executing c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "c:/ti/ccsv7/ccs_base\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/ccsv7/ccs_base\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\USB_eZ-RF": Program ended with an error exit code
Executing c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "c:/ti/ccsv7/ccs_base\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/ccsv7/ccs_base\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\USB_FET_Win7_8_10_64": Program ended with an error exit code
Executing c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\USB_CDC\installCerts.bat
Script exit code: 0

Script output:

c:\ti\ccsv7\ccs_base\emulation\drivers\msp430\USB_CDC>certutil -addstore -f "TrustedPublisher" "USB_CDC_CERT.p7b"
TrustedPublisher "Trusted Publishers"
Related Certificates:

Exact match:
Element 16:
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 7:00 PM
NotAfter: 2/7/2020 6: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 15:
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 7:00 PM
NotAfter: 7/16/2036 6: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 3:
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 7:00 PM
NotAfter: 2/25/2017 6: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/ccsv7/ccs_base\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\USB_CDC"
Script exit code: 256

Script output:

Script stderr:
Program ended with an error exit code

Error running c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\DPInst\DPinst64.exe /q /se /sa /lm /path "c:/ti/ccsv7/ccs_base\emulation\drivers\msp430\USB_CDC": Program ended with an error exit code
Creating Uninstaller

 

  • 0
    TI__Mastermind 22060 points
    Hi Vitaly,
    Can you zip up the contents of the install directory's install_logs folder and post here?
    Thanks,
    Danish
  • 0 in reply to danishinnis
    TI__Prodigy 260 points

    HI Danish,

    How do I attach a file to the post?

    Thanks,

    Vitaly 

  • 0 in reply to Vitaly Andrianov
    TI__Mastermind 22060 points

    When you click on "reply" you should see a link on the bottom right that says "insert code, attach files and more..." It should take you to a hypertext window. You can use the paperclick icon to attach a file.

  • 0 in reply to danishinnis
    TI__Prodigy 260 points

    Danish, thank you. I'm attaching two files. One is the zip you have asked. Also I tried to install just

    the ti_msp430driver_setup_1.0.1.0. I'm attaching its log, which show the same errors.

    Fullscreen ti_msp430driver_setup_1.0.1.0_install.log Download 
    Log started 11/24/2017 at 14:48:17
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
Preparing to Install
[14:48:28] eclipsedir = 
Preparing to Install
Directory already exists: 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
Directory already exists: 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
Directory already exists: 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
Directory already exists: 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"
Related Certificates:

Exact match:
Element 16:
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 7:00 PM
 NotAfter: 2/7/2020 6: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 15:
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 7:00 PM
 NotAfter: 7/16/2036 6: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 3:
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 7:00 PM
 NotAfter: 2/25/2017 6: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 16:
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 7:00 PM
 NotAfter: 2/7/2020 6: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 15:
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 7:00 PM
 NotAfter: 7/16/2036 6: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 3:
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 7:00 PM
 NotAfter: 2/25/2017 6: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 11/24/2017 at 14:48:33
    install_log20171124150602.zip

  • 0 in reply to Vitaly Andrianov
    TI__Mastermind 22060 points

    Hi Vitaly,

    The error messages you're seeing are not really errors - the return codes from DPinst are non-zero so the msp installer reports the codes as potential errors, but your installation has gone fine. 

    When you say you're unable to run the debugger, what are you seeing? I'll forward the thread to the debugging experts.

    Danish

  • 0 in reply to danishinnis
    TI__Prodigy 260 points
    Hi Danish,
    I remember when I had a working CCS when I plugged the MSP430 launchpad, I saw two new COM ports on DeviceManager. One port was a serial COM and another was a debug comport. The last one was to be used by CCS debugger. Now, I can see only the serial COM port, but nodt the debug one. BTW, installation log for the serial port returns 0, while other returns 256.
    So, I'm still suspecting that there was an installation error installation error.
    Thanks,
    -Vitaly
  • 0 in reply to Vitaly Andrianov
    TI__Prodigy 260 points
    Hi Danish,
    Any update on the issue?
    Thanks,
    -Vitaly
  • 0 in reply to Vitaly Andrianov
    TI__Genius 16490 points

    Vitaly,

    Note the zero return code you see in the log is for the installCerts.bat  script, not the previous dpinst call. It looks as though the drivers are installed correctly. 

    Can you tell us more about the debugging issue you are having?  Are you able to use UniFlash or the Cloud IDE (from  ) on this device?

    Thanks

    Andy

  • 0 in reply to AndyW
    TI__Prodigy 260 points

    Hi Andy,

    I didn't try the Cloud IDE. I just wanted to use CCS installed on my PC. As I said before when I plugged in the MSP-EXP430G2 Launchpad I can see only application port, but not the debug port. As a workaround I'm using the MSP430F5529 launchpad emulator connected to MSP430G2x devices. When I plugged the MSP430F5529 launchpad in I see the both application and debug serial ports.

    Thanks,

    -Vitaly