• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 1194 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.

AWR1843 How to configure the Chirp setting

Pyounghwa Yoon
Prodigy 30 points
Other Parts Discussed in Thread: AWR1843

Hi, 

I'm using AWR1843 and Firmware Medium Range Radar(MRR) in Automotive Toolbox 3.2.0. 

I would like to know the method configure the chirp setting likes the figure below.

number of subframe is 1,

number of burst is 2, (burst1, burst2)

number of chirp profile is 4. (c1, c2, c3, c4)

But I don't know which parameter, in MRR DEMO, should be modified to operate the AWR1843 with 2 bursts.

And how to assign the 3rd, 4th chirp profile to 2nd burst.

im looking up the document "mmWave-Radar-Interface-Control".

Could I get any advice about chirp configure using multiple bursts?

Best regards,

Yoon

  • 0
    TI__Genius 15046 points

    Hi Yoon,

    Could you share the screenshot again? Drag and drop doesn't work on this forum, you would need to use the "Insert file" button to do so.

    In general, the ICD is the authoritative document on mmwavelink API offered by the frontend. You could also look at mmwavelink's doxygen documentation for a more user friendly, programmer oriented version of the documentation.

    You would want to look into how rlSetProfileConfig, rlSetChirpConfig and rlSetAdvFrameConfig are used in the MRR demo in the src/mss/mss_mrr_cli.c file to configure the demo. These functions use configuration read from the files  src/common/mrr_config_chirp_design_<config>.h. I would also suggest looking at these files along with src/common/cfg.c file to see how the MRR demo is configured.

    I will get back to you with specific details once I see the shared image.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Prodigy 30 points

    Hi Aayush,

    Thanks for your advice firstly.

    I attach the figure as below. it is MIMO.

    And read the "src/common/cfg.c" file and modifed some value in "rlAdvFrameCfg" such as below.

    """""""""""""""rlAdvFrameCfg""""""""""""""""""""

    subFrameCfg.forceProfileIdx = 0

    subFrameCfg.numLoops = 64

    subFrameCfg.numOfBurst = 2

    subFrameCfg.numOfBurstLoops = 1

    subFrameCfg.chirpStartIdxOffset = 128

    subFrameCfg.numOfChirps = 2

    subFrameCfg.chirpStartIdx = 0

    subFrameCfg.subFramePeriodicity = SUBFRAME_MRR_PERIODICITY_VAL

    subFrameCfg.burstPeriodicity = BURST_PERIODICITY

    subframeDataCfg.numAdcSamples = number of adc sample * 2

    subframeDataCfg.totalChirps = 256

    subframeDataCfg.numChirpsInDataPacket = 1

    """"""""""""""""""""""""""""""""""""""""""""""""""

    Is it correct value to operate the chirp signal as the represented figure below?

    And another question is should I give some value to "loopBackCfg" in "rlAdvFrameSeqCfg"?

     

    I would like to ask your advice about above question.

     

    Best regards,

    Yoon.

  • 0 in reply to Pyounghwa Yoon
    TI__Genius 15046 points

    Hi Yoon,

    I can't say for sure without experimenting with this on my own, but it seems to be on the right track. The subFrameCfg.chirpStartIdxOffset = 128 would ensure that the second burst starts from chirp index 128. For the screenshot you provided, the total number of chirps defined are 4 at indices 0, 1, 128, 129, so it should achieve the desired outcome.

    I would suggest having a look at the DFP user guide in ti/mmwave_dfp_<ver>/docs folder, specifically the mmWave Sensor Advanced Features section for details on advance frame configuration.

    The loopback configurations are for RF loopback features, they are not required for normal operation. You can refer to the DFP user guide for more details on loopback configurations as well. You can see the loopback architecture in figure 2-1 in this app note.

    Regards,

    Aayush