• State
  • Locked Locked
  • Replies 12 replies
  • Subscribers 54 subscribers
  • Views 5148 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.

Could not launch TI Cloud Agent

Adila
Prodigy 140 points
Other Parts Discussed in Thread: CC2650

Hi,

I've been trying to flash on the sensortag cc2650 but kept on getting this error of not able to launch TI cloud agent.

I've installed TI Cloud Agent Application, went through the troubleshooting guide (checked that TICloudAgent Bridge enabled) and installed the library dependencies

Is there something that I missed that I'm not seeing?

Thanks,

Adila

  • 0
    TI__Intellectual 2265 points

    Which browser and OS are you using?

    Mandeep

  • 0 in reply to Mandeep Deol
    Prodigy 140 points

    I tried with Chrome in Ubuntu and also Chrome in Windows 7

    -Adila

  • 0 in reply to Adila
    TI__Intellectual 2265 points
    Which version of chrome are you using?

    Can you check on windows 7 if there is something ( assuming you installed to the default location ) at

    - %USERPROFILE%\TICloudAgent
    - %LOCALAPPDATA%\Texas Instruments\TICloudAgent

    If those exist can you try grabbing and passing along the logs from
    - %USERPROFILE%\TICloudAgent\ticloudagent_install.log
    - %USERPROFILE%\ti\node\TICloudAgent.log

    Thanks in advance,
    Mandeep
  • 0 in reply to Mandeep Deol
    Prodigy 140 points

    Hi Mandeep,

    log from ticloudagent_install

    Log started 08/18/2015 at 12:28:10
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
[12:28:11] Installer name: ticloudagent__2__xds110_drivers.exe
Preparing to Install
Preparing to Install
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Visual C++ Redistributable 2008
Executing C:\Users\noradila\TICloudAgent/vcredist_x86.exe /q /l "C:\Users\noradila\TICloudAgent/MSVC_REDIST_2008.log" /nostart
Script exit code: 0

Script output:
 

Script stderr:
 

[12:28:35] no C:\Users\noradila\AppData\Local\Texas Instruments\TICloudAgent
[12:28:35] FEATURE_WEBSOCKET_MAXCONNECTIONSPERSERVER is set to 16.
Installing npTICloudAgentLauncher.dll
Executing regsvr32 /s C:\Users\noradila\TICloudAgent/plugins/npTICloudAgentLauncher.dll
Script exit code: 0

Script output:
 

Script stderr:
 

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

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

Exact match:
Element 6:
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: 08/02/2010 01:00
 NotAfter: 08/02/2020 00:59
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 5:
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: 08/11/2006 01:00
 NotAfter: 17/07/2036 00:59
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 4:
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: 25/07/2012 01:00
 NotAfter: 26/07/2013 00:59
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\noradila\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\noradila\TICLOU~1\util\\ti2.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 6:
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: 08/02/2010 01:00
 NotAfter: 08/02/2020 00:59
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 5:
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: 08/11/2006 01:00
 NotAfter: 17/07/2036 00:59
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: 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: 04/10/2011 01:00
 NotAfter: 04/10/2012 00:59
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\noradila\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\noradila\TICLOU~1\util\\ti3.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 6:
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: 08/02/2010 01:00
 NotAfter: 08/02/2020 00:59
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 5:
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: 08/11/2006 01:00
 NotAfter: 17/07/2036 00:59
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: 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: 15/04/2014 01:00
 NotAfter: 17/04/2015 00:59
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\noradila\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\noradila\TICLOU~1\util\\ti4.p7b 
TrustedPublisher
Related Certificates:

Exact match:
Element 6:
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: 08/02/2010 01:00
 NotAfter: 08/02/2020 00:59
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 5:
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: 08/11/2006 01:00
 NotAfter: 17/07/2036 00:59
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 0:
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: 26/02/2014 01:00
 NotAfter: 26/02/2017 00:59
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\noradila\TICloudAgent/node.bat 
Script exit code: 1

Script output:
 Installing support for component : xds110_drivers
Finished

Script stderr:
 Program ended with an error exit code

Error running C:\Users\noradila\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 08/18/2015 at 12:28:49

    I notice that there's an error "Error running C:\Users\noradila\TICloudAgent/node.bat  : Program ended with an error exit code"

    log from TICloudAgent

    2015-08-18T11:28:37.971Z - info: Overridden Proxy =  source=unknown
