Other Parts Discussed in Thread: DCA1000EVM, UNIFLASH
We're using SDK 3.4.0.3. We've added commands to cli_mmwave.c to allow for a configuration of 'dfeDataOutputMode 2' and 'contModeCfg 60.25, 0, 0, 10000, 0, 131072, 30, 0, 256'.
We're getting ready to take the product to an FCC testing house and we can only use the IWR6843ISK to run the tests with. We have configurations for the chirp testing that we think will work without using LUA commands, but we need something similar for the continuous wave tests.
The code for contModeCfg is as follows:
static int32_t CLI_MMWaveContModeCfg (int32_t argc, char* argv[])
{
MMWave_ContModeCfg *contCfg = &gCLIMMWaveControlCfg.u.continuousModeCfg;
/* Sanity Check: Minimum argument check */
if (argc != 10)
{
CLI_write ("Error: Invalid usage of the CLI command\n");
return -1;
}
/* Sanity Check: Continuous configuration is valid only for the Continuous Mode: */
if (gCLIMMWaveControlCfg.dfeDataOutputMode != MMWave_DFEDataOutputMode_CONTINUOUS)
{
CLI_write ("Error: Configuration is valid only if the DFE Output Mode is Continuous\n");
return -1;
}
/* Populate the configuration: */
contCfg->cfg.startFreqConst = (uint32_t) (atof(argv[1]) * (1U << 26) /
gCLI_mmwave_freq_scale_factor);
contCfg->cfg.txOutPowerBackoffCode = (uint32_t) atoi (argv[2]);
contCfg->cfg.txPhaseShifter = (uint32_t) atoi (argv[3]);
contCfg->cfg.digOutSampleRate = (uint16_t) atoi (argv[4]);
contCfg->cfg.hpfCornerFreq1 = (uint8_t) atoi (argv[5]);
contCfg->cfg.hpfCornerFreq2 = (uint8_t) atoi (argv[6]);
contCfg->cfg.rxGain = (uint16_t) atoi (argv[7]);
/*argv[8] is reserved*/
contCfg->dataTransSize = (uint16_t) atoi (argv[9]);
return 0;
}
All of this appears to configure correctly. However, it's difficult to tell if the unit is actually running in CW mode when we send sensorStart on this configuration. This isn't really a typical data-path configuration, so we're not sure what to expect. Is there anything else we need to setup beforehand? Is there any way to confirm that this is working (or not)? If it runs, will it only run for the 256 cycles and then stop?
-Tom Grounds
