AWR1642BOOST: Runtime exception rarely seen with sensorStop command in mmwaveDemo

Hello;

I've been trying to solve an intermittent issue seen when rapidly repeating "sensorStart" then "sensorStop".

I've only recently been able to recreate the issue with only a few modifications to the stock mmwave demo source code. I believe the key is decreasing the frame period so frames are repeating as fast as possible. In most of the applications I've seen this issue, I've been using frame periods such as .5ms, 1ms, or 10ms.

These are the steps I took in the mmwaveDemo default source code to recreate the issue through the debugger:

1. Remove all interframe processing by commenting out "MmwDemo_interFrameProcessing(dataPathObj);" in dss_main.c
2. Remove all "System_printf()" calls so sensorStop and sensorStart do not spend time displaying debug messages
3. Use the following config with a 17.5ms frame periodicity and no guiMonitor data (this is the default 76-77 config from the demo visualizer, but with the frame period set to 17.5ms)
   

   % ***************************************************************
   % Created for SDK ver:01.01
   % Created using Visualizer ver:1.1.0.1
   % Frequency:76
   % Platform:xWR16xx
   % Scene Classifier:best_range_res
   % Azimuth Resolution(deg):15
   % Range Resolution(m):0.25
   % Maximum unambiguous Range(m):12.8
   % Maximum Radial Velocity(m/s):1
   % Radial velocity resolution(m/s):0.13
   % Frame Duration(msec):100
   % Range Detection Threshold (dB):15
   % Doppler Detection Threshold (dB):15
   % Range Peak Grouping:disabled
   % Doppler Peak Grouping:disabled
   % Static clutter removal:disabled
   % ***************************************************************
   sensorStop
   flushCfg
   dfeDataOutputMode 1
   channelCfg 15 3 0
   adcCfg 2 1
   adcbufCfg -1 0 0 1 0
   profileCfg 0 76 473 7 20 0 0 50 1 64 5333 0 0 30
   chirpCfg 0 0 0 0 0 0 0 1
   chirpCfg 1 1 0 0 0 0 0 2
   frameCfg 0 1 16 0 17.5 1 0
   guiMonitor -1 0 0 0 0 0 0
   cfarCfg -1 0 0 8 4 4 0 5120
   cfarCfg -1 1 0 4 2 3 0 5120
   peakGrouping -1 1 0 0 1 63
   multiObjBeamForming -1 1 0.5
   clutterRemoval -1 0
   calibDcRangeSig -1 0 -5 8 256
   extendedMaxVelocity -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
   sensorStart
   
   

4. Configure the sensor once with those settings
5. Use a terminal program such as RealTerm to repeatedly send "sensorStart" then "sensorStop" with 25ms in between each command.

After a non deterministic amount of time, either the MSS hangs waiting for sensorStop to complete, or an exception below is shown:

Do you have any thoughts on why this could be happening?

Thanks,
Erik