Hi,
My customer use the mmw demo in mmwave SDK 1.0 for test, changed the configuration based on the profile_2d.cfg, the changes are labeled as yellow shown in below. Then the demo cannot run well, connect the EVM board through JTAG, then just load the DSS symbol, found DSS stop at below code. It indicates the previous chirp process is not completed in one chirp period.
DebugP_assert(dpObj->chirpProcToken == 0); //software abort code
Added test variable to record the cycle consumption of function MmwDemo_processChirp(dataPathObj), normally the consumption time is about 6.5us, but sometimes it reaches about 18.5us which is greater than the below configured chirp period(18us), it is very strange. Pls help investigate the issue. If any unclear pls feel free let me know, thank u very much.
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg 0 0 1 1
profileCfg 0 77 2 5 16 0 0 9 1 64 6250 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 32 0 100 1 0
lowPower 0 0
guiMonitor 1 1 1 0 0 1
cfarCfg 0 2 8 4 4 0 5120
cfarCfg 1 0 8 4 4 0 5120
peakGrouping 1 0 0 1 224
multiObjBeamForming 1 0.5
calibDcRangeSig 0 -5 8 256
sensorStart
Andy
