• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 2226 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:

TI cloud IDE installation for ti cloud

CCS/MSP430FR6989: TI cloud IDE installation for ti cloud

Hendrik
Prodigy 70 points

Part Number: MSP430FR6989
Other Parts Discussed in Thread: ENERGIA

Tool/software: Code Composer Studio

Hi TI-Support,

I want to use CCS Cloud with Google Chrome (lastest version) on a Win10 64-Bit System, but for some reason TI Cloud Agent fails to start when I want to run a project.
The extension TI Cloud Bridge is enabled and incognito mode is off.
I already deinstalled the TI Could Agent and performed all the actions CCS Cloud want me to perfrom again, to get that fixed. but  the error still ocurrs after a refresh or even a restart.
Do you have any Idea what else could be the reason for that?

Regards

Hendrik

  • 0
    TI__Genius 16510 points

    Hi Hendrik,

    When you say "TI Cloud Agent fails to start when I want to run a project", I want to make sure I understand.  Do you mean that when you click the run button in the CCS Cloud IDE, it always asks you to install both the extension and Cloud agent even though you have already installed it? If you're getting an error message or other dialog, could you describe this?  Thanks!

  • 0 in reply to AndyW
    Prodigy 70 points
    Hi Andy,

    thanks for your replay. When I hit the run-button, CCS Could always ask's me to install TI Cloud Manager again and again, regardless of the fact, that it is already installed - at least I can see it in the list of installed software on my PC.

    The dialog is the following:
    Could not launch TI Cloud Agent: Failed to start TICloudAgent. Please perform the actions listed below and try your operation again.
    Step 1: Download and install the TI Cloud Agent Application

    The extension seems to work. That's strange somehow and I dont have an idea what to do, to get that fixed. Maybe you can help.



    Thanks
    Hendrik
  • 0 in reply to Hendrik
    TI__Genius 16510 points

    Hendrik,

    Thanks for confirming. Some more questions:

    • Are you behind a proxy?
    • Does your Windows login account have admin privileges?
    • Could you generate a log file and post it here (see )

    Thanks, Andy

  • 0 in reply to AndyW
    Prodigy 70 points

    Hi Andy, 

    sorry for my late replay, was sick last week. Anyway regarding your questions Im behind a proxy and my general account has no admin privileges, but I installed TICloudAgent as admin. Pls find bellow the installation-logfile.

    Regards, 
    Hendrik 

    ________________________________________________________

    Log started 08/27/2018 at 13:01:45
    Preferred installation mode : win32
    Trying to init installer in mode win32
    Mode win32 successfully initialized
    [13:01:45] Installer name: ticloudagent__2__msp430 (1).exe
    [13:01:46] installer_command_line_arguments:
    [13:01:46] installer_command_line_arguments:
    Preparing to Install
    [13:01:53] BuildID: 0.5 1956
    Preparing to Install
    Unpacking files
    Removing Files
    [13:01:59] no C:\Users\install\AppData\Local\Texas Instruments\TICloudAgent
    [13:01:59] FEATURE_WEBSOCKET_MAXCONNECTIONSPERSERVER is set to 16.
    Installing npTICloudAgentLauncher.dll
    Executing regsvr32 /s C:\Users\install\TICloudAgent/plugins/npTICloudAgentLauncher.dll
    Script exit code: 0

    Script output:

    Script stderr:

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

    Script output:

    C:\Users\install\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\install\TICLOU~1\util\\ti1.p7b
    TrustedPublisher "Vertrauenswürdige Herausgeber"
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 6:
    Seriennummer: 5200e5aa2556fc1a86ed96c9d44b33c7
    Aussteller: 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
    Nicht vor: 08.02.2010 02:00
    Nicht nach: 08.02.2020 01:59
    Antragsteller: 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
    Kein Stammzertifikat
    Zertifikathash(sha1): 495847a93187cfb8c71f840cb7b41497ad95c64f

    Das Zertifikat "VeriSign Class 3 Code Signing 2010 CA" befindet sich bereits im Speicher.
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 5:
    Seriennummer: 18dad19e267de8bb4a2158cdcc6b3b4a
    Aussteller: 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
    Nicht vor: 08.11.2006 02:00
    Nicht nach: 17.07.2036 01:59
    Antragsteller: 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
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Stammzertifikat: Antragsteller stimmt mit Aussteller überein
    Zertifikathash(sha1): 4eb6d578499b1ccf5f581ead56be3d9b6744a5e5

    Das Zertifikat "VeriSign Class 3 Public Primary Certification Authority - G5" befindet sich bereits im Speicher.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 4:
    Seriennummer: 7ba5aab20f054f4560dedc8991e62a27
    Aussteller: 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
    Nicht vor: 25.07.2012 02:00
    Nicht nach: 26.07.2013 01:59
    Antragsteller: CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US
    Kein Stammzertifikat
    Zertifikathash(sha1): 50fcdbea5930e04e0ced6746715f2380ec6d03a9

    Das Zertifikat "Texas Instruments Incorporated" befindet sich bereits im Speicher.
    CertUtil: -addstore-Befehl wurde erfolgreich ausgeführt.

    C:\Users\install\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\install\TICLOU~1\util\\ti2.p7b
    TrustedPublisher "Vertrauenswürdige Herausgeber"
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 6:
    Seriennummer: 5200e5aa2556fc1a86ed96c9d44b33c7
    Aussteller: 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
    Nicht vor: 08.02.2010 02:00
    Nicht nach: 08.02.2020 01:59
    Antragsteller: 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
    Kein Stammzertifikat
    Zertifikathash(sha1): 495847a93187cfb8c71f840cb7b41497ad95c64f

    Das Zertifikat "VeriSign Class 3 Code Signing 2010 CA" befindet sich bereits im Speicher.
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 5:
    Seriennummer: 18dad19e267de8bb4a2158cdcc6b3b4a
    Aussteller: 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
    Nicht vor: 08.11.2006 02:00
    Nicht nach: 17.07.2036 01:59
    Antragsteller: 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
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Stammzertifikat: Antragsteller stimmt mit Aussteller überein
    Zertifikathash(sha1): 4eb6d578499b1ccf5f581ead56be3d9b6744a5e5

    Das Zertifikat "VeriSign Class 3 Public Primary Certification Authority - G5" befindet sich bereits im Speicher.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 2:
    Seriennummer: 1124ac88d0430481e0eaa40ef04118a9
    Aussteller: 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
    Nicht vor: 04.10.2011 02:00
    Nicht nach: 04.10.2012 01:59
    Antragsteller: 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
    Kein Stammzertifikat
    Zertifikathash(sha1): bcccf26267cee6b58b3818782d26f4307bcb6a4f

    Das Zertifikat "Texas Instruments Inc" befindet sich bereits im Speicher.
    CertUtil: -addstore-Befehl wurde erfolgreich ausgeführt.

    C:\Users\install\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\install\TICLOU~1\util\\ti3.p7b
    TrustedPublisher "Vertrauenswürdige Herausgeber"
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 6:
    Seriennummer: 5200e5aa2556fc1a86ed96c9d44b33c7
    Aussteller: 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
    Nicht vor: 08.02.2010 02:00
    Nicht nach: 08.02.2020 01:59
    Antragsteller: 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
    Kein Stammzertifikat
    Zertifikathash(sha1): 495847a93187cfb8c71f840cb7b41497ad95c64f

    Das Zertifikat "VeriSign Class 3 Code Signing 2010 CA" befindet sich bereits im Speicher.
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 5:
    Seriennummer: 18dad19e267de8bb4a2158cdcc6b3b4a
    Aussteller: 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
    Nicht vor: 08.11.2006 02:00
    Nicht nach: 17.07.2036 01:59
    Antragsteller: 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
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Stammzertifikat: Antragsteller stimmt mit Aussteller überein
    Zertifikathash(sha1): 4eb6d578499b1ccf5f581ead56be3d9b6744a5e5

    Das Zertifikat "VeriSign Class 3 Public Primary Certification Authority - G5" befindet sich bereits im Speicher.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 1:
    Seriennummer: 558c8cedb57ce54fa6fb351fb84b222f
    Aussteller: 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
    Nicht vor: 15.04.2014 02:00
    Nicht nach: 17.04.2015 01:59
    Antragsteller: CN=Texas Instruments, OU=WCS, O=Texas Instruments, L=Dallas, S=Texas, C=US
    Kein Stammzertifikat
    Zertifikathash(sha1): c76e488afc115ad09da669cbe413316fe56e9438

    Das Zertifikat "Texas Instruments" befindet sich bereits im Speicher.
    CertUtil: -addstore-Befehl wurde erfolgreich ausgeführt.

    C:\Users\install\TICloudAgent\util>certutil -addstore "TrustedPublisher" C:\Users\install\TICLOU~1\util\\ti4.p7b
    TrustedPublisher "Vertrauenswürdige Herausgeber"
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 6:
    Seriennummer: 5200e5aa2556fc1a86ed96c9d44b33c7
    Aussteller: 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
    Nicht vor: 08.02.2010 02:00
    Nicht nach: 08.02.2020 01:59
    Antragsteller: 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
    Kein Stammzertifikat
    Zertifikathash(sha1): 495847a93187cfb8c71f840cb7b41497ad95c64f

    Das Zertifikat "VeriSign Class 3 Code Signing 2010 CA" befindet sich bereits im Speicher.
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 5:
    Seriennummer: 18dad19e267de8bb4a2158cdcc6b3b4a
    Aussteller: 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
    Nicht vor: 08.11.2006 02:00
    Nicht nach: 17.07.2036 01:59
    Antragsteller: 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
    Signatur stimmt mit dem öffentlichen Schlüssel überein.
    Stammzertifikat: Antragsteller stimmt mit Aussteller überein
    Zertifikathash(sha1): 4eb6d578499b1ccf5f581ead56be3d9b6744a5e5

    Das Zertifikat "VeriSign Class 3 Public Primary Certification Authority - G5" befindet sich bereits im Speicher.
    Verwandte Zertifikate:

    Genaue Übereinstimmung:
    Element 0:
    Seriennummer: 39ad63d2f5c9efdc46d734ae5e381b8f
    Aussteller: 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
    Nicht vor: 26.02.2014 02:00
    Nicht nach: 26.02.2017 01:59
    Antragsteller: CN=Texas Instruments Incorporated, OU=Digital ID Class 3 - Microsoft Software Validation v2, O=Texas Instruments Incorporated, L=Dallas, S=Texas, C=US
    Kein Stammzertifikat
    Zertifikathash(sha1): ee0c8ba018ce926432c3cc23523a34073d01954a

    Das Zertifikat "Texas Instruments Incorporated" befindet sich bereits im Speicher.
    CertUtil: -addstore-Befehl wurde erfolgreich ausgeführt.

    Script stderr:

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

    Script output:
    Installing windows drivers for [core, msp430, msp430]
    Additional files need to be installed to support selected configuration. Starting Install Process.

    ccs_base/DebugServer/propertyDB/MSP430_FlashProperties.xml
    ccs_base/emulation/drivers/msp430/USB_CDC/installCerts.bat
    ccs_base/emulation/drivers/msp430/USB_CDC/USB_CDC_CERT.p7b
    ccs_base/emulation/tpi/tpi_ds.ini
    ccs_base/common/targetdb/drivers/TI_reg_ids/MSP430_regids.xml
    ccs_base/emulation/drivers/msp430/USB_CDC/msp430tools.cat
    ccs_base/emulation/tpi/TPIMSP430.dll
    ccs_base/DebugServer/bin/FlashMSP430.dll
    ccs_base/common/bin/MSPAutoDetector.exe
    ccs_base/common/bin/ti_logger.dll
    ccs_base/emulation/drivers/msp430/USB_FET_Win7_8_10_64/umpf3410.i51
    ccs_base/emulation/drivers/msp430/USB_FET_Win7_8_10_64/ump3410.cat
    ccs_base/emulation/drivers/msp430/USB_CDC/msp430tools.inf
    ccs_base/emulation/drivers/msp430/USB_FET_Win7_8_10_64/usbuart3410.inf
    ccs_base/emulation/drivers/msp430/USB_eZ-RF/USB_eZ_RF.p7b
    ccs_base/emulation/drivers/msp430/USB_eZ-RF/430cdc.cat
    ccs_base/emulation/drivers/msp430/USB_FET_Win7_8_10_64/umpusbvista.sys
    ccs_base/emulation/drivers/msp430/USB_eZ-RF/430CDC.inf
    ccs_base/emulation/drivers/msp430/USB_eZ-RF/installCerts.bat
    ccs_base/common/targetdb/setup_parser.xsd
    ccs_base/common/bin/CCReg.dll
    ccs_base/common/targetdb/setup_parser_cache.xsd
    ccs_base/common/bin/MiniDump.dll
    ccs_base/emulation/drivers/msp430/USB_FET_Win7_8_10_64/difxapi.dll
    ccs_base/DebugServer/bin/BatchDriverInstaller.exe
    ccs_base/DebugServer/drivers/MSP430.dll
    ccs_base/DebugServer/bin/FlashDLLDB.xml
    ccs_base/common/bin/fsutil.dll
    ccs_base/DebugServer/bin/DebugProperties.dll
    ccs_base/DebugServer/bin/DSLite.exe
    ccs_base/common/bin/xerces-c_2_8.dll
    ccs_base/DebugServer/bin/LibraryLoader.dll
    ccs_base/common/bin/setup_parser.dll
    ccs_base/DebugServer/components/components.txt
    ccs_base/DebugServer/bin/tiofr_gnu.dll
    ccs_base/DebugServer/propertyDB/FlashPropertiesTranslator.xml
    ccs_base/DebugServer/propertyDB/PropertiesDB.xml
    ccs_base/DebugServer/schemas/PropertiesDB.xsd
    ccs_base/DebugServer/bin/XPCOMUtility.dll
    ccs_base/DebugServer/schemas/PropertiesSaveSetting.xsd
    ccs_base/DebugServer/bin/ti_xpcom.dll
    ccs_base/DebugServer/scripts/flash.dsls
    ccs_base/DebugServer/bin/tiofr11.dll
    ccs_base/DebugServer/bin/tiofr_tial.dll
    ccs_base/DebugServer/scripts/help.dsls
    ccs_base/DebugServer/scripts/load.dsls
    ccs_base/DebugServer/scripts/memory.dsls
    ccs_base/DebugServer/scripts/serial.dsls
    ccs_base/DebugServer/bin/api-ms-win-core-file-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-handle-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-debug-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-errorhandling-l1-1-0.dll
    ccs_base/DebugServer/bin/DebugServer.dll
    ccs_base/DebugServer/bin/api-ms-win-core-delayload-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-console-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-file-l1-2-0.dll
    ccs_base/emulation/drivers/msp430/USB_FET_Win7_8_10_64/WdfCoInstaller01009.dll
    ccs_base/DebugServer/bin/api-ms-win-core-fibers-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-file-l2-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-datetime-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-localization-l1-2-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-io-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-localregistry-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-heap-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-libraryloader-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-interlocked-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-memory-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-localization-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-namedpipe-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-misc-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-profile-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-synch-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-string-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-processthreads-l1-1-1.dll
    ccs_base/DebugServer/bin/api-ms-win-core-processenvironment-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-sysinfo-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-threadpool-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-processthreads-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-synch-l1-2-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-rtlsupport-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-xstate-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-timezone-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-xstate-l2-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-filesystem-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-core-util-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-conio-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-locale-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-convert-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-environment-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-heap-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-multibyte-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-math-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-process-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-private-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-runtime-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-stdio-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-utility-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-string-l1-1-0.dll
    ccs_base/DebugServer/bin/api-ms-win-crt-time-l1-1-0.dll
    ccs_base/common/targetdb/drivers/TI_reg_ids/regids.xsd
    ccs_base/emulation/tpi/tpi.ini
    ccs_base/DebugServer/bin/vcruntime140.dll
    ccs_base/DebugServer/bin/msvcp120.dll
    ccs_base/DebugServer/bin/msvcp140.dll
    ccs_base/DebugServer/bin/ucrtbase.dll
    ccs_base/DebugServer/bin/msvcr120.dll
    Installing Windows driver (please accept the UAC dialog): ccs_base/emulation/drivers/msp430/USB_CDC, ccs_base/emulation/drivers/msp430/USB_FET_Win7_8_10_64, ccs_base/emulation/drivers/msp430/USB_eZ-RF.

    Installation completed.

    Finished

    Script stderr:

    Creating Uninstaller
    Creating uninstaller 25%
    Creating uninstaller 50%
    Creating uninstaller 75%
    Creating uninstaller 100%
    Uninstaller icon changed
    Installation completed
    Log finished 08/27/2018 at 13:02:17

  • 0 in reply to Hendrik
    TI__Genius 16510 points

    Hi Hendrik,

    There is a limitation in the CCS cloud installation that prevents it from working for "Windows Standard Users".  When a Windows user account is created as a "standard user", Windows will prompt you to enter the admin user ID and password whenever admin actions are required. Windows will then run the action using the credentials of the Admin account.  This creates a problem for CCS cloud, as the CCS Cloud installer will put some files in the administrator's account instead of the original user. The end result is the CCS cloud agent will not work.  Note that the Windows UAC prompt is different than the prompt to login as the Administrator.  In the UAC case, Windows is asking you if it is OK to run the process with elevated permissions but it does not change the login credentials of the calling process.

    I can't tell from the log if you are using a setup where your user account is a standard user, but if you say your account does not have admin rights this is probably what is going on.  I don't have a workaround in CCS cloud for this issue, but we are planning on addressing it in coming months.  An alternative for you may be to look into using the Energia IDE, or the full CCS install.  Both these require a larger installation, but should work in your scenario.

  • 0 in reply to AndyW
    Prodigy 70 points

    Hi Andy,

    thanks for getting back and sorry for my late reply. Indeed the limited rights have been the reason for the problem. Meanwhile I decided to use CCS and Energia as IDE which work both fine for me. 

    Thanks again and have a nice day.

    Hendrik