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.

AWR1843BOOST: Reducing the interframe periodicity and amount of chirp loops in config file without the chip to stall or fail

Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843

Hello

I'm trying to use the subframe configuration  in order to get different chirps from different Tx each frame. It seems ,as explained in the sdk user guide, that the minimum number of "chirps per subframe" (if only one chirp configuration is used) or loops is 4, configured in "subFrameCfg". However, the lower I can get is 12 loops which in my case this means 12 chirps every subframe. Is there a way to reduce it? perhaps not to 1 but 4?

I'm also aware of the rule that subframe/frame periodicity should be equal to the burst periodicity (at least for the demo)  and this should also be greater than the number of loops per duration of chirp, since I only have twelve chirps per loop this seems to not be an issue and it can be changed up 0,5 ms as stated in doxygen. However, the lower time I can get in periodicity of frame is 30 ms. Is this a demo restriction or can it be lowered via fine tuning of chirp parameter? if sow how should I follow?

Best Regards

  • Hi,

    More information about AWR1843 Advanced Frame configuration can be found in following documents

    Programming Chirp Parameters in TI Radar Devices

    https://www.ti.com/lit/an/swra553a/swra553a.pdf

    Radar Interface Control Document

    C:\ti\mmwave_dfp_01_02_06_03\docs\mmWave-Radar-Interface-Control.pdf

    My understanding is that you are using the mmWave SDK demo.

    You will not be able to lower the frame duration because there is time needed to process the data.

    What is the error you get if you decrease the number of chirps?

    Thank you
    Cesar