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.

RTOS/AWR1642: some questions about capture_demo

Part Number: AWR1642

Tool/software: TI-RTOS

Hi.

I'd like to ask some questions. I'm currently running capture_demo in AWR1642. And I looked at the memory content of gDataCube. 

1. I found that if I entered the default configuration, I would have gotten data that would have only one frame. My configuration is shown below. I want to get a lot of frame data content until L3 memory is full.

How do you configure parameters?

2. Can you tell me that the data we got when we ran capture_demo was in gDataCube? What size should we save the gDataCube?

3. What's the difference between chirp and frame?My understanding is that a frame is made up of many chirps and each chirp is also composed of many sampling points.This right?

  • Is there anyone to help
  • Hello Jian,

    Apologies for the delay. Someone should have an answer for you early next week.


    Cheers,
    Akash
  • Hi Jian,

    1. The capture_demo enters an infinite loop after capturing the first frame - this is to allow user's to view the raw data. You will have to edit and recompile to store more.

    2. Data is stored in GDataCube - this is a heap in L3, and the size can be reconfigured by recompiling the software. To calculate the size of a frame - Number of chirps(per Tx)*number of Rx*number of Tx*num samples per chirp*4 bytes per sample

    3. Each chirp is a linear ramp from frequency x to frequency y. We sample n times during the chirp with the ADC. Each frame is composed of multiple chirps - this is necessary to calculate velocity, and improves the accuracy of range and angle measurements.

    Regards,
    Justin