• State
  • Locked Locked
  • Replies 21 replies
  • Subscribers 54 subscribers
  • Views 5815 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/F28M36H33B2: Ti Cloud Agent not connecting with Gui Composer

Albert Smit
Intellectual 730 points

Part Number: F28M36H33B2
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

My post on this issue was locked but never resolved. Please see the previous thread:

I still have this problem. I can not get the debugger to connect to my device when using the cloud tools, specifically the Gui Composer. Please help. Log file attached again.

Fullscreen 8055.log_ticld.log Download 
2017-10-30T09:27:19.607Z: Staring directory : C:\Users\asmit\TICLOU~1\src
2017-10-30T09:27:19.609Z: Starting Agent!
2017-10-30T09:27:19.618Z: Module( Agent )->Web socket server started!
2017-10-30T09:27:22.241Z: Overridden Proxy = 
2017-10-30T09:27:22.314Z: Discovered Module : DeviceDetector
2017-10-30T09:27:22.365Z: Discovered Module : DS
2017-10-30T09:27:22.379Z: Discovered Module : EventBroker
2017-10-30T09:27:22.398Z: Discovered Module : File
2017-10-30T09:27:22.405Z: Discovered Module : Flash
2017-10-30T09:27:22.410Z: rov_server_redirect: looking in: C:\Users\eclipse\dropins
2017-10-30T09:27:22.412Z: rov_server_redirect: looking in: C:\Users\eclipse\plugins
2017-10-30T09:27:22.414Z: rov_server_redirect: looking in: C:\Users\eclipse\Eclipse.app\Contents\Eclipse\dropins
2017-10-30T09:27:22.415Z: rov_server_redirect: looking in: C:\Users\eclipse\Eclipse.app\Contents\Eclipse\plugins
2017-10-30T09:27:22.417Z: Failed to load module : rov_server_redirect.js : TypeError: Arguments to path.join must be strings
    at f (path.js:204:15)
    at Object.filter (native)
    at Object.exports.join (path.js:209:40)
    at Object.<anonymous> (C:\Users\asmit\TICLOU~1\src\modules\rov_server_redirect.js:65:22)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
2017-10-30T09:27:23.114Z: Discovered Module : Serial
2017-10-30T09:27:23.120Z: Discovered Module : TargetSupport
2017-10-30T09:27:23.121Z: Agent main module running on port 64155
2017-10-30T09:27:23.123Z: len=
2017-10-30T09:27:23.124Z: 
2017-10-30T09:27:23.125Z: buf=
2017-10-30T09:27:23.126Z: {"port":64155,"version":"4.2"}
2017-10-30T09:27:23.160Z: Module( Agent )->{"command":"listCommands","id":1,"data":[]}
2017-10-30T09:27:23.162Z: Module( Agent )->{"data":{"commands":["listSubModules","createSubModule","listCommands","addConfigProperty","registerModuleWebSocket","registerModuleByPath"]},"response":1}
2017-10-30T09:27:23.170Z: Module( Agent )->Socket closed

  • 0
    TI__Expert 4150 points

    Are you using dev.ti.com? And which browser are you using? What is the version of ticloudagent-bridge ie the extension you are using?

    From your log it appears you are using an older version of Cloud Agent. Did you ever see a pop up that ask you to download and update the cloud agent?

  • 0 in reply to Victor Yang
    Intellectual 730 points

    Yes I am using dev.ti.com. Using Google Chrome Version 61.0.3163.100. ticloudagent-bridge version 3.0.5. Yes the log was from the older version. I got the dialog now and updated the cloud agent, but problem still persist. I can not find the log file even though it is enabled in the .bat file(see below). It is supposed to be in c:/temp/ according to the ticloudagent.bat but there is noting. I attached the install log file.

    @echo off

    set PATH=%~dp0\util;%PATH%
    rem set TI_DS_ENABLE_LOGGING=1
    rem set TI_DS_LOGGING_OUTPUT=c:/temp/my.log
    rem echo ---ARGS--- %1 %2 %3 > c:/temp/my.log

    if not exist "%windir%\system32\reg.exe" goto QUERY_BITSIZE_DONE
    if not exist "%windir%\system32\find.exe" goto QUERY_BITSIZE_DONE
    "%windir%\system32\reg" Query "HKLM\Hardware\Description\System\CentralProcessor\0" | "%windir%\system32\find" /i "x86" > NUL && set OS_BIT_SIZE=32||set OS_BIT_SIZE=64
    :QUERY_BITSIZE_DONE

    if "%~1"=="not_chrome" goto NOT_CHROME else goto CHROME

    :CHROME
    rem echo ---CHROME--- >> c:/temp/my.log
    "%~dp0/node.exe" "%~dp0/src/main_chrome.js" %*
    goto END

    :NOT_CHROME
    rem echo ---NOT_CHROME--- >> c:/temp/my.log
    "%~dp0/node.exe" "%~dp0/src/main.js" %*

    :END

    Fullscreen 2465.ticloudagent_install.log Download 
    Log started 10/31/2017 at 10:06:59
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
[10:06:59] Installer name: ticloudagent__2 (3).exe
[10:07:01] installer_command_line_arguments: 
[10:07:01] installer_command_line_arguments: 
Preparing to Install
[10:07:05] BuildID: 0.5 1567
Preparing to Install
Unpacking files
[10:07:46] no C:\Users\asmit\AppData\Local\Texas Instruments\TICloudAgent
[10:07:47] FEATURE_WEBSOCKET_MAXCONNECTIONSPERSERVER is set to 16.
Installing npTICloudAgentLauncher.dll
Executing regsvr32 /s C:\Users\asmit\TICloudAgent/plugins/npTICloudAgentLauncher.dll
Script exit code: 0

