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.

AWR1843: GUI tool: MRRVisualizer in Automotive lab demo lab0007_medium_range_radar doesn't work with AWR1843 when connect via XDS110 DEBUG PROBE

Expert 1440 points
Part Number: AWR1843
Other Parts Discussed in Thread: TMDSEMU110-U,

We have a customised AWR1843 module. We connect it with an external XDS110 Debug Probe(TMDSEMU110-U). The COM ports are shown as below in device manager.

The test firmware is ti automotive lab demo lab007_medium_range_rader. We want to check the detected objects in demo tool: MRRVisualizer.exe. We set 27 and 28 respectively in UART port options, but cannot see any detected objects.

Does MRRVisualizer.exe not support the XDS110 Debug Probe? Can you please check in your side?


  • Hi,

    MRR visualizer isn't particularly concerned with XDS. As long as you can see COM ports in the device manager, MRR GUI should also be able to read them. 

    Are you convinced that this lab is indeed running on the device? Have you tried debugging the lab with CCS debug beforehand to get the first level of confirmation?

    I ask this because I can think of two possibilities only: data is not being sent from the lab itself, or that data gets corrupted in transport and MRR can't detect it.

    To find out which of the two it is, after connecting the PC to the EVM flashed with MRR software, use PuTTY/Teraterm/any other software to read the UART at 921600 baud rate and verify that you can see some data come in.