• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 206 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.

AWR2944EVM: UART baud rate for HECR demo

Vikas
Prodigy 85 points
Part Number: AWR2944EVM

Tool/software:

Hi

We're trying to customize the HECR demo for our application. As a first step, we need to get the processed data on a serial terminal.

-Since CLI_BYPASS is defined, the sensor should start without any configuration or sensor start being sent through GUI or CLI port?

-We're only seeing garbage on a serial terminal connected to data port with baud rate set to 3125000

- How to I modify the baud rate? I tried modifying it in ti_drivers_open_close.c from 3125000 to 921600 in mssgenerated folder, but it gets rewritten during the ccs build

  • 0
    Prodigy 85 points

    Found the answer to point 3 from another thread. However, after building with 921600 baudrate I still see garbage coming out on the serial terminal. I know that the baud rate is being set correctly in the program since when I connect to the GUI it displays results as expected.

  • +1
    TI__Genius 14840 points

    Hi Vikas,

    Vikas said:
    Since CLI_BYPASS is defined, the sensor should start without any configuration or sensor start being sent through GUI or CLI port?

    As the CLI is bypassed, it's not required to send any configuration. The sensor should start without waiting for configuration to be sent.

    Vikas said:
    We're only seeing garbage on a serial terminal connected to data port with baud rate set to 3125000

    I suggest you taking a log of the object data that is received over UART. You can use any hex editor to analyze the data. Refer to mmwave_mcuplus_sdk_<ver>/mmwave_mcuplus_sdk_<ver>/ti/demo/awr294x/mmw/docs/doxygen/html/index.html to understand the output packet structure.

    Regards,

    Samhitha