Script output:
 

Script stderr:
 

Executing C:\Users\asmit\TICloudAgent/util/install-certs.bat 
Script exit code: 0

Script output:
 
C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti1.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 10:
Serial Number: 7ba5aab20f054f4560dedc8991e62a27
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: 7/25/2012 2:00 AM
 NotAfter: 7/26/2013 1:59 AM
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
Template: 
Cert Hash(sha1): 50 fc db ea 59 30 e0 4e 0c ed 67 46 71 5f 23 80 ec 6d 03 a9

Certificate "CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti2.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 3:
Serial Number: 1124ac88d0430481e0eaa40ef04118a9
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: 10/4/2011 2:00 AM
 NotAfter: 10/4/2012 1:59 AM
Subject: CN=Texas Instruments Inc, OU=Stellaris MCU, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Inc, L=Austin, S=Texas, C=US
Non-root Certificate
Template: 
Cert Hash(sha1): bc cc f2 62 67 ce e6 b5 8b 38 18 78 2d 26 f4 30 7b cb 6a 4f

Certificate "CN=Texas Instruments Inc, OU=Stellaris MCU, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Inc, L=Austin, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti3.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 2:
Serial Number: 558c8cedb57ce54fa6fb351fb84b222f
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: 4/15/2014 2:00 AM
 NotAfter: 4/17/2015 1:59 AM
Subject: CN=Texas Instruments, OU=WCS, O=Texas Instruments, L=Dallas, S=Texas, C=US
Non-root Certificate
Template: 
Cert Hash(sha1): c7 6e 48 8a fc 11 5a d0 9d a6 69 cb e4 13 31 6f e5 6e 94 38

Certificate "CN=Texas Instruments, OU=WCS, O=Texas Instruments, L=Dallas, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti4.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 1:
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/26/2014 2:00 AM
 NotAfter: 2/26/2017 1:59 AM
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
Template: 
Cert Hash(sha1): ee 0c 8b a0 18 ce 92 64 32 c3 cc 23 52 3a 34 07 3d 01 95 4a

Certificate "CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

Script stderr:
 

Installing target support (This may take some time)
Executing C:\Users\asmit\TICloudAgent/node.bat 
Script exit code: 1

Script output:
 no valid command line parameter passed


Script stderr:
 Program ended with an error exit code

Error running C:\Users\asmit\TICloudAgent/node.bat : Program ended with an error exit code
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Uninstaller icon changed
Installation completed
Log finished 10/31/2017 at 10:08:05

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    From your log line 226, it shows that the installation actually failed. Could you try to uninstall the CloudAgent and download a new one and try to reinstall it? Did you see any error pop up during install?

    The batch file above actually generate "my_ticld.log" instead  of "my.log" due to historical reasons. I should really fix that in the next release...

    Anyway the log is only generated when you try to use the cloud tool to access the target. After reinstall, could you give it a try to Cloud CCS or UniFlash as well to see if you can flash the target?

    Also, after reinstall, please send me the content of the file C:\Users\<user id>\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json

  • 0 in reply to Victor Yang
    Intellectual 730 points

    I reinstalled it, no error popped up, still not working.

    On CCS Cloud it says it does not have a target type, I don't know where to set the target type.

    Uniflash also not working.

    (I just had to make the .json file .jason.txt, other wise it did not alow me to upload the file)

    Fullscreen com.ti.ticloudagent.json.txt Download 
    {
  "name": "com.ti.ticloudagent",
  "description": "TI Cloud Agent - To communicate with TI devices",
  "path": "C:\\Users\\asmit\\TICLOU~1/ticloudagent.bat",
  "type": "stdio",
  "allowed_origins": [
    "chrome-extension://pfillhniocmjcapelhjcianojmoidjdk/",
    "chrome-extension://dmgblliompgilineecgmkpofdoechinj/"
  ]
}
    Fullscreen 1072.ticloudagent_install.log Download 
    Log started 11/02/2017 at 16:58:26
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
[16:58:27] Installer name: ticloudagent__2 (3).exe
[16:58:29] installer_command_line_arguments: 
[16:58:29] installer_command_line_arguments: 
Preparing to Install
[16:58:33] BuildID: 0.5 1567
Preparing to Install
Unpacking files
[16:59:23] no C:\Users\asmit\AppData\Local\Texas Instruments\TICloudAgent
[16:59:23] FEATURE_WEBSOCKET_MAXCONNECTIONSPERSERVER is set to 16.
Installing npTICloudAgentLauncher.dll
Executing regsvr32 /s C:\Users\asmit\TICloudAgent/plugins/npTICloudAgentLauncher.dll
Script exit code: 0

