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

Original question:

AWR2243: How to calculate mmwl_TDA_height[..] for subframes with different values for numLoops, numOfChirps, numOfBurst,...

AWR2243: mmwl_TDA_framePeriodicity computation can result in truncation of 1 millisecond, is this a problem?

Eddie Arrant
Prodigy 130 points
Part Number: AWR2243

reference example code:

C:\ti\mmwave_dfp_02_02_03_01\ti\example\mmWaveLink_Cascade_Example

In the MMWL_advFrameConfig() function, the mmwl_TDA_framePeriodicity is computed and later used in MMWL_ArmingTDA() 

The resolution for mmwl_TDA_framePeriodicity is 1-LSB = 1 ms

The resolution for the Advanced Frame Parameter, subFramePeriodicity, is 1-LSB = 5 ns  

If "AdvframeCfgArgs.frameSeq.subFrameCfg[i].subFramePeriodicity" is set to 4.999995 mSec  (999999 LSBs)

and after the conversion to milliseconds, "mmwl_TDA_framePeriodicity" value is 4 LSBs, or 4 ms.

This computation results in mmwl_TDA_framePeriodicity being set to a value 1 ms too short.

Will the mmwl_TDA_framePeriodicity value set by MMWL_ArmingTDA() to radar work as intended?

Regards

Eddie

  • 0
    TI__Guru 69960 points

    Hi Eddie,

    Looks like application does take max value of periodicity and parameters to calculate from all the subframes.

    This is the current implementation with PC based application and with TDA cascade application.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 130 points

    The above looks like a cut-and-paste from another question:

    Should we round up the (mmwl_TDA_framePeriodicity) value to account for truncation after the 5nS resolution parameter (subFramePeriodicity) is converted to mmwl_TDA_framePeriodicity, which has a resolution of only 1 millisecond?

    Regards
    Eddie


  • +1 in reply to Eddie Arrant
    TI__Guru 69960 points

    above two parameters are meant for two devices, mmwl_TDA_framePeriodicity for TDA2x to prepare and capture the ADC data from AWR device over CSI2 interface and pass it over ethernet to PC.

    and subFramePeriodicity is meant for AWR device for rf-front end configuration.

    mmwl_TDA_framePeriodicity parameter has taken into maximum possible duration so it doesn't hit any capture issue within TDA. However if you are trying to bigger value to subFramePriodicity then optionally you can minimize TDA_frameperiodicity. But this particular scenario is not tested at our end.

    You can edit and try as you need.

    Regards,

    Jitendra