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.

AWR2944: dynamic chirp and phase shift reconfiguration

Part Number: AWR2944

Hi,

My customer is considering using the adv frame and dynamic reconfiguration. Below notes and time diagram confuse me a lot. Need your help clarify, look forward to your comments soon, appreciated.

 

  1. My understanding that dynamic chirp/PS config can be called at any time as the configuration is stored in SW RAM and not applied until DYN_CHIRP_ENABLE is called, how to understand “Note that the configuration should be received by the firmware 10 ms before the end of the current frame.” Does it mean that the update configuration need at least 10ms to take effect after DYN_CHIRP_ENABLE is issued?
  2. How to understand the “HW reconfiguration time is around 500 us”? why it is need to issue before end of the ongoing frame active window? Can it be issued during frame idle time?

 

// AWR_DYN_CHIRP_ENABLE_SB

*   @note 1: User needs to invoke this API within inter-frame idle time, not at boundary of frame

*            end. Since dynamic chirps are configured at run time, there is not error checks done

*            on the input data. If input data is out of range or invalid, device might misbehave.

*   @note 2: HW reconfiguration time is around 500 us. User has to ensure that

*            AWR_DYN_CHIRP_ENABLE_SB API is issued at least 500 us before the end of the ongoing

*            frame active window (start of the frame idle time) to apply configurations for next

*            frame onwards. \n

 

// AWR_DYN_PERCHIRP_PHASESHIFTER_CONF_SET_SB

*   This API can be used to dynamically change the per-chirp phase shifter configuration while

*   frames are on-going. The configuration will be stored in software and the new configuration

*   will be applied at the end of the on-going frame. Note that the configuration should be

*   received by the firmware 10 ms before the end of the current frame.

  • Hi, 

    Will check this with the team internally and get back to you with an update in a couple of days.

    Thanks,

    Pradipta.

  • Hi,

    If you issue the DYN_CHIRP_ENABLE API during the frame, then the changes will come into effect from the next frame. If you issue the API during the idle time of the frame, then the changes will come into effect one frame after and not in the following frame. So, depending on how you want the changes to take place you can issue the API as per your application requirement. Also, you will need to meet the 10 ms timing constraint for phase shift API if you want the changes to take place in the very next frame.

    Thanks,

    Pradipta.

  • Hi, Pradipta

    If you issue the DYN_CHIRP_ENABLE API during the frame, then the changes will come into effect from the next frame.

    1) in the above quote, do you mean during the chirping?

    2)Pls help confirm, If I want the dynamic changes take place in the very next frame, the right way is :

    ①Call AWR_ADV_DYN_PERCHIRP_PHASESHIFTER_CONF_SET_SB while the current frame is still chirping. 

    ②AWR_ADV_DYN_PERCHIRP_PHASESHIFTER_CONF_SET_SB should be issued 10 ms before end of current frame.

    ③if PROGRAM_MODE is 1, we need to issue AWR_DYN_CHIRP_ENABLE API 500 us before the end of current frame.

    ④the dynamic changes take place in the very next frame

  • Hi,

    Please find my comments below.

    1) in the above quote, do you mean during the chirping?

    Comment) Yes

    2)Pls help confirm, If I want the dynamic changes take place in the very next frame, the right way is :

    ①Call AWR_ADV_DYN_PERCHIRP_PHASESHIFTER_CONF_SET_SB while the current frame is still chirping. 

    ②AWR_ADV_DYN_PERCHIRP_PHASESHIFTER_CONF_SET_SB should be issued 10 ms before end of current frame.

    ③if PROGRAM_MODE is 1, we need to issue AWR_DYN_CHIRP_ENABLE API 500 us before the end of current frame.

    ④the dynamic changes take place in the very next frame

    Comment) Yes this will the correct way to have the changes take effect in next frame.

    Thanks,

    Pradipta.