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/AWR1642: How to read the raw data collocted by mem_capture porvided in C:\ti\mmwave_sdk_02_01_00_04\packages\ti\drivers\test\mem_capture?

Part Number: AWR1642
Other Parts Discussed in Thread: MMWAVE-SDK,

Tool/software: Code Composer Studio

I used the mem_capture provided in   C:\ti\mmwave_sdk_02_01_00_04\packages\ti\drivers\test\mem_capture to collect raw data. I saved it with two formats binary and 16bit hex-TI style.

and the start address is 0x20000000,length is  131072  (=512kb = 512*1024/4).while I can’t read the raw data correctly and process it .So how I can read the raw data into matlab and process it correctly ?

  • Hi,
    Please refer this document which explain much about processing the raw data using Matlab script.
    www.ti.com/.../swra581b.pdf

    Regards,
    Jitendra
  • Dear Jitendra
    Thank you so much for your replay, I can see the processing raw data by DCA1000 with X16xx using Matlab ,while how about the raw data collected by CCS memory? Is there any matlab script?
  • Hi Lu Tan,
    Please refer mmWave-SDK 1.0 version which has capture demo application along with Matlab script to process capture data from CCS.
    software-dl.ti.com/.../index_FDS.html

    Refer SDK user guide to get the step to capture raw data from CCS using Capture-demo application.

    Regards,
    Jitendra
  • Dear Jitendra
    TKS, I find capture_demo.m from C:\ti\mmwave_sdk_01_01_00_02\packages\ti\demo\xwr16xx\capture\gui, I will refer this to process capture data from CCS,it's the same data storage format when we colloct data by mem_capture provided in SDK 2.1, right?

  • Hi Lu Tan,
    Both of this demo dumps ADC-buffer data to L3 memory which you save from CCS memory, so format should be same from both version of applications.

    Regards,
    Jitendra
  • Dear Jitendra

    while the raw data collected by mem_capture seems alternate in size,big and small.  ADC samples figure is on the below. I repeat this operation many times ,it's not change.Do you why? and  how I can get the right raw data?

  • Hi Lu Tan,
    It dumps only single frame data to L3 memory (0x21000000), so you won't see any update after it dumps first data. This application configures eDMA for single frame worth of data to copy ADC data from ADCBuffer to L3 memory.

    And try to use Matlab script(gui\capture_demo.m) from SDK 1.0 which plots the captured data. Make sure that you follow the steps to save the memory from CCS (16-bit Hex TI style and file Type: TI Data [*.mat]).

    Regards,
    Jitendra
  • Dear Jitendra
    sorry for late reply, I'm sure I save the memory from CCS by TI data , 16 bit hex TI style ,and plot the captured data by matlab script(gui\capture_demo.m) from SDK1.0.
  • Hi,

    You might not be capturing the right size of data from CCS. Follow this setting-

    Regards,

    Jitendra

  • Hi Jitendra

    I changed the size of data from CCS,but still got the raw data which seemed uncorrecte.It looked like last time, as below

    1.Could I know why the right size of data is 0x10000?

    2.Only one frame can be saved in memory when it starts working ,and it can't be refreshed after that,right?

    3.when I plot the raw data by matlab script ,I should modify the chirp configuration parameters as it's in mss.c. Is there anything I should pay attention to?

  • For the configuration total no. of bytes in a frame
    256(numSample) * 2 (complex2x) * 2 (16Bit each) * 1 (numOfRx) * 128 (numOfChirps) = 0x20000

    In CCS you need to capture in 16Bit style so you need to capture 0x10000 size (16Bit word size).

    I would suggest to use SDK 1.0 capture_demo and matlab script to verify your experiment. This application you need to load from CCS when ccsdebug.bin (SDK 2.1 +) is flashed to AWR1642 ES2.0 EVM.

    I have use these configuration

    capture_demo_script.txt:--
    /* CLI command script to have 1 frame with 128 chirps */
    flushCfg
    dfeDataOutputMode 1
    channelCfg 2 1 0
    adcCfg 2 1
    adcbufCfg 0 0 1 1
    profileCfg 0 77 20 5 80 0 0 40 1 256 6000 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 128 1 20 1 0
    lowPower 0 1
    sensorStart


    Matlab script contains the configuration which must match with the configuration you send to device, so please note this point as well.


    Regards,
    Jitendra