• TI Thinks Resolved

CCS/TM4C123GH6PM: TI Cloud Agent setup issues for GUI Composer

Prodigy 30 points

Replies: 8

Views: 205

Part Number: TM4C123GH6PM

Tool/software: Code Composer Studio

Trying to set up the online GUI Composer 2, and I'm having issues connecting to the device:

I checked the config.json in the TICloudAgent folder and this is the result:

Can someone help me set this up correctly? Many thanks.

Apologies if this isn't the correct forum, I'm new here.

  • Hi Dan,
    This is the correct forum. Thank you for reporting the issue and sorry for the delayed response. I escalated the issue to our engineering team and will let you know of any response I get.

    btw - what is your full username? I see the 8.3 name as DANSPI~1

    Thanks
    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    Thanks for getting back to me! For reference, DANSPI~1 is just a trick the windows file system uses to shorten my username (replacing the path with the actual username is fine for traversing the file system e.g. "C:\Users\Dan Spingarn\AppData\Local\Texas Instruments" and "C:\Users\DANSPI~1\AppData\Local\Texas Instruments" would go to the same location.

    What's odd to me is that the file path when searched for cuts off at the space in "Texas Instruments".

  • In reply to Dan Spingarn:

    Note that in certain instances, a space in your username can cause issues:
    e2e.ti.com/.../2734766

    It doesn't look like the root cause here but it may cause issues down the road

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • Genius 13750 points

    We've been trying to figure out why, in a few isolated cases, the path in config.json is not converted to a Windows 8.3 path (long paths seems to cause problems elsewhere but not on all PCs). The issue has not been reproducible for us. 

    Could you try a couple of things?  First, if you delete the C:\Users\DANSPI~1\TICloudAgent folder and re-run the ticloudagent__*.exe installer that should still be in your downloads folder, does the config,json get  re-created with 8.3 paths?

    Could you also edit the last part of the path in config.json from "\\Texas Instruments\TICloudAgent" to "\\TEXASI~1\\TICLOU~1" ?  Does GUI composer work any differently after this change?

  • In reply to AndyW:

    Deleted the indicated folder and redownloaded with the exe installer. Config.json is re-created with the same path as before

    Edited the path and the path wasn't found. Trying the symbol TEXASI~1 did not work, nor did TICLOU~1, in windows file explorer

    I decided to peek at what the console was displaying in my browser (Chrome v. 70, also tried in firefox but same exact issue). Here's what I got after hitting the "flash" button.

    So I went back and restored the file path to the default, and looked at the console again, and this is what I got:

    (Scrolled down a line or two and got this):

    Hopefully someone can glean some more information from this!

  • In reply to Dan Spingarn:

    Hi Dan,
    Sorry for the delayed response. The issue is still under investigate, but frankly we are running out of troubleshooting ideas. Just wanted to check one thing - did you try connecting to the target from CCS Cloud outside of GUI Composer?

    Thanks
    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    Hi Dan,
    Just following up with you regarding my last post regarding if you tried connecting to the target from CCS Cloud directly (outside GUI Composer).
    Thanks
    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    Hello,
    I haven’t heard back from you, hence this issue is being closed. If you wish to continue the discussion, please post a reply with an update below (or create a new thread).

    Thanks,
    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