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: MRR_demo : How to activate the CLI commands

Part Number: AWR1843

Tool/software:

CLI Configuration

Most of the mmWave demos provided by our team on TI Resource Explorer support a CLI configuration from the PC host:

  • The RF and demo configuration parameters are usually provided in a file called profile.cfg
  • The content of this file is sent to the mmWave sensor target through the UART
  • The application running on the target uses this information to configure the RF front end and the demo.

The MRR demo also supports a CLI, however the main difference with the other demos is that the RF configuration is not sent through the UART but hard coded in the application that runs on the target.

The MRR demo supports only two commands which are sent by the Matlab GUI through UART to start the demo.

The MRR demo can be started using these commands using Tera Term for example.

This is the snippet i found in MRR demo documentation. I would like to know how to activate the CLI commands in this{MRR) demo. 

Thanks,

Rehman

  • Hello Rehman,

    The reason why it is hard coded in the MRR demo is that, in a real use case scenario, the chirp parameters are not dynamically updated and most customers prefer to hardcode the value.
    For proper implementation of this youc an refer the example in the SDK 3.6:
    mmwave_sdk_03_06_00_00-LTS\packages\ti\demo\xwr18xx\mmw
    in this demo they use the CLI funcitonality and you can refer these functions:
    mmwave_sdk_03_06_00_00-LTS\packages\ti\utils\cli

    These are all the resources we have, you can use it as needed.

    Regards,
    Saswat Kumar

  • OK....Thanks, will go through it