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

CCS/F28M36H33B2: Ti Cloud Agent not connecting with Gui Composer

Albert Smit
Intellectual 730 points
Part Number: F28M36H33B2

Tool/software: Code Composer Studio

I connot get the new Cloud based Gui Composer to connect to my device and run the Gui directly from the cloud using the TI Cloud Agent Bridge. I am able to create my Gui and then export it as a CCS Desktop View, copy it into the folder and run the application. But this is quite a hassle while I'm still busy developing and testing the Gui. So I have configured an XDS device under the Target Communication Settings in CCS GUI Composer Cloud so that I can program my device and run the Gui from the Cloud Gui composer. When I then try to connect from the Target Communication Settings dialog it just hangs with "Connecting to TI Cloud Agent..." message. I tried to find the TICloudAgent.log file to add it here but I could fine any such file under the path "ti/node/logs/TICloudAgent.log". I'm using Spectrum Digital XDS 200 Debug probe and the Blackhawk XDS 560, does the Cloud agent support these emulators or does it only work with the TI XDS emulators? 

  • 0
    TI__Guru**** 173310 points

    The Cloud Agent should support those emulators. In fact I just tried out a F28M35 Experimenter kit and XDS200 debug probe with Gui Composer and was able to establish the connection. Did the Cloud Agent installation complete properly? And did it prompt you for any driver installation (for the debug probe)? 

  • 0 in reply to AartiG
    Intellectual 730 points

    Yes, both the application and browser extension installed successfully. There was no prompt for any driver installation. How can I install the drivers?

  • 0
    TI__Genius 16025 points

    HI Albert,

    Can you try to create a simple project inside CCS Cloud and see if you can debug the project on the cloud? I don't have this device and I am wonder if this is GC specific issue or a general cloudagent issue. The cloudagent is shared between CCS Cloud and GC. Do note that you will need to terminate the debug session inside CCS Cloud before you can connect your GUI App in GC.

    Patrick

  • 0 in reply to Patrick Chuong
    TI__Genius 16025 points
    Albert,

    We don't have a good support for multi-core device in the cloud, ti looks like you might be using a multi-core device. You can create a ccxml file in CCS and bypass one of the core using the Target Configuration editor inside CCS, than update this file to the GC app, the file need to have a gcxml file extension when you upload it to GC.

    Regards,
    Patrick
  • 0 in reply to Patrick Chuong
    Intellectual 730 points

    It does not work from CCS cloud as well. If I go to Target > Connect COM port, it says: "Opening COM port failed. The project does not have Target Type". I don't know where to set the target type.

    Yes I am using a Multi Core. How do I bypass the one core in the Target Configuration file? If I create a new configuration file and select the F28M36 it automatically adds both cores (M3 and C28) to the configuration, I can not remove one. Under the advanced tab in the Target Configuration Editor I can only delete the entire device, not just one core. 

    Where do I add the configuration file to the GC app? The cloud GC only gives the ability to upload the executable (.out) file under Target Program. I don't know where to upload the configuration file (.gcxml).

    Please can you give more instructions on how to do this?

    In the TI Cloud Agent wiki page it says the following:

    Device-specific support files are downloaded as needed to minimize the installed footprint size. The initial installation requires elevated permissions in order to install hardware drivers.

    I did not install any such device specific support files or set any elevated permissions. Is this perhaps what I am missing? Where do I get these device specific files and set the permissions?

    Thanks

  • 0 in reply to Albert Smit
    TI__Genius 16025 points

    Hi Albert,

    The applications in the cloud don't have good support for multi-core at the moment, so you are likely run into the issue where the application doesn't know how to connect to the core that you wanted.

    To Bypass a core in CCS Desktop:
    In Target Configuration Editor, switch to the advanced tab and check the 'Bypass' for the core that you don't use. See the attached screen capture.

    To upload a .gcxml file to GC:
    Within the project view, select the project that you want to upload the .gcxml file. Then, right click on the project to show the context, click on "Add File" and select the .gcxml file (rename .ccxml file to .gcxml file extension before upload). See the attached screen capture.

    CloudAgent will install the required device driver files as long as you have an internet connection. 

    Regards,
    Patrick

  • 0 in reply to Patrick Chuong
    Intellectual 730 points

    I have done exactly as your instructions but it still just hangs when trying to connect.

  • 0 in reply to Albert Smit
    TI__Genius 16025 points

    Hi Albert,

    You can add these two lines into ticloudagent.bat(.sh) file to enable logging, the file is located in your user home directory under the folder TICloudAgent. Please attach the log file here. Thanks.

    set TI_DS_ENABLE_LOGGING=1
    set TI_DS_LOGGING_OUTPUT=<path to log file>

    Patrick

  • 0 in reply to Patrick Chuong
    Intellectual 730 points

    I added the lines. ticloundagent.bat file looks like this:

    @echo off

    set PATH=%~dp0\util;%PATH%
    set TI_DS_ENABLE_LOGGING=1
    set TI_DS_LOGGING_OUTPUT="C:\ti\log.txt"

    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

    "%~dp0/node.exe" "%~dp0/src/main_chrome.js" %*
    goto END

    :NOT_CHROME

    "%~dp0/node.exe" "%~dp0/src/main.js" %*

    :END

    I still doesn't create a log file when I try to connect and it still hangs.

    The only log file I can find is ticloudagent_install.log :

    0576.ticloudagent_install.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    Log started 07/31/2017 at 16:00:58
    Preferred installation mode : win32
    Trying to init installer in mode win32
    Mode win32 successfully initialized
    [16:01:00] Installer name: ticloudagent__2 (1).exe
    [16:01:02] installer_command_line_arguments:
    [16:01:02] installer_command_line_arguments:
    Preparing to Install
    [16:01:08] BuildID: 0.5 1462
    [16:06:49] found C:\Users\asmit\TICloudAgent\uninstall.exe
    Uninstalling TICloudAgent from C:\Users\asmit
    Executing C:\Users\asmit\TICloudAgent\uninstall.exe --mode unattended
    Script exit code: 0
    Script output:
    Script stderr:
    Preparing to Install
    Unpacking files
    [16:08:21] no C:\Users\asmit\AppData\Local\Texas Instruments\TICloudAgent
    [16:08:21] 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
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Albert Smit
    TI__Genius 16460 points

    Albert,

    The install log turns out to be useful as the initial install seems to be failing.  Could you post the contents of C:\Users\asmit\TICloudAgent\node.bat here (it should be just a few lines). Could you also open a windows command prompt, CD to C:\Users\asmit\TICloudAgent\ , and run node.bat  and also post the output here. The output of this may be useful to see what is going wrong.

  • 0 in reply to AndyW
    Intellectual 730 points

    node.bat file contents:

    @echo off
    set PATH=%~dp0\util;%PATH%
    reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86" > NUL && set OS_BIT_SIZE=32||set OS_BIT_SIZE=64
    C:\Users\asmit\TICloudAgent/node C:\Users\asmit\TICloudAgent/src/installer/cli.js --installer ticloudagent__2 (1).exe --quiet true

    node.bat output after execution:

    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
    no valid command line parameter passed


    C:\Users\asmit\TICloudAgent>

  • 0 in reply to Albert Smit
    TI__Genius 16460 points

    Thank you Albert.

    A couple of other items that will help track this down:

    • You already added lines to enable logging in ticloudagent.bat.  From a Windows command prompt, could you run this file from the command line and post both the log file and console output here:

    C:\Users\asmit\TICloudAgent>ticloudagent.bat

    • Regarding this issue from an earlier reply
      • It does not work from CCS cloud as well. If I go to Target > Connect COM port, it says: "Opening COM port failed. The project does not have Target Type". I don't know where to set the target type.

    The reason you see this message is the IDE was unable to determine the target type from the selected project. If the project you select in your workspace has a supported target configuration, it should be able to find a configuration.  Just to prove whether it is working elsewhere, you could create a project for a different device (say a 28027) and try the same thing.

    • Regarding the supported debug probes mentioned earlier.  We do not have support for 560-class debug probes in CCS cloud. XDS200 class probes should work though.

  • 0 in reply to AndyW
    Intellectual 730 points

    output of ticloudagent.bat:

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

    C:\Users\asmit>cd TICloudAgent

    C:\Users\asmit\TICloudAgent>ticloudagent
    ▲ {"port":56395,"version":"4.2"}

    log file attached.

    log_ticld.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    2017-08-03T10:03:24.018Z: Staring directory : C:\Users\asmit\TICloudAgent\src
    2017-08-03T10:03:24.020Z: Starting Agent!
    2017-08-03T10:03:24.030Z: Module( Agent )->Web socket server started!
    2017-08-03T10:03:25.151Z: Overridden Proxy =
    2017-08-03T10:03:25.165Z: Discovered Module : DeviceDetector
    2017-08-03T10:03:25.168Z: Discovered Module : DS
    2017-08-03T10:03:25.170Z: Discovered Module : EventBroker
    2017-08-03T10:03:25.175Z: Discovered Module : File
    2017-08-03T10:03:25.178Z: Discovered Module : Flash
    2017-08-03T10:03:25.181Z: rov_server_redirect: looking in: C:\Users\eclipse\dropins
    2017-08-03T10:03:25.182Z: rov_server_redirect: looking in: C:\Users\eclipse\plugins
    2017-08-03T10:03:25.184Z: rov_server_redirect: looking in: C:\Users\eclipse\Eclipse.app\Contents\Eclipse\dropins
    2017-08-03T10:03:25.185Z: rov_server_redirect: looking in: C:\Users\eclipse\Eclipse.app\Contents\Eclipse\plugins
    2017-08-03T10:03:25.187Z: 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\TICloudAgent\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-08-03T10:03:25.247Z: Discovered Module : Serial
    2017-08-03T10:03:25.251Z: Discovered Module : TargetSupport
    2017-08-03T10:03:25.253Z: Agent main module running on port 56395
    2017-08-03T10:03:25.255Z: len=
    2017-08-03T10:03:25.256Z: ·
    2017-08-03T10:03:25.257Z: buf=
    2017-08-03T10:03:25.258Z: {"port":56395,"version":"4.2"}
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX