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: TLV encoding data formats

Part Number: AWR1843
Other Parts Discussed in Thread: AWR2243,

Hi Team,

Can you please help us with this inquiry from our customer?

I looking for help with format of TLV encoding Data Formats. I work with AWR1843 and AWR2243. I found some document in documentation. If it is possible I can attach to you the document. I decode the receive data by documentation, however the data are different as the described in the document.

TLV_uart_format_tm.pdf

I want only add information. The data are received from AWR1843 and i want check the document if is all correct. Because on the position of TLV Header type. I do not detect value, which describe the TLV type. Not even around the TLV Header, 'type' position.

I checked the appended files and documents as:  mmWave SDK User Guide located on C:\ti\mmwave_sdk_03_06_00_00-LTS\docs  &  C:/ti/mmwave_sdk_03_06_00_00-LTS/docs/mmwave_sdk_module_documentation.html
But the information are primarily about programing of radar kit. But, I need something about detailed description of output TLV data.

In my case, AWR1843 acts as a black box that communicates with my C++ code.
Out-of-the-box firmware was flashed to the AWR1843.
I correctly created sending configuration commands in my code.
I am receiving TLV data after configuring the AWR1843 with cfg commands. So my question is, could you point me in the direction of documentation on TLV data? I'm referring to the structure of TLV data.
Because I need to sort this data by functionality (such as position, SNR, and so on) for future use.

The second question is: Is the output structure of TLV data dependent on flashed firmware? Or dependent on some configuration command for the radar kit?
Regards,
Danilo
  • Hi,

    Here is some information that will be helpful to you

    1) The TLV format is specific to the demo running on the board.

    2) The data that is sent out by demo is configurable through the profile configuration file

    The profile configuration files are provided in

    C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\demo\xwr18xx\mmw\profiles

    In the profile configuration file there is a command "guiMonitor -1 1 1 1 0 0 1" that configures the data that is sent out by demo.

    The meaning of this command is provided in the mmWave SDK User Guide "C:\ti\mmwave_sdk_03_06_00_00-LTS\docs\mmwave_sdk_user_guide.pdf", search for "guimonitor" in Section "Configuration File Format"

    The format of the TLV is described in the SDK documentation

    Section "Output Information Sent to Host"

    C:/ti/mmwave_sdk_03_06_00_00-LTS/packages/ti/demo/xwr18xx/mmw/docs/doxygen/html/index.html

    Please note that the GUI Visualizer allows to record this data and perl scripts are provided to read the recorded data in

    C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\demo\parser_scripts\mmw_demo_example_script.py

    Thank you

    Cesar