• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 53 subscribers
  • Views 754 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: GUI Composer v2, comport handshaking.

Michael Koval27
Intellectual 990 points

Tool/software: Code Composer Studio

Hello, I jprogrammed my device  to send  0x55 ,0x55,0x55,0x55,0x55 and six's byte 0x01, or 0x02  and try  to connect to  Serial_tutorial_binary example  project from GUI COmposer gallery.   But it is not connected, though from source of custom codec it is clear, that it is enough.  I checked out in usual terminal and assured that device sends  this sequence.  What is the problem? May bt GUI app needs some handshaking, may be it is finding comport with another number?  I can not understand. Please, explain.  

  • 0
    TI__Genius 16220 points
    Hi Michael,
    What device are you using? It might have multiple COM Port and you need to select the COM Port in your app's menu.

    Patrick
  • 0 in reply to Patrick Chuong
    Intellectual 990 points
    I try to write my own GUI application to solar_hv_dc_ac 28034 CPU. How do you arrange menu for multiple COM PORTS?
  • 0 in reply to Michael Koval27
    TI__Genius 16220 points

    The number of com port options in the dialog is depended on the number of USB UART transport that you have in your application. Open the Project Properties dialog and add an additional USB UART transport in the Target communication setting page. When you preview your app, you should be able to select comport for each transport/model. See attach screen capture for the dialog.

  • 0 in reply to Patrick Chuong
    Intellectual 990 points

    So for any combination COMport/BaudRate I have to create its own transport?  And , when I create project it does not give me possibility to setup in advance nor comport, nor baudrate:  http://joxi.ru/D2P3lweIqBzgzm

  • 0 in reply to Michael Koval27
    TI__Genius 16220 points
    Yes, each comport/baudrate is mapped to a model/transport. You can bind your widget(s) to a model where data is transfer between the host application and your device.
  • 0 in reply to Patrick Chuong
    Intellectual 990 points
    It does not allow me to set up even one comport : http://joxi.ru/VrwbRkYI7jYeeA .
  • 0 in reply to Michael Koval27
    Intellectual 990 points

    It turned out, that even without this options in properties (comport and baudrate)  it is set up menu Serial Port in application automatically( if I add 'Option' widget). But why button OK is unavailable for choosing com port? How I have to satisfy her to be submitted? http://joxi.ru/bmo05lYh37vJa2

  • 0 in reply to Michael Koval27
    TI__Genius 16220 points
    In the project dialog, the comport/baudrate setting is used to connect to the device when you press the CONNECT button. This is used for check whether you can successfully make a connection from host to target device. The spinner progress is stuck, perhaps you have the preview open and the comport is in use. Try closing the preview tab.

    When you preview the application, you can than select the comport. GUI Composer should remember your comport selection when you preview.

    You are presented with two comport settings, one in the project properties and one in the application that you are developing. In the project setting, it is used to test your comport connect and perhaps see the data coming from the comport in the console tab. The comport needs to be select in the application independent of the selection in the project's properties dialog.
  • 0 in reply to Michael Koval27
    TI__Genius 16220 points
    did you add a model to the transport?
  • 0 in reply to Patrick Chuong
    Intellectual 990 points

    Hello, Patrick. Thank you for explanation, yes it turned out that settings of project of comport mislead and are not connected with settings of comport in app, which are automatically added when you add Option widget to project. But I discovered very strange situation: when my PC has only genuine COMPORTs ( not virtual USB-COMPORT), application finds them but does not allow to connect. When I plug in usb-com converter on FTDI chip, application allows button OK in choosing any comports ( genuine and virtual). When I unplug com-usb device - button OK becomes again forbidden. After this experiment I recieved access to comport communication ( through usb-com converter) and application works. Only JS log blames that it can not find /target/target.xml file - it is not exist in app, but hopefully it does not matter for communication. What the problem with genuine com-ports?