Script output:
 

Script stderr:
 

Executing C:\Users\asmit\TICloudAgent/util/install-certs.bat 
Script exit code: 0

Script output:
 
C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti1.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 10:
Serial Number: 7ba5aab20f054f4560dedc8991e62a27
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: 7/25/2012 2:00 AM
 NotAfter: 7/26/2013 1:59 AM
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
Template: 
Cert Hash(sha1): 50 fc db ea 59 30 e0 4e 0c ed 67 46 71 5f 23 80 ec 6d 03 a9

Certificate "CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti2.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 3:
Serial Number: 1124ac88d0430481e0eaa40ef04118a9
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: 10/4/2011 2:00 AM
 NotAfter: 10/4/2012 1:59 AM
Subject: CN=Texas Instruments Inc, OU=Stellaris MCU, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Inc, L=Austin, S=Texas, C=US
Non-root Certificate
Template: 
Cert Hash(sha1): bc cc f2 62 67 ce e6 b5 8b 38 18 78 2d 26 f4 30 7b cb 6a 4f

Certificate "CN=Texas Instruments Inc, OU=Stellaris MCU, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Inc, L=Austin, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti3.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 2:
Serial Number: 558c8cedb57ce54fa6fb351fb84b222f
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: 4/15/2014 2:00 AM
 NotAfter: 4/17/2015 1:59 AM
Subject: CN=Texas Instruments, OU=WCS, O=Texas Instruments, L=Dallas, S=Texas, C=US
Non-root Certificate
Template: 
Cert Hash(sha1): c7 6e 48 8a fc 11 5a d0 9d a6 69 cb e4 13 31 6f e5 6e 94 38

Certificate "CN=Texas Instruments, OU=WCS, O=Texas Instruments, L=Dallas, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

C:\Users\asmit\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\asmit\TICLOU~1\util\\ti4.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 12:
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/8/2010 2:00 AM
 NotAfter: 2/8/2020 1:59 AM
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
Template: 
Cert Hash(sha1): 49 58 47 a9 31 87 cf b8 c7 1f 84 0c b7 b4 14 97 ad 95 c6 4f

Certificate "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" already in store.
Signature matches Public Key
Related Certificates:

Exact match:
Element 11:
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/8/2006 2:00 AM
 NotAfter: 7/17/2036 1:59 AM
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
Template: 
Cert Hash(sha1): 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5

Certificate "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" already in store.
Related Certificates:

Exact match:
Element 1:
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/26/2014 2:00 AM
 NotAfter: 2/26/2017 1:59 AM
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
Template: 
Cert Hash(sha1): ee 0c 8b a0 18 ce 92 64 32 c3 cc 23 52 3a 34 07 3d 01 95 4a

Certificate "CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US" already in store.
CertUtil: -addstore command completed successfully.

Script stderr:
 

Installing target support (This may take some time)
Executing C:\Users\asmit\TICloudAgent/node.bat 
Script exit code: 1

Script output:
 no valid command line parameter passed


Script stderr:
 Program ended with an error exit code

