Flash the updated mmw_demo appimage into the AWRL1432BOOST. This paper uses radar_toolbox_4_00_00_05 and MMWAVE_L_SDK_05_05_04_02 for subsequent testing work. During the data acquisition process, we still need to rely on the serial CLI of mmw_demo to issue the cfg file. After receiving the CLI command issued by the serial port, mmw_demo will normally execute RF initialization and other necessary RF APIs, such as rl_sensChirpProfComnCfg.

An example of a cfg file verified through DCA1000 data capture tests is shown below. To adapt to data acquisition, the main modifications include: limiting the number of frames to 10 frames in frameCfg; enabling LVDS output of raw ADC data in adcLogging; disabling the low-power mode in lowPowerCfg to prevent data loss during acquisition; and seeing from chirpComnCfg that TDM modulation is used. Before testing, we also need to modify the CLI_MMWaveChirpCommonCfg function to prevent the CLI from abnormally exiting after detecting the use of TDM modulation (gMmwMssMCB.profileComCfg.c_ChirpTxMimoPatSel == 1).

sensorStop 0
channelCfg 7 3 0
chirpComnCfg 20 0 0 128 1 33 2
chirpTimingCfg 6 34 0.00 117.1875 76.5 
frameCfg 2 0 1200 32 80 10
antGeometryCfg 0 0 1 1 0 2 0 1 1 2 0 3 
guiMonitor 2 1 0 0 0 1 0 0 0 0 0
sigProcChainCfg 64 32 1 0 0 0 0 0
sensorPosition 0 0 0.3 0 0
cfarCfg 2 8 4 3 0 12.0 0 0.95 0 1 1 1 
aoaFovCfg -80 80 -20 20
rangeSelCfg 0.1 10.0
clutterRemoval 0
compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000
adcLogging 1
lowPowerCfg 0
factoryCalibCfg 0 0 40 0 0x1ff000
sensorStart 0 0 0 0