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

IWRL6432BOOST: TLVs packet parsing

Eddy Lai
Prodigy 230 points
Part Number: IWRL6432BOOST

Im trying to parse the CLI output from Motion and Presence Detection example withTracking config (TrackingClassification_MidBw.cfg),
can understand the TLV type: 306 (MMWDEMO_OUTPUT_EXT_MSG_STATS) and 
308 (MMWDEMO_OUTPUT_EXT_MSG_TARGET_LIST),  but what's for the 0x1F09 TLV type?
(packet between 306 and 308 below)
=========================================================================

0201040306050807
01000405

C0000000
32640A00
D7010000
00000000
00000000
02000000
FFFFFFFF

32010000 TLV.Type 0x0132=306 :EXT_MSG_STATS
18000000 TLV.Len 0x0018=24
------------------------------------------------
19090000EC0700002E110000167400002DD50000D18D0000

901F0000 ???
A0110000 ???
----------------------------------------------------------------------------------------------------
760D000089090000B1080000C6080000710700004C070000750C0000C30F0000FD0A0000710A0000B009000075060000D305
0000E5050000E90500007406000040060000130700009C070000FA06000052060000300600004D0600005306000060050000
110600000B0700002907000097050000E805000006060000350600005E060000970600002C060000D5050000E9050000E505
0000D3050000FD050000260500006C050000D9050000650500009B050000E90500008F050000F2050000A10500003B060000
6705000048050000CE040000C4040000F00300005A040000

34010000 TLV.Type 0x0134=308 : EXT_MSG_TARGET_LIST
70000000 TLV.Len 0x0070=112
----------------------------------------------------------------------------------------------------
7D7700002C830000C00100009602570029002A002C002600010000000000000001000000B65C3A00000000000100280000F0
1F00010000000100000000000000000000003333F33F0000C04000002041CDCCCC3D040000000000003F0000A04100004040
000000400000004000000040350100000100000002

  • 0
    TI__Genius 16601 points

    Hello, 

    Can you let me know what version of the SDK you are using? Also have you modified the example configuration file at all?

    There shouldn't be any TLV with that type. Is this data present for every frame?

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 230 points

    MMWAVE_L_SDK_05_04_00_01
    use TrackingClassification_MidBw.cfg 
    and enable "quick eval" 

  • 0 in reply to Eddy Lai
    TI__Genius 16601 points

    Thank you. 

    If you have enabled the quick eval option, the radar will run without the need to send a configuration file. So when you say you are using TrackingClassification_MidBw.cfg, do you mean you have copied the commands from that cfg file into the structure which is saved in the demo code and used with "quick eval"? Or is it that you are using quick eval and still sending the cfg file over uart?

    Also, can you please let me know if this unknown data is always present with every frame or it occurs occasionally with most frames containing only the expected data?

    Best Regards,

    Josh 

  • 0 in reply to Josh Dye
    Prodigy 230 points

    Yes, I have copied the commands from that cfg file into the structure which is saved in the demo code and used with "quick eval"
    and this unknown data always present with every frame

  • +1 in reply to Eddy Lai
    TI__Genius 16601 points

    Thanks for the response. This is not an issue that we have seen before and I'm still not quite sure on the cause. I noticed in your first post that the frame header indicates there should be 2 TLVs and that the total packet size is 192 Bytes. This seems to match the 2 known TLVs that you see in the data.

    I have not been able to replicate the issue on my end so I suspect it could be 1 of 2 things:

    1. It's possible that there is a problem with the way that you are capturing/parsing the output UART data. Please double check the methods you are using.

    2. Have you modified the demo code and added any extra mmw_UartWrite calls? 

    Regards,

    Josh