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.

AWR2243: [Bug] chirpStart in advance frame configuration

Part Number: AWR2243

Hi, we found phenomenon that we did not understand the advanced frame configuration operation.

We think this is a bug, and we'll explain why.

1) First bug. 

In manual, chirpStartIdx and chirpStartIdxOffset are independant variables.

But in below example code, chirpStartIdx is equal to chirpStartIdxOffset.

--------------------------------------------------------------------------------------------------------------------------------

File : C:\ti\mmwave_dfp_02_02_03_01\ti\example\mmWaveLink_Cascade_Example\mmw_config

Function : MMWL_readAdvFrameConfig(rlAdvFrameCfg_t *rlAdvFrameCfgArgs)

--------------------------------------------------------------------------------------------------------------------------------

2) Second bug. 

We consider the first bug to be a mistake, and have been using chirpStartIdx by changing it to recognize the actual startIdx.

However, more big issue bothered us.

If ChirpstartIdx is not 0, the desired phaseshifter value cannot be set.