2015-08-18T11:28:37.987Z - info: Creating db dir : C:\Users\noradila\AppData\Local\TEXASI~1\TICLOU~1\db source=unknown
2015-08-18T11:28:37.987Z - info: Creating loaders dir : C:\Users\noradila\AppData\Local\TEXASI~1\TICLOU~1\loaders source=unknown
2015-08-18T11:28:37.987Z - info: Could not open installed.json : Error: ENOENT, no such file or directory 'C:\Users\noradila\AppData\Local\TEXASI~1\TICLOU~1\db\installed.json' source=unknown
2015-08-18T11:28:37.987Z - info: Could not open targets.json : Error: ENOENT, no such file or directory 'C:\Users\noradila\AppData\Local\TEXASI~1\TICLOU~1\db\targets.json' source=unknown
2015-08-18T11:28:37.987Z - info: Getting Component Info: dev.ti.com/.../getComponentInfo source=unknown
2015-08-18T11:28:37.987Z - info: Looking up proxy settings for url http://dev.ti.com source=unknown
2015-08-18T11:28:40.581Z - info: Setting proxy to wwwcache.ee.ucl.ac.uk:8080
 source=unknown
2015-08-18T11:28:40.581Z - info: installer.js using proxy: wwwcache.ee.ucl.ac.uk:8080
 source=unknown
2015-08-18T11:36:23.416Z - info: Staring directory : C:\Users\noradila\TICLOU~1\src source=unknown
2015-08-18T11:36:23.418Z - info: Starting Agent! source=unknown
2015-08-18T11:36:23.423Z - info: Module( Agent )->Web socket server started! source=unknown
2015-08-18T11:36:23.426Z - info: Discovered Module : DS source=unknown
2015-08-18T11:36:23.426Z - info: Discovered Module : File source=unknown
2015-08-18T11:36:23.428Z - info: Discovered Module : Flash source=unknown
2015-08-18T11:36:23.453Z - info: Discovered Module : Serial source=unknown
2015-08-18T11:36:23.456Z - info: Discovered Module : TargetSupport source=unknown
2015-08-18T11:36:23.456Z - info: len= source=unknown
2015-08-18T11:36:23.456Z - info: <Buffer 1e 00 00 00> source=unknown
2015-08-18T11:36:23.456Z - info: buf= source=unknown
2015-08-18T11:36:23.456Z - info: <Buffer 7b 22 70 6f 72 74 22 3a 34 39 35 37 30 2c 22 76 65 72 73 69 6f 6e 22 3a 22 32 2e 32 22 7d> source=unknown
2015-08-18T11:36:23.468Z - info: Module( Agent )->Exec Command : listCommands:1 source=unknown
2015-08-18T11:36:23.468Z - info: Module( Agent )->Ret Command ( response) : listCommands : 1 source=unknown
2015-08-18T11:36:23.471Z - info: Module( Agent )->Exec Command : addConfigProperty:2 source=unknown
2015-08-18T11:36:23.471Z - info: Setting property cloudAgentInstallerServerURL : dev.ti.com/ticloudagentinstaller source=unknown
2015-08-18T11:36:23.471Z - info: Module( Agent )->Ret Command ( response) : addConfigProperty : 2 source=unknown
2015-08-18T11:36:30.636Z - info: Module( Agent )->Exec Command : createSubModule:3 source=unknown
2015-08-18T11:36:30.636Z - info: Module( Agent )->Creating Sub Module : File source=unknown
2015-08-18T11:36:30.638Z - info: Module( File )->Web socket server started! source=unknown
2015-08-18T11:36:30.638Z - info: Module( Agent )->Ret Command ( response) : createSubModule : 3 source=unknown
2015-08-18T11:36:30.658Z - info: Module( File )->Exec Command : listCommands:1 source=unknown
2015-08-18T11:36:30.658Z - info: Module( File )->Ret Command ( response) : listCommands : 1 source=unknown
2015-08-18T11:36:30.916Z - info: Module( File )->Exec Command : write:2 source=unknown
2015-08-18T11:36:30.918Z - info: Module( File )->Ret Command ( response) : write : 2 source=unknown
2015-08-18T11:36:30.926Z - info: Module( Agent )->Exec Command : createSubModule:4 source=unknown
2015-08-18T11:36:30.926Z - info: Module( Agent )->Creating Sub Module : TargetSupport source=unknown
2015-08-18T11:36:31.278Z - info: Overridden Proxy =  source=unknown
2015-08-18T11:36:31.281Z - info: Could not open installed.json : Error: ENOENT, no such file or directory 'C:\Users\noradila\AppData\Local\TEXASI~1\TICLOU~1\db\installed.json' source=unknown
2015-08-18T11:36:31.281Z - info: Could not open targets.json : Error: ENOENT, no such file or directory 'C:\Users\noradila\AppData\Local\TEXASI~1\TICLOU~1\db\targets.json' source=unknown
2015-08-18T11:36:31.283Z - info: Module( TargetSupport )->Web socket server started! source=unknown
2015-08-18T11:36:31.283Z - info: Module( Agent )->Ret Command ( response) : createSubModule : 4 source=unknown
2015-08-18T11:36:31.288Z - info: Module( TargetSupport )->Exec Command : listCommands:1 source=unknown
2015-08-18T11:36:31.288Z - info: Module( TargetSupport )->Ret Command ( response) : listCommands : 1 source=unknown
2015-08-18T11:36:31.288Z - info: Module( TargetSupport )->Exec Command : add:2 source=unknown
2015-08-18T11:36:31.291Z - info: Getting Install Info: dev.ti.com/.../getInstallInfo;deviceID=cc2650f128&connectionID=TIXDS110_Connection source=unknown
2015-08-18T11:36:31.291Z - info: Looking up proxy settings for url dev.ti.com/ticloudagentinstaller source=unknown
2015-08-18T11:36:31.458Z - info: Setting proxy to wwwcache.ee.ucl.ac.uk:8080
 source=unknown
