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.

TMS320F28035: GUI Composer

Part Number: TMS320F28035

Hello,


I did upload my project to GUI composer from my local Directory and changed the target communication settings to XDS in project properties. On system Connect, I am getting the message 'Connected to Target' and 'Hardware Connected' on the console. After this when I try to save it, it just goes into this infinite loop where it displays 'working' and then I have to refresh the page after a long wait in order to kill the process. 

Please suggest me an approach here. 

Thanks,

Nikit Shah

  • Nikit Shah said:
    After this when I try to save it, it just goes into this infinite loop where it displays 'working' and then I have to refresh the page after a long wait in order to kill the process. 

    Is this behavior consistently reproducible? Could you try it on a couple of different projects to see if it is a consistent or isolated behavior?
    I just tried adding XDS communication to a couple of GUI Composer projects and did not have this issue when saving the project.

  • Yes, I tried running Toggle LED example code for F28035 on my Local CCS first to get .out file. Then I tried to save my project properties to XDS on GUI composer and got stuck with the same problem as before.

  • Can you detail your procedure step-by-step so we can try to reproduce this?

    The CCS application project and GUI Composer project are separate independent projects. Do you mean that you created a GUI Composer project/application to communicate with your Toggle LED CCS application, and then added XDS communication to the GUI Composer project?

    I assume you are using GUI Composer v2 on the Cloud, is that correct? https://dev.ti.com/gc/

  • It might also help if you could attach your GUI Composer project here.
  • So, I built the Toggle LED code on my CCS application. On GUI Composer, I imported the same project and added XDS communication (which I am not able to save). The reason for building it on the local CCS is to have the symbol file for GUI composer. Do I need to debug my code in CCS cloud in order to run GUI composer? I wanted to go with GUI composer 1 as that is a desktop version but I did not find any user guide for that. I am using GUI Composer v2.
  • Nikit Shah said:
    So, I built the Toggle LED code on my CCS application. On GUI Composer, I imported the same project and added XDS communication (which I am not able to save).

    The CCS application is not intended to be imported into GUI Composer. As I mentioned earlier, the CCS project and GUI Composer project are separate, independent projects created in different environments. 

    A GUI Composer project allows you to create a GUI dashboard comprising of widgets, then you can bind those widgets to global variables in your code so you can visualize the state/value of variables in the GUI dashboard. For this, you would first need to create a new GUI Composer project. In this project, you set up various properties like the communication model (how the GUI will communicate with the target application, eg. XDS), the location of CCS project executable to be downloaded to target (that GUI Composer will be communicating with) etc. 

    There is a tutorial written for F28379D device that walks through these steps, which you can use as a guideline (link here).

    In addition, the Users Guide and Getting Started Guide under the GUI Composer section of Resource Explorer are also great resources for general information on GUI Composer. 

    Hope this helps!

  • Thank you for clearing my Questions Aarti.