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.

XDS110 debugger

Other Parts Discussed in Thread: AWR1843

The idea is to use our Custom 1843 board to work with VitalSignsRadar_demo.exe PC application. The Custom board is nothing but a custom layout with exact schematic. I have changed code, compiled and loaded onto the Custom board and verified to some effect it works (i.e. CLI configuration using PC application, start/stop data on data port etc).

When working with the AWRxxxxBOOST eval board the PC application communicates with the XDS110 debugger populated as a part of the EVAL, instead, I am using a XDS110 debugger. I have the AUX.FUNCTIONS Txd and Rxd connected to the AWR1843 Custom for CLI and have verified that it works correctly.

To get data from the Custom board, I have the Tx data wired to the EXPANSION port Pin 17 of the XDS110 debugger. I have verified data using scope, however, it does not make it to the PC application.

To verify if this scheme works correctly:

I programmed the AWR1843 with TI provided demo .bin and run Visualizer app on PC, In this PC app, I could change the Data port configuration to use a secondary FTDI port/cable for receiving data and it worked correctly. However, the Vital Signs Demo does not allow this feature, so I have to get the Data port/PC4 on external debugger TM4C going.

Kindly advise.

  • Hello Shyam,

    We have not used the XDS110 debugger but if you are able to use the FTDI cable with the demo.bin then you should be able to use the same with the Vital signs demo. In the Vital signs demo you can select the Data and User COM ports. In the Data UART port you need to select the COM port number that corresponds to the FTDI cable.

    Regards,

    Vivek

  • Hi Vivek,

    Maybe I am missing something, could you please try the VitalSigns Demo PC application (Windows) and see if it detects any other port than the debugger? It doesn't do that for me. All you need is the debugger and an FTDI cable, also the Vital Signs demo app. Could you provide step by step instructions?

    Although academic, given that I have traced the Expansion header to the Pin 25 on the TM4C1294, made sure that it has the same firmware as the eval board, would want to understand why I cannot get he data port going, Is it not supported on the XDS110 debugger? Is it mentioned in any errata ?

    Thanks,

    Shyam

  • In the below window you can select the COM port number (see the region marked using red box). The FTDI cable would show up as a COM port in the windows device manager, you need to enter that COM port number in the GUI.

    Regards,
    Vivek 

     Hello Shyam,

  • Hi Vivek,

    I Have you tried this?  Did it work for you? It doesn't for me. Any changes I make to the Data COM port don't reflect in the background cmd window and the data does not get through as it does in the mmWaveDemo.

    Thanks,

    Shyam

  • Hi,

    We have to check with the developer of the Vital Signs GUi

    Will get back to you tomorrow

    thank you

    Cesar

  • Sorry for the late reply

    Can you please try the following:

    1) When the GUI opens disable "Auto-Detect COM Ports"

    2) Fill in COM Port information

    3) Select "Start"

    thank you

    Cesar