• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 319 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.

Original question:

CCS/TMS320F28027F: Interfacing GUI and TMS320F28027F

CCS/TMS320F28027F: Software stops execution when GUI is started

Thomas Hecht
Expert 1080 points

Part Number: TMS320F28027F
Other Parts Discussed in Thread: MOTORWARE,

Tool/software: Code Composer Studio

hi there

I've been working with the lab11a project from the instaSPIN motorware in combination with a GUI composer V2 generated interface. The project was debugged step by step; the GUI was opened from the CCS. The mainISR was extended by GPIO that toggles each time the mainISR is called. This signal was observed on a oszilloscop. So far everything worked as expected. In the next step, I created a new project in the CCS, all the necessary files from the motorware were linked into the project. The Project was compiled and debugged on the TMS320F28027F the mainISR GPIO was toggling as in the previous but when now start the GUI form CCS the GPIO Output stops toggling for a while and toggles than again (toggle stop toggle stop and so on) . As soon as the GUI is closed, the GPIO toggles continuously again. Is the GUI opened as standalone everything works as expected (the pin toggles continuously). Do I have to set something within the CCS so that the GUI works correctly? I Looks as there is a data exchange between the GUI and the CCS the stops the execution of the Software.

thanks for helping

best regards

Thomas

  • 0
    TI__Guru**** 173310 points

    Thomas Hecht said:
    The project was debugged step by step; the GUI was opened from the CCS. The mainISR was extended by GPIO that toggles each time the mainISR is called. This signal was observed on a oszilloscop. So far everything worked as expected.

    In this working scenario, was the program loaded to target by CCS each time prior to opening/visualizing with the GUI? Or was CCS connected to code that was already running on the target device? If it was the latter then it was likely set up to connect in real-time mode. My recommendation would be to ensure that the connection/download and GUI startup procedure is the same between the working/example setup and your custom project setup.