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.

CCS/AWR1642BOOST: ADC raw data for 4 Rx by using mem_capture demo

Part Number: AWR1642BOOST

Tool/software: Code Composer Studio

Hi,

I'm using AWR1642BOOST ES2.0 with the capture demo to get the raw ADC data from L3 memory, and the SDK version is mmwave_sdk_02_01_00_04. When I use  defalut setting in the mss.c, it works well. Now, I want to increase the Rx numbers from 1 to 4, and some other parameters are also modified. The whole parameters changed are below.

/* Populate the profile configuration: */
ptrProfileCfg->profileId = 0U;
ptrProfileCfg->startFreqConst = (uint32_t)(77.0 * (1U << 26) / 3.6);
ptrProfileCfg->idleTimeConst = (uint32_t)(12U * 1000 / 10); 
ptrProfileCfg->adcStartTimeConst = (uint32_t)(5 * 1000 / 10); 
ptrProfileCfg->rampEndTime = (uint32_t)(50 * 1000 / 10); 
ptrProfileCfg->txOutPowerBackoffCode = 0U;
ptrProfileCfg->txPhaseShifter = 0U;
ptrProfileCfg->freqSlopeConst = (int16_t)(15U * (1U << 26) / (3.6*1e3*900)); 
ptrProfileCfg->txStartTime = (int32_t)(1U * 1000 / 10); 
ptrProfileCfg->numAdcSamples = 256;
ptrProfileCfg->digOutSampleRate = 6250; 
ptrProfileCfg->hpfCornerFreq1 = 0;
ptrProfileCfg->hpfCornerFreq2 = 0;
ptrProfileCfg->rxGain = 44; 

ptrFrameCfg->chirpStartIdx = 0U;
ptrFrameCfg->chirpEndIdx = 0U;
ptrFrameCfg->numLoops = 128;
ptrFrameCfg->numFrames = 1; 
ptrFrameCfg->framePeriodicity = (uint32_t)(100 * 1000000 / 5); 
ptrFrameCfg->triggerSelect = 1U;
ptrFrameCfg->frameTriggerDelay = (uint32_t)(0 * 1000000 / 5); 

/* Populate the open configuration: */
ptrOpenCfg->freqLimitLow = 760U;
ptrOpenCfg->freqLimitHigh = 810U;
ptrOpenCfg->chCfg.rxChannelEn = 15U; 
ptrOpenCfg->chCfg.txChannelEn = 1U;
ptrOpenCfg->chCfg.cascading = 0U; 
ptrOpenCfg->lowPowerMode.lpAdcMode = 1U; 
ptrOpenCfg->adcOutCfg.fmt.b2AdcBits = 2U; 
ptrOpenCfg->adcOutCfg.fmt.b2AdcOutFmt = 1U; 
ptrOpenCfg->disableFrameStartAsyncEvent = false;
ptrOpenCfg->disableFrameStopAsyncEvent = false;
ptrOpenCfg->useCustomCalibration = false;
ptrOpenCfg->customCalibrationEnableMask = 0x0;

After storing the data in L3 memory, I used a matlab script from SDK 1.0 to parse the data. Then I get a picture like this.

5037.untitled.tif

There are 256 * 128 = 32768 samples in this picture. But it actually has only 32 chirps and every chirp with 1024 samples. For a range FFT result, it shows like below.

un2titled.tif

So,what is the problem for capturing 4 Rx's data? Are there any mistakes I made in  mss.c or miss some necessary parameter modified ?

Thanks!

  • Hi,

    Capture demo is no longer supported in SDK 2.1.

    Support would come from forum community.

    Will let the forum community answer this thread

    Thank you
    Cesar
  • Hi Cesar
    Thanks for your reply. Actually, I have browsed most of the posts about capture demo in the forum. But most of threads are using the method provided by SDK 1.0, I can not get too much help from them. So, I would appreciate it very much if anybody could tell me how to capture the correct data for 4Rx by using capture demo in SDK 2.0 or 2.1.
    Thank you,
    Jay
  • Hi Jay

    As I mentioned there is no capture demo in SDK 2.1

    You will need to port the Capture demo from SDK 1.0 to SDK 2.1

    Let's see if anybody in the forum community has ported this demo to SDK 2.1

    Thank you
    Cesar
  • Hi Cesar

    Thanks for your reply. You said that there is no capture demo in SDK 2.1, but I found the similar one in the folder "mmwave_sdk_02_01_00_04\packages\ti\drivers\test\mem_capture\xwr16xx". Then I followed the steps that provided in chapter 4.5 of SDK_user guide, and I got the new compiled xwr16xx_mem_capture_dss.xe674 and xwr16xx_mem_capture_mss.xer4f which would be used in CCS to capture raw data.Just like this.

    And my EVM version is 2.0, is it useful that port the Capture demo from SDK 1.0 to SDK 2.1?

    Thank you

    Jay

  • Yes,

    You are right. In SDK 2.0 the full capture demo is no longer supported. However a unit test was provided in the drivers folder.

    You can definitely use that with SDK 2.0

    Thank you
    Cesar
  • Hi Cesar

    Thanks for your reply. The full capture demo is no longer supported, but a unit test is available. So, what is the difference between full capture

    demo and unit test? Can I get the correct raw data of 1Tx & 4Rx, or can I only capture the correct raw data for 1Tx & 1Rx? Are there some

    parameters in mms. c that cannot be modified? Please forgive me for having so many questions.

    Thank you
    Jay
  • Hi,

    The behavior of the unit test and capture demo are similar. However the unit test has a hard-coded config whereas the capture demo supported a config through the cli

    Please see description in the unit test header file

    mmwave_sdk_02_01_00_04\packages\ti\drivers\test\mem_capture\capture.h

    Thank you
    Cesar