5.3 Console Message: sensorStart Message Not Sent to Host
If the user sees some messages appear in the console messages, but not all of them and the last message is not sensorStart, then the following common errors could be the root cause:
- Commands sent earlier generated an error. User must correct the source of error (fix the user-generated configuration file, move the sliders, and so on) and try again.
- Commands sent earlier caused the software running on the device to crash and an assert or exception message is displayed. Users can connect the Code Composer Studio™ (CCS) debugger to the target device to debug this situation further. In the absence of CCS, reboot the device and start again. If the device still does not work for a given config, check the config against the mmWave SDK user's guide.
- One reason could be that the number of plots selected caused the shipment of the output data to exceed one frame duration.
- Sometimes the UART on the target device does not receive all the characters or messages (for example, the PC sends configuration data over the UART faster than the device can process). Just repeat the action (Send Config.. or Load Config..) and try again.