Tool/software:
I am using CCS 20.1, radar toolbox 2.30.0.12, and mmwave SDK 3.06.2. I wss having trouble getting MSS and DSS running with the debugger, so changed the mss to NOT automatically start the sensor. For this, I enabled the CLI interface and then start the sensor via the CLI using the "advFrameCfg" command followed by the "startSensor" command. I now get output to the MRR Visualizer. I updated to the application to capture some data during a run to RAM. The application continues to run fine for extended periods of time while capturing data. (I use a circular buffer for capturing data, so memory utilization is limited). I added a CLI command to dump this data in text form to the CLI output. The issue I am running into is that when I dump a good bit of data (more than a line or two of text), the sensor will stop. I cannot track down or see any error of any sort. Attempt to stop and restart the sensor does not work. So, my conclusion is that somehow using the CLI has the potential to interfere with the sensor. I would assume that the CLI is running at a lower priority than the sensor, so expectation is that this writing a dozen lines or so of text to the CLI should not interfere. Is it possible for the CLI to interfere with the sensor operation?
