• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 55 subscribers
  • Views 1196 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.

GuiComposer does not create default appConfig.ccxml

Donald Rich
Prodigy 100 points

When creating a simple Gui for the blinky example (similar to what is shown in the deployment video) for the Stellaris Launchpad I found that the exported code does not include the required appConfig.ccxml file. This causes the launch to fail with an error of:

Could not start server: DebugServer.1: No configuration was supplied

Copying the ccxml file from the build directory solves the problem but this requires an additional manual step that is not described on the GuiComposer DeployApp page.

  • 0
    TI__Genius 15580 points

    Hi Donald, 

    The lack of .ccxml file is intentional. .appsettings file (should be part of your exported application) contains the device/connection settings that you selected during project export. This would allow users to select a different emulator (i.e. connection) if they did not have the one that is selected by default. For Stellaris based devices this is probably not that important as most people would use ICDI emulator, but it would be useful for some other devices that CCS & GUI composer support.

    Unfortunately, there seems to be a bug with this feature and triggers the error that you ran into. The workaround that your figured out is the best way of getting past it. 

    Also, appInitScript.js is a script that a GUI Composer application uses to initiate a target connection. By default it contains this line:

    session.options.setBoolean("UseLegacyStopMode", true);

     which ensures greatest compatibility with various devices. However, this option makes target accesses intrusive, i.e. target will be temporarily halted, memory access made and then target restarted. Stellaris devices when used with ICDI can make non-intrusive accesses, thus you could simply delete this line and your application would not halt the processor when memory is read or written. 

    Martin

  • 0 in reply to MartinS
    Prodigy 20 points

    Hi MartinS,

    I am pretty much trying to do the same thing as Donald, namely creating a simple GUI for the blinking LED program (in order to be able to create a GUI for our bigger project eventually). However, even with previous tips I'm still not able to create a working executable file... I copied everything in the right directory, and tried copying the CCXML file from the example provided when downloading CUI composer runtime. Also disabling the line 

    session.options.setBoolean("UseLegacyStopMode", true);

    didn't work. I keep getting this error:

    What could possibly be the cause of this? And how can I fix it?



    Thanks,


    Pieter


  • 0 in reply to Pieter Heemeryck
    Guru 192875 points

    Hi Pieter,

    Were you able to resolve this error???Please check:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/306375.aspx

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 20 points

    Hi Gautam,

    Unfortunately no, sorry.

    Regards,

    Pieter

  • 0 in reply to Pieter Heemeryck
    TI__Genius 15580 points

    Hi Pieter, 

    Unfortunately, I missed your original question. We suggest that new threads be started rather than old threads re-used even though information might be relevant. 

    Getting back to your question:

    In you webapp you should have a launcher.exe that gets created when you export. That executable is a shell that invokes ..\..\eclipse\GuiComposer.exe -Dgc.webApp="LauncherdirectoryName". relative paths are used thus you need to place your app in appropriate place in directory structure of GUI Composer Runtime and you need to use launcher.exe. Another way would be to use GUIComposer.exe and pass in argument. LauncherDirectoryName needs to be the directory name for your app. e.g. GC Runtime includes one example app called "modem_m3",  thus the command line would be GUIComposer.exe -Dgc.webApp="modem_m3". This parameter allows multiple apps to be available in the same runtime. 

    Martin

  • 0 in reply to MartinS
    TI__Genius 15580 points

    Sorry, the actual command line would need to be 

    GuiComposer.exe --launcher.appendVmargs -Dgc.webApp="modem_m3" 


    Martin


  • 0 in reply to MartinS
    Guru 192875 points

    Will try this out tomorrow. Mann it's tough managing time between EST and IST! 

    Good night guys. 

    Regards, 

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 190 points

    Hi,

    GUI composer takes 15 min to start in CCS5.5 ?

  • 0 in reply to ali riza ictihadi
    TI__Genius 15580 points

    Normally no, however some people have run into slow startup issues. see if any suggestions in this thread work for 

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/312512/1088196.aspx#1088196

    Martin

  • 0 in reply to MartinS
    Prodigy 190 points

    Martin,

    That's OK. Thank you very much.

    Ali Riza