• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 977 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.

AWR1642BOOST: Extracting Raw Data Using the DCA1000EVM with the AWR1642BOOST

Benjamin Bartlett
Prodigy 100 points
Part Number: AWR1642BOOST

I am using the AWR1642BOOST EVM in conjunction with the DCA1000 EVM to capture complex raw data. I am using the MATLAB script from page 16 in the user guide "mmWave Radar Device ADC Raw Data Capture", and when I read the acquired data into MATLAB, I find that the fileSize is an odd number that does not match the total number of samples considering the number of ADC samples, chirps and frames.  This problem first appears in Line 37 for the code "LVDS = zeros(1, fileSize/2)."  Why am I reading an odd fileSize? 

Even when removing a very small portion of data to maintain an even number of data points at the beginning of the array, the code still crashes when creating the LVDS matrix in the for loop towards the end.

I have also noticed that when extracting the raw data from the binary file that the first 7 numbers (1, 0, 1456, 0, 0, 0, 0) in the adcData variable are consistent whenever I capture data for any number of frames, chirp loops, etc.

Is there a specific reason as to why I am obtaining too many numbers in the initial adcData array in MATLAB.  Just a reminder, this is right after I initially open the binary file and read the information.

I am using mmWave Studio v2.0.0.2.  The only values I change are the number of frames in the sensorConfig tab; the rest are default values.

  • 0
    TI__Mastermind 30405 points

    Hi Benjamin,

    Please provide your complete sensor configuration parameters including adcconfig, profile, chirp and frame parameters etc.

    Thanks

    -Nitin

  • 0 in reply to Nitin Sakhuja
    Prodigy 100 points

    • ADC Config
      • Bits: 16
      • Full Scale Reduction Factor: 0
      • Format: Complex2x
      • IQ Swap: I First

    • Profile
      • Profile ID: 0
      • Start Freq: 77 GHz
      • Frequency Slope: 29.982 MHz/us
      • Idle Time: 100 us
      • TX Start Time: 0 us
      • ADC Start Time: 6 us
      • ADC Samples: 256
      • Sample Rate: 10,000 ksps
      • Ramp End Time: 60 us
      • RF Gain Target: 30dB
      • VCO Select: VCO1
      • HPF1 Corner Freq: 175K
      • HPF2 Corner Freq: 350K
      • O/p Pwr Backoff TX0 (dB): 0
      • O/p Pwr Backoff TX1 (dB): 0
      • Phase Shifter TX0 (deg): 0
      • Phase Shifter TX1 (deg): 0
      • Bandwidth: 1798.92 MHz

    • Chirp
      • Profile ID: 0
      • Start Chirp for Cfg: 0
      • End Chirp for Cfg: 0
      • Start Freq Var: 0 MHz
      • Frequency Slope Var: 0 MHz/us
      • Idle Time Var: 0 us
      • ADC Start Var: 0 us
      • TX Enable for Current Chirp: TX0 & TX1

    • Frame
      • Start Chirp TX: 0
      • End Chirp TX: 0
      • No. of Frames: 64
      • No. of Chirp Loops: 128
      • Periodicity: 40 ms
      • Trigger Delay: 0 us
      • Duty Cycle: 51.2%
      • Trigger Select: Software Trigger

    • Enable Dynamic Power Save in Inter-Chip
      • TX
      • RX
      • LO Dist

    • Inter Rx Gain Phase Freq Control Config
      • all values are 0

  • 0 in reply to Nitin Sakhuja
    Prodigy 100 points

    Under "Capture and Post Processing", after I arm the DCA1000 and select "Trigger Frame", should I be using the "adc_data.bin" file or the  "adc_data_Raw_0.bin" file in the PostProc directory for the Dump File?

  • 0 in reply to Benjamin Bartlett
    TI__Expert 4025 points

    Hi Benjamin,

    You should be selecting adc_data.bin. What is the file size you're seeing for these two files?

    Please recreate these parameters and capture using mmWave studio.  What are the files sizes when capturing with mmWave studio?

    -Chloe

  • 0 in reply to Chloe Shay71
    Prodigy 100 points

    I just used the adc_data.bin instead of the adc_data_Raw_0.bin file and the original MATLAB code worked.

    • adc_data.bin is 32,768 KB
    • adc_data_Raw_0.bin is 33,084 KB

    In MATLAB:

    • fileSize = 16,777,216 (for adc_data.bin)
    • fileSize = 16,938,538 (for adc_data_Raw_0.bin)

    I'm not too sure why the fileSize variable changed from odd to even after the 1st test, but I'll use adc_data.bin from now on.

    Thanks for the help!