2015-08-18T11:36:31.458Z - info: installer.js using proxy: wwwcache.ee.ucl.ac.uk:8080
 source=unknown
2015-08-18T11:36:33.006Z - info: An error occurred while retrieving information from the remote server. The most likely cause of this is incorrect proxy settings.
To manually override the proxy settings see : C:\Users\noradila\TICLOU~1\util\proxy.js
The Cloud IDE page needs to be refreshed for the changes to take effect
 source=unknown
2015-08-18T11:36:33.006Z - info: Module( TargetSupport )->Ret Command ( error) : add : 2 source=unknown

    I couldn't find the file to override the proxy. 

  • 0 in reply to Adila
    TI__Intellectual 2265 points
    There is no proxy.js at "c:\Users\noradila\TICloudAgent\util"
  • 0 in reply to Mandeep Deol
    TI__Intellectual 2265 points
    Can you also confirm that these folders are not empty

    - %USERPROFILE%\TICloudAgent
    - %LOCALAPPDATA%\Texas Instruments\TICloudAgent

    Paste the addresses into file explorer.
  • 0 in reply to Mandeep Deol
    Prodigy 140 points

    yes those folders are not empty.

    I set to bypass the proxy and didn't get that error anymore at %USERPROFILE%\TICloudAgent\util\proxy.js to 

    module.exports.proxy = "DIRECT"

    However, got these

    "Cortex_M3_0Memory Map Initialization Complete.

    Cortex_M3_0Failed Board Reset

    IcePick_C: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: invalid firmware update, invalid  XDS110 serial number, or faulty USB connection. The firmware and  serial number may be updated using the xdsdfu utility found in  the .../ccs_base/common/uscif/xds110 directory of your  installation. View the ReadMe.txt file there for instructions. (Emulation package 5.1.641.0)"
    I couldn't find .../ccs_base/common/uscif/xds110 directory
    I was reading 

    http://processors.wiki.ti.com/index.php/CC13xx_CC26xx_Tools_Overview#Tips_.26_Tricks

     and it says about battery
    Could it be because the battery is weak? or totally has nothing to do with the battery?
    Also, I prefer to use the cloud but it is better to use the CCS that is downloaded to the computer?
    It seems to have more help for these kind of problems with it
    Thanks,
    Adila
  • 0 in reply to Adila
    TI__Intellectual 2265 points

    Adila,

    Good to know that the Cloud Agent is working. The error you posted is coming from the emulation stack. I'll try to get some one more familiar with that to help you.

    Regards,
    Mandeep

  • 0 in reply to Mandeep Deol
    TI__Guru**** 169894 points
    Adila,

    I just got this very same error with my Sensortag DevPack. I basically removed the battery of mine and tried to program the device. Thus it is possible that insufficient power is causing problems.

    The DevPack is somewhat unique in the sense that it is partially powered by the SensorTag itself - thus the error message is vague. When using other boards and JTAG debuggers, powering off the device brings a more meaningful error message (target power failure).

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 140 points

    Hi Rafael,

    I replaced the battery with a new one and it doesn't solve the problem.

    Any idea what should I try doing to make it work?

    Thanks,

    Adila

  • 0 in reply to Adila
    TI__Guru**** 169894 points
    Adila,

    One additional detail I noticed is that sometimes, when I connect the DevPack to my PC its green LED is not lit - irrespective of the power status of the SensorTag. When this happens, the CCS Cloud fails to connect to the device with the same error as above.

    In this case, when I disconnect and reconnect the USB cable (or, in other instances, I have to change the USB port) the LED on the DevPack lits and I am able to connect.

    I can't precisely tell why this is happening - as I said earlier, the DevPack is somewhat unique in its HW design and it seems to behave somewhat differently than my other XDS110 JTAG debugger on the MSP432 Launchpad.

    In any case, please give this a try and see if that helps you solve the issue.

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 140 points

    Hi Rafael,

    The DevPack and SensorTag LED are both lit when I connect to the PC.

    I changed the USB port (in case that is the problem) and still get the same error message :(

    One thing that I notice is that the SensorTag LED doesn't lit on when I attach the DevPack to it (not connecting to the PC yet). I would assume that it should lit since the battery is on. Or is it how it's suppose to be?

    Thanks,

    Adila