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.

AWR1642BOOST: Profiling parameter of Demo Visualizer: InterChirpProcessingMargin

Part Number: AWR1642BOOST

Hi, TI team,

I'm figuring out the measured timing from "Profiling" parameters. According to the code in mmwave SDK 3.4, the InterChirpProcessingMargin was computed in each chirp event. (During DPC_ObjectDetection_chirpEvent and DPC_ObjectDetection_execute were called for each single chirp for range processing, thus get timing value then.)

So, for overall timing value of Range process, it become "InterChirpProcessingMargin * 2 (since its complex signal) * numChirpsPerChirpEvent * numChirpsPerFrame". Is this right?

Thank you.

Shihyu.