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.

AWR1642BOOST-ODS: Process of sending configuration CLI commands over UART

Part Number: AWR1642BOOST-ODS

Hello,

I currently am using a MATLAB implementation that writes the CLI configuration commands (sensorStop, flushCfg, etc.) to the radar User/Application serial port and it seems to work fine with most settings. However, I want to improve the robustness of my implementation to mimic that of mmWave Studio or the Demo Visualizer.

In order to do this, I am trying to understand the hand-off procedure between the software and the hardware. Particularly, does the device send back any feedback validating the parameters you have set? If not, is it possible to find the hardware limits for every parameter? I have noticed some combinations that seem theoretically possible, and I have used with mmWave Studio in the same setup, result in no data being sent from the radar.

I have read the following posts as well to gain further understanding and would like some guidance from here. 

https://e2e.ti.com/support/sensors/f/sensors-forum/712967/awr1642-starting-up-the-device-without-sending-config-from-the-visualizer

https://e2e.ti.com/support/sensors/f/sensors-forum/625663/starterware-awr1642-starting-up-the-device-without-sending-config-from-the-visualizer

Thanks,

Josiah W. Smith

  • Hi Josiah,

    When you use mmw demo which takes CLI commands over UART, so for each of the commands it returns 'Done' as confirmation of successful execution of that CMD. So in your matlab implementation, you need to readback the data from the same UART-COM-port for 'Done' string, only then proceed for next command.

    You can verify this first using some serial terminal tool (TeraTerm) to connect on the same COM port and send CLI command, which should print 'Done' string for each of the command.

    For more detail on device implementation you can refer

    C:\ti\mmwave_sdk_03_05_00_01\packages\ti\utils\cli\src\ cli.c and cli_mmwave.c files

    C:\ti\mmwave_sdk_03_05_00_01\packages\ti\demo\xwr16xx\mmw\mss\mmw_cli.c

    ANd for ODS:   mmwave_automotive_toolbox_3_0_0\labs\lab0004_obstacle_detection\src\mss\cli.c

    Regards,

    Jitendra

  • Thank you. This is very helpful.

    Best,

    Josiah W. Smith