Error running C:\Users\asmit\TICloudAgent/node.bat : Program ended with an error exit code
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Uninstaller icon changed
Installation completed
Log finished 11/02/2017 at 16:59:43

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    Do you happen to be behind a proxy?

    Also, could you try if firefox works?

  • 0 in reply to Victor Yang
    Intellectual 730 points

    It is at my work, so yes I believe that it is behind a proxy.

    Firefox does not work either.

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    It is probably because your linux proxy doesn't support websocket properly. This is a common issue, you can find more info about it here:  and discussions here: 

    Try unset both the http_proxy and https_proxy and see if it works.

  • 0 in reply to Victor Yang
    Intellectual 730 points

    Where do I unset the http_proxy and https_proxy?

    If I go to proxy settings it seems like there is in fact no proxy:

     

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    Maybe the installation didn't go through correctly. 

    Could you zip up the following folder and send it to me?

    C:\Users\asmit\TICloudAgent

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    Did you remove the node.exe before you zip the package? because your installation failed on this line:

    C:\Users\asmit\TICloudAgent/node C:\Users\asmit\TICloudAgent/src/installer/cli.js --installer ticloudagent__2 (3).exe --quiet true


    If you have the node.exe in the root folder of TICloudAgent, try to run that command manually and see if it gives any error messages.


    Also you would need to change the resources/Chrome/com.ti.ticloudagent.json.txt back to .json

  • 0 in reply to Victor Yang
    Intellectual 730 points

    No there was no node.exe file in the folder. I reinstalled and now there is a node.exe. If I run it the output is nothing, it just hangs with the cursor blinking in command prompt. See the new TICloudAgent folder attached.6765.TICloudAgent.zip 

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    change the node.bat 's line where it runs the cli.js from this:

    C:\Users\asmit\TICloudAgent/node C:\Users\asmit\TICloudAgent/src/installer/cli.js --installer ticloudagent__2(1).exe  --quiet true

    into this:

    C:\Users\asmit\TICloudAgent/node C:\Users\asmit\TICloudAgent/src/installer/cli.js --installer ticloudagent__2__lm_icdi.exe

    run node.bat from cmd and let me know what the output looks like.

  • 0 in reply to Victor Yang
    Intellectual 730 points

    Here is the cmd output after changing that line:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\asmit>cd TICloudAgent

    C:\Users\asmit\TICloudAgent>node.bat
    Installing windows drivers for [lm_icdi]
    Additional files need to be installed to support selected configuration. Startin
    g Install Process.

    ccs_base/common/bin/ti_targetdb_parser.dll
    ccs_base/common/bin/libusb-1.0.dll
    ccs_base/emulation/analysis/bin/AETPropertyHelper.dll
    Finished
    [object Object]

    C:\Users\asmit\TICloudAgent>

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    So you were saying previously it just stuck there right? At least now it runs to finish, for some reason we don't know.

    This step of the process is grabbing additional support files from the server, I thought you might have a connection issue to the server that's why it hangs there, but since some files are downloaded, the mystery thickens... 

    Could you compress and send me the directory C:\Users\asmit\AppData\Local\Texas Instruments\TICloudAgent\db

    If you are interested, it contains the list of installed files from the server by the cloudagent. You can verify if all these files are indeed installed if you have the time. I will go through them to see if all files should be installed is listed there.

  • 0 in reply to Victor Yang
    Intellectual 730 points

    There is nothing in that folder, its completely empty.

    I have also tried 2 other computers and manged to get it working on one of them. Interestingly, the 2 computers that are not working have windows 7 installed and the one that is working has windows 10. Don't know if that says anything?

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    Could be your network settings such as firewall etc. The problem is that the cloud agent don't seem to be able to download files from the server on your machine that doesn't work.

    If you have a PC with stock Win7 it should work. You can give that a try and narrow down where in the network setting that is causing the problems

  • 0 in reply to Victor Yang
    Intellectual 730 points

    All machines on the same network and firewall is off. Can't see any difference. Can I manually download those file?

  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    You can copy the whole folder C:\Users\asmit\AppData\Local\Texas Instruments\TICloudAgent from the machine that has it working to the machine that doesn't work and see if that fixes the issue. However dependencies are downloaded on the fly so if you change devices you might have to do it again.

  • 0 in reply to Victor Yang
    Intellectual 730 points
    I copied the file but it still does not work. I really want yo get this working because I need to setup it on other machines as well. Why What exactly in the network settings can cause it not to be able to download those files?
  • 0 in reply to Albert Smit
    TI__Expert 4150 points

    Albert,

    I wish I could help you here but I really can't figure out more unless I have full access to your machine and its environment, since the existing info I get from you makes very little sense to me. Content binary wise there is no diff from windows 10 to windows 7. If you have the setup fully working on the windows 10 copying over to windows 7 should work. 

    If you want to get to the bottom of it though, since you have windows 10 machine working but not on the windows 7 machines, I would suggest to first try using GC on a clean windows 7 machine(stock windows) in your network environment, such as a win 7 VM, a laptop etc, just to see if it is the network setting.

    We know for a fact that windows 7 machine should work since the vast majority of the customers are on windows 7 and you are the only case in your issue. You can also try this at home if you have a windows 7 machine.

    Victor