• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 2876 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/TM4C1294NCPDT: GUI Composer CCSV7 is missing GUI wizard and menu say drop app into /eclipse/dropins-gc folder don't exist

Genatco
Guru 56033 points
Part Number: TM4C1294NCPDT


Tool/software: Code Composer Studio

Have a GUI composer project built in CCSV5.4 but lost original CCSV5.4 installation (bad HDD) though had previously saved the entire CCS5.4 workspace on another machine with standalone GUI files.   

1. Moved CCSv5.4 workspace composer folders (.GUIComposerWorkspace) into CCSv7 workspace but how to import?

2. There is no GUI Composer tool selection in View menu CCSv7 and opt to uninstall GUI Composer completely thinking bad JAR install. 

3. Download GUI Composer for CCS v1.0 application center and install to CCSv7, then GUI Composer tool exists in the perspective (View) but crashes in a long JAVA error exception when launched.

4. Uninstall all GUI Composers and put back the original V.6xxxxxxxx GUI composer files = back to square 1.

5. What does drop app into /eclipse/dropins-gc folder mean exactly? 

6. Added the CCS5.4 GUI Composer project under eclipse/gc/MyWebApp and it still not showing up in the view applications menu. 

  • 0
    Guru 56033 points

    BP101 said:
    Added the CCS5.4 GUI Composer project under eclipse/gc/MyWebApp and it still not showing up in the view applications menu

    Ended up reinstalling CCS5.4 in an other folder since patching GUI composer files did not correct but a small part of the main IDE feature. Reverting the feature to an earlier date; installer could not locate the IDE main feature GUI composer 1.0 repository in the TI download secession.

    BP101 said:
    5. What does drop app into /eclipse/dropins-gc folder mean exactly? 

    Still have not figured out why CCSV7 GUI composer launcher icon is missing from the perspective, reset perspective did not recover it.  

  • 0 in reply to Genatco
    TI__Genius 15700 points
    Hello,
    There are two versions of GUI Composer. Unfortunately, they are not backwards compatible. CCS v5.4 - CCS 6.2 provide GCv1. In CCSv6 and higher GCv1 is available through CCS App Center. Each version of GC also has GC Designer (tool to create GUIs) and GC Runtime (if you already have an app and just want to run it).

    CCS 6.2 from App Center brings in GC Designer and Runtime.

    CCSv7 straddles two versions of GC. Runtime for GCv1 is available in App Center, this allows you to run GCv1 applications in CCSv7. GCv2 designer is available at dev.ti.com/gc, there is no GCv2 designer available in CCS Desktop. GCv2 runtime is included in CCSv7, thus GCv2 apps can also be run in CCSv7 desktop.

    GCv1 required applications to be dropped into CCS Desktop "webapps" folder GCv2 uses "dropins-gc". If neither of those directories exist then they can be manually created.

    Hopefully this clarifies some of your questions.

    As a note: CCSv5.4 included very first release of GCv1. It might be best to stick with CCSv5.4. If you need to use CCS 6.2, due to need to support a new device, then the app may require some tweaking. Let me know if you need help.

    Martin
  • 0 in reply to MartinS
    Guru 56033 points

    MartinS said:
    CCSv7 straddles two versions of GC. Runtime for GCv1 is available in App Center,

    That is the problem CCSv7 installer is not correctly installing runtime GCv1 into the IDE perspective. The App center install over the existing IDE/GC backbone caused a huge JAVA exception train wreck and backbone structures showing as double IDE features. Removing the CCS7 GC backbone entirely from the IDE and installing the App center version placed a GCv1 icon in the perspective but when launched would create a very large Java exception. 

    It seems CCSv7 installer version of GC backbone 6.x is not compatible with the App center GCv1.0 version. 

    Ergo CCSv7 update to GCv1.0 runtime was no longer showing a selection Icon in the App center over the weekend.

  • 0 in reply to MartinS
    Guru 56033 points

    MartinS said:
    GCv1 required applications to be dropped into CCS Desktop "webapps" folder GCv2 uses "dropins-gc". If neither of those directories exist then they can be manually created.

    The GCv1.0 projects CCSv5.4 existed in the CCS workspace folders tree under ( .GUIComposerWS ) and not the "dropins-gc" folder. So this explanation makes no sense to me.

  • 0 in reply to Genatco
    TI__Genius 15700 points
    Please follow these steps:
    Install CCSv7 in New Directory
    Open CCS App Center and select GUI Composer Runtime v1
    After you restart CCS you should see View ->Gui Composer-> Applications v1 menu, which should be empty at this point.
    You can now unzip your GCv1 application into ccsv7\webapps folder, after a restart you should see your app under v1 menu.

    You are mixing different versions of GUI Composer which are not compatible.

    GCv1 which is only available in CCSv5.x and CCS 6.x and included Designer (tool to create GC Apps) and GC Runtime (features necessary to run GC apps).

    GCV1 Designer tool used .GUIComposerWS workspace to store your design. I.e. only the creator was able to run the app. If you wanted to distribute your GC APP to other developers they would then unzip the output into webapps folder, without the need to open GC Designer or import the app into GC Designer.

    Since CCSv7 does not have GCV1 designer, there is no .GUICOmposerWS area and thus the only thing you can do is install GC Runtime V1 and unzip your app into webapps folder. Once you restart CCS you should see the app under View -> GUI Composer -> Application v1

    dropins-gc follows similar pattern but it is applicable only to GCV2. Since your app is not a GCv2 app, then you should not be using dropins-gc.

    martin
  • 0 in reply to MartinS
    Guru 56033 points

    MartinS said:
    You are mixing different versions of GUI Composer which are not compatible.

    That is the GC1.0 version which was showing up in the application center of CCSv7. I didn't mix versions and the designer is not integrating properly into CCSV7. You seem to be saying our GC1.0 project started in CCsV5.4 can no longer be edited in CCSV7 even when there was never an NDNR of the TM4C1294NCPDT. 

    MartinS said:
    Since CCSv7 does not have GCV1 designer, there is no .GUICOmposerWS area and thus the only thing you can do is install GC Runtime V1 and unzip your app into webapps folder.

    That's the entire point I was making - why is the GC Divinci designer tools missing in CCSv7?

    The runtime GCv1 re-distributable launcher has a webapps folder and we manually copy all CCSV5.4 GCv1.0 designer files and achieve a very professional looking GUI environment under portable CE or other desktop access points. We view IOT for the ability to report status more than control highly complex systems where hackers could possibly intrude and cause mayhem in high voltage grid attached systems.

  • 0 in reply to Genatco
    TI__Genius 15700 points

    That is the GC1.0 version which was showing up in the application center of CCSv7. I didn't mix versions and the designer is not integrating properly into CCSV7. You seem to be saying our GC1.0 project started in CCsV5.4 can no longer be edited in CCSV7 even when there was never an NDNR of the TM4C1294NCPDT. 

    My comment about mixing versions was mostly related to workspace comments, dropins-gc is for GCv2 only. It was a reply to your reply which I copied below. 

         "The GCv1.0 projects CCSv5.4 existed in the CCS workspace folders tree under ( .GUIComposerWS ) and not the "dropins-gc" folder. So this explanation makes no sense to me."

    However, yes, GCv1 projects are no longer editable in CCSv7. If you need newer version of CCS than CCS5.4 then CCSv6.2 would be latest that does support editing of GCv1 projects. Is there a specific feature or functionality that you require that is available in CCSv7 that is not available in CCSv6.2? 

    CCS still supports TM4C1294NCPDT. GUI Composer v1 design mode is not supported for any device and it has been replaced by GCv2. 

    The runtime GCv1 re-distributable launcher has a webapps folder and we manually copy all CCSV5.4 GCv1.0 designer files and achieve a very professional looking GUI environment under portable CE or other desktop access points. Sorry to say the cloud version designer infantile looking widgets and lack of complex variable controls are mostly useless for real time mandated local controls of MCU peripherals, especially where high voltage is concerned. The cloud is a gee wiz gadget access point that is highly volatile to a number of environmental climate factors or even war, forcing TI customers into that funnel cloud is a bad idea. We view IOT for the ability to report status more than control highly complex systems where hackers could possibly intrude and cause mayhem in high voltage grid attached systems.

    Our documentation for GCv2 is still substandard and it will be improved over next few weeks. It is not obvious but GCv2 online tool is used as designer (think of it as an editor). It can be tested online using an agent that runs locally on the PC to provide JTAG access. Once a design is complete it can be exported and then combined with GCv2 Desktop runtime just like GCv1. If an end user installs GCv2 desktop runtime and adds the app that has been created with GCv2 online designer, then there is no difference between GCv1 and GCv2. There is no difference with how device is accessed through JTAG. The widget libraries and middleware are different, but once installed on desktop they do not interact with cloud. 

    Martin

  • 0 in reply to MartinS
    Guru 56033 points

    MartinS said:
    It is not obvious but GCv2 online tool is used as designer (think of it as an editor).

    That explains a lot better what/why all the fuss over CCSv7 in this thread. By accident discovered Palette is accessible via chevrons located at top right side of web page, I was stupidly only using the (+) button at the bottom to test a few widgets. 

    Another con is GCv2 fails to import our GCv1 project (*.zip) without generating an error. Also noticed absolute widget positioning is not available for dash board content pain and seems to only support flow mode. That might be why the import is failing since project uses absolute positioning of widgets. Perhaps the GCv1 digital meter/gauge widgets are not found in GCv2, looked all over the pallet and they are not there.

    Thanks Martin your latest explanation really clears up any confusion! 

  • 0 in reply to Genatco
    TI__Genius 15700 points
    My apologies for lack of documentation that does not cover this.

    Unfortunately, we do not support importing GCv1 projects into GCv2. Javascript libraries that are used are completely different.

    New project wizard has a few templates(first selection in the New Project Wizards) Dashboard has the flow layout and as you mentioned earlier is intended to provide a simpler way to get started and it is best suited for IoT type user interfaces. Application template uses absolute positioning and should have the widget pallette (the slide out window with more widget options) opened automatically.

    For C2000 JTAG access you would need to choose XDS/Target Monitor option in the wizard.

    Martin
  • 0 in reply to MartinS
    Guru 56033 points

    Just finished the GCv1 4 tab application GUI and now being told can not import or migrate it into GCv2 seems a future road block.

    GCv1/2 JTAG/ICDI method of data transfer is slow as beans anyway and someday (launcher) should be rewritten for UART, USB or EMAC peripheral interface as the primary transport. A target device of http transport might be the easiest way to make that happen for use with Divinci widgets by use of Chrome client calls at the desktop level.

  • 0 in reply to Genatco
    TI__Genius 15700 points

    Unfortunately, the the technology under the hood makes it very difficult to provide backwards compatibility for GCv1 apps in GCv2.

    In next few months we will be looking at different transport mechanisms for GCv2 including http and WIFI. GCv2 standalone desktop apps leverage NodeWebkit, which is a chromium browser. 

    Martin