Tool/software: TI C/C++ Compiler
Hi Jitendra,
In our previous thread, you said that the additional two chirps in the firmware looked fine. Now, I need to specifically identify them in the CLI script, so I would need to add two additional entries in the CLI script (i.e. <chirp2Idx> and <chirp3Idx>). Therefore, my CLI script would look something like: [bpmCfg -1 1 0 1 2 3] instead of [bpmCfg -1 1 0 1] in the two chirp BPM case. Is there anything I should consider when I include more entries for an API in the CLI script, like editing the cli_mmwve.c code to include the chirpEndIdx to be the arg[4] value?
sensorStop flushCfg dfeDataOutputMode 1 channelCfg 15 1 0 adcCfg 2 1 adcbufCfg -1 0 0 1 0 profileCfg 0 77 7 7 160 0 0 20 1 512 6200 0 0 30 chirpCfg 0 0 0 0 0 0 0 1 chirpCfg 1 1 0 0 0 0 0 1 chirpCfg 2 2 0 0 0 0 0 1 chirpCfg 3 3 0 0 0 0 0 1 bpmCfg -1 1 0 1 2 3 frameCfg 0 3 16 480 250 1 0 lowPower 0 1 guiMonitor -1 0 0 0 0 0 0 cfarCfg -1 0 2 8 4 4 0 5120 cfarCfg -1 1 0 8 4 4 0 5120 peakGrouping -1 1 0 0 1 224 multiObjBeamForming -1 0 0.5 calibDcRangeSig -1 0 -5 8 256 extendedMaxVelocity -1 0 clutterRemoval -1 0 compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 measureRangeBiasAndRxChanPhase 0 1.5 0.2 nearFieldCfg -1 0 0 0 CQRxSatMonitor 0 3 4 127 0 CQSigImgMonitor 0 63 8 analogMonitor 0 0 lvdsStreamCfg -1 0 1 0 sensorStart
Above is my CLI script to see the bpmCfg API with everything else.
George
