• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 3467 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

IWR6843: TLV Parser

Anthony Pesin
Intellectual 600 points
Part Number: IWR6843

Dear technical support,

I am trying to build a TLV parser to get the Point Clouds of my application, based on the "indoor_false_det_68xx_data_output_format.pdf" document + the file I have just recorded using "mmWave_Demo_Visualizer 3.0.0".

I am a little bit confused:

1 - It says that first 8 bytes are for Sync Pattern which is Ok: 02 01 04 03 06 05 08 07 in little endian order.

2 - Then it says 4 bytes for Version which is Ok: 08 00 00 03 in little endian order.

3 - Then it says 4 bytes for Platform and here I get lost: 40 03 00 00 do not correspond to Platform where bytes for Platform appear on the next 4 bytes: 43 68 0A 00.

--> So it seems there is a mismatch between this TLV file and the document.

Please could you advise?

I thank you in advance for your support.

Best regards.

Anthony Pesin

  • Former Member
    0 Former Member
    Hello,

    The UART description for the indoor false detection mitigation demo does not apply to the data recorded for the mmWave SDK demo (referred to commonly as OOB - out of box demo).

    The mmWave Demo Visualizer record function logs the UART byte stream exactly as received. Therefore, please refer to the section "Output information sent to host" of the doxygen of the demo for details on the UART stream (file:///C:/ti/mmwave_sdk_03_00_00_08/packages/ti/demo/xwr68xx/mmw/docs/doxygen/html/index.html)

    To reference your question though - the output for the SDK demo is the magic word, version, totalPacketLen, and then platform, and then the remaining data fields. This is why you see the discrepancy - further details can be found in the doxygen linked above.

    Amanda
  • 0 in reply to Former Member
    Intellectual 600 points

    Hello,

    Thanks for your quick reply. I found the structure of the UART output in the "mmw_output.h" of doxygen link.

    I have other questions:

    1 - There is no generic description of the TLV structure because it depends on the use case of the demo: is it correct ?

    2 - Can I have access to the source code of the mmWave_Demo_Visualizer GUI?

    3 - How can I have access to the Point Clouds in the People_Counting / Indoor False Detection demos? There is no button to record the data output in the GUI as done in the OOB.

    Thanks.

    Anthony.

  • 0 in reply to Former Member
    Intellectual 600 points

    Hello,

    Now I am able to parse the output message header. Please could you help me now in parsing the message content?

    I checked in the doxygen linked and it is not clear for me. Giving an example on the data provided above would help a lot.

    Thanks in advance for your support.

    Best regards.

    Anthony

  • Former Member
    0 Former Member in reply to Anthony Pesin
    Hello Anthony,

    1) Correct

    2) Please see this post for accessing the visuzlizer source code. This will also provide you the reference for parsing the output message e2e.ti.com/.../2781558

    3) The people counting and false detection demos automatically log processed data as fhist files that can be viewed with Matlab.

    Amanda