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.

AWR1243P Cascade Dev Board/TDA2xx mmwave Raw Data File alignment

We have purchased AWR1243P Cascade board and TDA2xx and are considering millimeter wave Cacade signal processing.

Using the sample script, we acquired millimeter wave raw bin data, and we were able to check the time domain, range doppler and etc with PostProc.

We have 2 question.

Q1.
I would like to develop the signal processing of raw data with Matlab. Is there any data description of raw data alignment?

Q2.
We acquired Data with the following settings.
Sample = 256
Chirp = 64
Frame = 10
Config = 12
IQ data
Rx = 4
Tx = 2 (probably)

The size of the millimeter-wave raw data file at this time was 28,311,552 bytes. How was this data size calculated?

A log file is attached below for reference.

08-Nov-2019 11:48:59: IsFPGA:,0,0,
08-Nov-2019 11:48:59: C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\RunTime,0,
08-Nov-2019 11:49:01: API:select_capture_device,DCA1000,0,
08-Nov-2019 12:05:23: API:select_capture_device,TDA2XX,0,
08-Nov-2019 12:06:19: API:select_chip_version,AR1243,0,
08-Nov-2019 12:06:19: API:select_chip_version,AR1243,0,
08-Nov-2019 12:06:20: API:ChannelConfig,7,15,0,
08-Nov-2019 12:06:20: API:AdcOutConfig,2,1,0,
08-Nov-2019 12:06:20: API:DataFmtConfig,15,2,1,0,0,0,
08-Nov-2019 12:06:27: API:select_chip_version,AR1243,0,
08-Nov-2019 12:06:27: API:select_chip_version,AR1243,0,
08-Nov-2019 12:06:27: API:select_chip_version,AR1243,0,
08-Nov-2019 12:06:30: API:ChannelConfig,7,15,0,
08-Nov-2019 12:06:30: API:AdcOutConfig,2,1,0,
08-Nov-2019 12:06:30: API:DataFmtConfig,15,2,1,0,0,0,
08-Nov-2019 12:06:30: API:LowPowerConfig,0,0,0,
08-Nov-2019 12:06:30: API:DataPathConfig,0,1,0,2,0,
08-Nov-2019 12:06:30: API:LvdsClkConfig,1,1,0,
08-Nov-2019 12:06:30: TSW1400 Sampling rate : 600000000 7500000,0,
08-Nov-2019 12:06:30: API:SetHsiClock,9,0,
08-Nov-2019 12:06:30: API:LaneConfig,15,0,
08-Nov-2019 12:06:30: API:LvdsLaneConfig,0,1,0,
08-Nov-2019 12:06:30: API:ProfileConfig,0,1435384036,500,600,4000,0,0,1636,0,256,8000,0,0,48,0,
08-Nov-2019 12:06:30: API:ChirpConfig,0,0,0,0,0,0,0,0,0,
08-Nov-2019 12:06:30: API:ChirpConfig,1,1,0,0,0,0,0,0,0,
08-Nov-2019 12:06:30: API:ChirpConfig,2,2,0,0,0,0,0,0,0,
08-Nov-2019 12:06:30: API:ChirpConfig,3,3,0,0,0,0,0,0,0,
08-Nov-2019 12:06:30: API:ChirpConfig,4,4,0,0,0,0,0,0,0,
08-Nov-2019 12:06:30: API:ChirpConfig,5,5,0,0,0,0,0,0,0,
08-Nov-2019 12:06:30: API:ChirpConfig,6,6,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,7,7,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,8,8,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,9,9,0,0,0,0,0,4,0,
08-Nov-2019 12:06:31: API:ChirpConfig,10,10,0,0,0,0,0,2,0,
08-Nov-2019 12:06:31: API:ChirpConfig,11,11,0,0,0,0,0,1,0,
08-Nov-2019 12:06:31: API:ChirpConfig,0,0,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,1,1,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,2,2,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,3,3,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,4,4,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,5,5,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,6,6,0,0,0,0,0,4,0,
08-Nov-2019 12:06:31: API:ChirpConfig,7,7,0,0,0,0,0,2,0,
08-Nov-2019 12:06:31: API:ChirpConfig,8,8,0,0,0,0,0,1,0,
08-Nov-2019 12:06:31: API:ChirpConfig,9,9,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,10,10,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,11,11,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,0,0,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,1,1,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,2,2,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,3,3,0,0,0,0,0,4,0,
08-Nov-2019 12:06:31: API:ChirpConfig,4,4,0,0,0,0,0,2,0,
08-Nov-2019 12:06:31: API:ChirpConfig,5,5,0,0,0,0,0,1,0,
08-Nov-2019 12:06:31: API:ChirpConfig,6,6,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,7,7,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,8,8,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,9,9,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,10,10,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,11,11,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,0,0,0,0,0,0,0,4,0,
08-Nov-2019 12:06:31: API:ChirpConfig,1,1,0,0,0,0,0,2,0,
08-Nov-2019 12:06:31: API:ChirpConfig,2,2,0,0,0,0,0,1,0,
08-Nov-2019 12:06:31: API:ChirpConfig,3,3,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,4,4,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,5,5,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,6,6,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,7,7,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,8,8,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,9,9,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,10,10,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:ChirpConfig,11,11,0,0,0,0,0,0,0,
08-Nov-2019 12:06:31: API:EnableTestSource,0,1,0,
08-Nov-2019 12:06:32: API:FrameConfig,0,11,10,64,20000000,0,512,0,
08-Nov-2019 12:06:32: API:AdvancedFrameConfig,1,0,0,0,12,64,20000000,0,1,1,20000000,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
08-Nov-2019 12:06:32: API:EnableTestSource,0,1,0,
08-Nov-2019 12:06:32: API:FrameConfig,0,11,10,64,20000000,0,512,0,
08-Nov-2019 12:06:32: API:AdvancedFrameConfig,1,0,0,0,12,64,20000000,0,1,1,20000000,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
08-Nov-2019 12:07:28: API:SensorStart,0,
08-Nov-2019 12:07:28: API:SensorStart,0,
08-Nov-2019 12:07:28: API:SensorStart,0,
08-Nov-2019 12:07:28: API:SensorStart,0,

  • Hi,


    If you read the data in Matlab as int16 values, then you can reshape it as (2, numRx, numSamples, numChirps, numLoops, numFrames), where the first index is for the I and Q channels.

    Note that the number of frames actually captured by the device may be less than the programmed number of frames due to frame drops. In your case, it appears that your raw data file has 9 frames of data. Note also that you should ignore the data for the first frame as it might be corrupted. This is currently a known issue.

    Best Regards,

    Anand

  • Hi Anand

    Thank you for your replay.

    I will confirm it.

    If I can not confirm it, I will ask again.

    Regards,

    Suzuki