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.

AWR2243: AWR2243 Chirp/Frame Configuration

Part Number: AWR2243

Can someone help clarify some of the parameters related to AWR_PROFILE_CONF_SET_SB and AWR_FRAME_CONF_SET_SB. I am referring to the mmWave-Radar-Interface-Control.pdf.

What is the difference between the CHIRP_START_INDX/CHIRP_STOP_INDX for the PROFILE and FRAME config settings?

The NUM_LOOPS in the FRAME_CONF specifies the number of times that the START/END  INDX are repeated and the NUM_FRAMES specifies the number of times the loop count with start/stop indices are repeated?

Thanks,

Gabriel

  • Hello Gabriel,

    Thanks for reaching out.

    Let me clarify things for you here.

    What is the difference between the CHIRP_START_INDX/CHIRP_STOP_INDX for the PROFILE and FRAME config settings?

    Chirp Start and stop index in frame config lists out all the chirps used in a frame whereas, Chirp start and stop index in Chirp config defines the chirps used for a particular profile. 

    Say for example, you want 10 chirps in a frame with type/profile A and 10 chirps with type B. In this case, following will be your chirp and frame config : 

    Chirp Config -- 

    Profile A: Chirp Start Index = 0, chirp End Index = 9

    Profile B: Chirp Start Index = 10, chirp End Index = 19

    Frame Config -- 

    Chirp Start Index = 0, Chirp End Index = 19

    The NUM_LOOPS in the FRAME_CONF specifies the number of times that the START/END  INDX are repeated and the NUM_FRAMES specifies the number of times the loop count with start/stop indices are repeated?

    Coming to your second question,

    Num_Loops defines the number of cycles for Chirp_Start Index and Chirp End Index in the frame config. If we continue on the previous example : 

    - Keeping num_loops as 1 : One Frame structure = A,B

    - Keeping Num_Loops as 2 : One Frame structure = A, B, A, B

    The above only defines the structure for one frame, to increase the number of similar frames, one has to program the NUM_FRAMES parameter.

    So say if you want 2 frames with chirp types A and B (10 chirps in each category), with num_loops as 2, Frame structure = 1st frame [A,B,A,B] , 2nd Frame [A,B,A,B]

    Hope this clarifies things for you.

    Regards,

    Ishita

  • Thank you for the detailed explanation... To add for further clarification...

    There 512 chirp profile indexes... Each of these chirp profiles or range of chirp profiles can be configured with its own slope and start and end time, etc...

    As you mentioned, I could then build up a Frame by using Start and Stop chirp indexes with the number of times I would like to Loop the sequence.

    Can you confirm my understanding? All of this would fall under one Profile ID? When is it better to increase the number of Loops and decrease the Frame count as opposed to just increasing the Frame count?

    Gabriel

  • Hello Gabriel,

    Yes, there can be 512 unique chirps each associated to one of the four profiles. Profiles are basically associated with chirps and not frames. 

    As you mentioned, I could then build up a Frame by using Start and Stop chirp indexes with the number of times I would like to Loop the sequence.

    Yes, that is correct.

    When is it better to increase the number of Loops and decrease the Frame count as opposed to just increasing the Frame count?

    That entirely depends on your usecase and chirp/frame structure. 

    To have more insights on chirps and frames, maybe you could refer to our application note on this : Programming Chirp Parameters in TI Radar Devices (Rev. A)

    Hope this helps. Let us know if you need more clarifications.

    Regards,

    Ishita