Hello!
Is it possible to use GUI as a standalone application?
I tried it with CCS5.3 but it doesn't work.
Thanks, best regards
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.
Yes, having the GUI work as a stand alone app is supposed to work. I assume you have read the section on 'Export Application' in GUI Composer wiki" (http://processors.wiki.ti.com/index.php/Category:GUI_Composer) . Can you detail a bit more where things went wrong?
Raj
Did you unzip you apps .zip into webapps folder of GUI Composer RUntime that you need to install separately? Information in this topic http://processors.wiki.ti.com/index.php/Category:Gui_Composer#Export_Application:
GUI Composer Beta 3 did not have a separate GC Runtime install package. It is now available from the wiki. Previous beta releases of GUi Composer had standalone runtime availalbe.
Martin
Salvatorre,
Please clarify what you are requesting assistance for. You replied to a GUI COMPOSER thread, but you are showing a Motor Control GUI, not of TI origin, so I am unclear as to what you are requesting. We will be glad to assist with some additional direction from you - thanks!
~Leonard~
Hello Salvatore,
GUI Composer v1 should allow you to get UART GUI working, below is a link to a wiki page that goes step by step how to create the GUI with UART.

You may also consider trying GUI Composer v2, designer tool is available onliine at dev.ti.com/gc
Getting started guide is available at

The tutorial about uart - monitor is available here

It is for a different device and it is using Energia framework to include a library that implements the monitor code(this is the piece that you would need to embed in your application). However, the protocol is the same as for GUI Composer v1, thus target code example from GUI Composer v1 would work with GCv2 design and runtime tools.
One last clarification, in GCv1 you are working within CCS desktop and when you click on preview, then GC infrastructure will automatically use currently selected CPU in CCS Debug View as the target for device communication. This should be shown in first link above. Only during export you make a choice as to what the communication target is. The picture that you included in your post is visible only when an application is run from GC Runtime and only for JTAG type target communication options.
GCv2 works a bit differently and some of those choices are made at the beginning during new project creation.
martin