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.

CCS/AWR1642: Profile, Chirp, Frame configuration

Part Number: AWR1642
Other Parts Discussed in Thread: MMWAVE-DFP

Tool/software: Code Composer Studio

Hi,

I'm running the lab0002_short_range_radar in automotive toolbox on AWR1642BOOST.
From the line 240 in the mms_srr_cli.c file, there are three steps:
Profile configuration
Chirp configuration
Frame configuration

Can anyone tell me the relationship between those three?
I'm a little confused.......

Best Regards,
-Kevin

  • Hello Kevin,

    The profile, chirp and the frame configurations are APIs/Commands to configure the Radar front end .

    Profile: Profile config API sets the FMCW radar chirp properties like FMCW slope, chirp duration, TX power etc. The API allows multiple profiles to be set together by passing the array of profile data along with count of profiles

    Chirp: Chirp config API sets the chirp to chirp variations on top of the chirp profile defined in ProfileConfig . This function indicates the profile to be used by each chirp in frame in addition to fine tuning parameters to the FMCW start frequency and idle time for each chirp

    Frame : Frame config API defines the frame properties like the sequence of chirps to be transmitted, number of frames to be transmitted, periodicity of the frame and the trigger method

    I recommend you to look at the Radar Interface control document that is available in the MMWAVE-DFP ($mmwave-dfp-install\docs\AWR1xx_Radar_Interface_Control.pdf).

    Refer to the profile, chirp and frame configuration APIs and commands in this document for better understanding.

    Thanks,
    -Raghu
  • Hi Raghu,

    Thanks for suggesting the document which I was looking for.
    I will read it and hope I can understand much better.

    Best Regards,
    -Kevin