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.

IWR6843ISK: How can I get the interframe processing time with vital sign demo via CCS debug

Part Number: IWR6843ISK

Hi,

I woulk like to increase the sampling frequency from 20Hz to 100Hz by optimizing the configurattion parameters and checking the interframe processing time from CCS debug.

There is any variables related direclty to the interframe processing time or It must be extracted from the calculation of differents variables?

Could you please support me to get the right way.

Thanks in advance

Kind regards

  • Hello, 

    Interframe processing time is stored within MmwDemo_output_message_stats. Struct definition is in <MMWAVE_SDK3_INSTALL_DIR>/packages/ti/demo/xwr68xx/mmw/include/mmw_output.h

    Documentation can be found at <MMWAVE_SDK3_INSTALL_DIR>/packages/ti/demo/xwr68xx/mmw/docs/doxygen/html/struct_mmw_demo__output__message__stats__t.html

    Best Regards,

    Josh

  • Hi,

    Thanks for your feedback. I cannot get this variable because I'm excecuting the EVM with ICBOOST in ccs debug mode with vital sign FW.

    Is there any way to read the Interframe processing time from vital sign source code? If not thanks to clarify me the right way

    Thanks in advance

  • Hello, 

    The issue is not clear to me. 

    Is the issue that you can not find this variable in the demo code or you can find it but are not able to view the value using CCS debug functionality?

    Also can you please let me know the exact Radar Toolbox version that the demo code is from?

    Best Regards,

    Josh

  • Hi,

    Sorry for this delay.

    I'm debugging in CCS the IWR6843ISK +IC BOOST with the vital sign FW without tracking and sdk3.6.

    By setting the frame period to 10ms instead 50ms, the frame processing time is around 290ms between two successive frames.

    My question is: It's is possible to decrease this processing time? How can I do it?

    Thanks in advance

    Kind regards

  • Hello, 

    A couple of things to note:

    1. I believe the demo that you are referring to was never updated to support SDK 3.6. Please check the software requirements in the demo user guide and ensure the correct SDK version is installed. 
    2. Processing time of 290ms does not make sense to me as the processing time should be less than the frame period. How are you measuring the processing time?
    3. As this demo has been deprecated in favor of the new vital signs demo (Vital Signs with People Tracking), we can not provide this level of support in terms of suggesting optimizations to the demo.

    Best Regards,

    Josh