AWRL6432: CCS debug failed when running sensor start

Hey Sreekesh,

First of all, what .cfg profile are you sending over to the device and how have you been sending over the .cfg? Are you using the CCS serial terminal? If you are using a custom .cfg, you might want to quickly test out one of the existing profiles for the demos - i.e., parking_5m.cfg for mmWave Demo and MotionDetect.cfg or any of the motion/presence/tracking.cfg's for Motion and Presence Detection Demo. If you are using the CCS serial terminal, you can manually type in "1250000" to set the baud rate. If you are still having issues, then you can step through the mmwDemo_DpcExecute function in whichever demo you are using to see if something in the configuration is causing issues. 

In case all of the previous steps do not work, you can try to re-flash the ATE calibration data onto the board. Its unlikely that the calibration data is wrong, and it usually ends up being a configuration issue which is why I would recommend following the previously mentioned steps. To re-flash the ATE calibration data, you can follow the instructions for the first question written in this FAQ: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1182245/faq-xwrlx432-common-questions-and-resources-for-xwrlx432. There is also some other information on that post that may be useful if you run into other issues. 

For the UART terminal freezing up after typing the baudRate CLI command, you will have to reopen the UART port with the baud rate you have set it to after sending the command - i.e., send all the chirp configuration commands at 115200 then bump up to 1250000 after sending the baudRate command. 

Let me know if there are any other questions.

Regards,

Kristien

Hey Sreekesh,

For the UART output, it is outputting the TLV data which contains information such as detected points, heatmap data, etc.. You can read more about the UART output and TLVs in the following Radar Toolbox guide: 

https://dev.ti.com/tirex/explore/node?node=A__ADnbI7zK9bSRgZqeAxprvQ__radar_toolbox__1AslXXD__LATEST&placeholder=true

If you would like to parse this TLV data, you will either have to add your code to the demo code or you can run the Industrial Visualizer in the Radar Toolbox - found under <RADAR_TOOLBOX>/tools/visualizers/Industrial_Visualizer - and check the "Save UART" box. For the Industrial Visualizer, it will output .bin files every 100 frames to the binData folder in the same directory as the visualizer. You can then use the parseStandardFrame function from parseFrame.py to parse the .bin file. I've included a Python script I threw together that will pull in a file and decode all of its frames - though it does nothing with the decoded TLV data.

It is normal that the program is polling the UART while sending TLV data so there's nothing going wrong on that part. If the program is getting stuck in a DebugP_assert statement or Hwi interrupt after pausing the program, this is likely due to the power management task that checks whether or not the device can enter low power mode amongst other conditions. This can be fixed by setting the lowPowerCfg to 2 when sending over the CLI commands which will emulate that check but prevent any assertion issues.

For the SysConfig, the Baudrate parameter is used to set the initial baud rate for the device. The baudRate CLI command will overwrite the device's baud rate regardless of the initial setting.

At this point, I believe it would be better to open up a new thread if you continue to have any more issues with the output as this discussion is starting to deviate from the original question. This helps other users find information relevant to issues such as yours in the future. You can also search the rest of the E2E forums to see if someone else has already asked a question similar to yours. If you do open up a new thread, I would recommend leaving a link here in case someone does stumble into this thread and follows along with everything discussed so far.

Regards,

Kristien

# Local File Imports
from parseFrame import *

# add path to TLV binary file
filepath = ""

def parseBin(filepath):
    # output list of decoded TLV data
    tlvDecoded = []
    with open(filepath, "rb") as f:
        # read entire binary file
        binaryFileData = bytearray(b'')
        binaryFileData = f.read()
        # separate out individual frames using magic word; first element is always b'' so skip it
        frames = binaryFileData.split(UART_MAGIC_WORD)[1:]
        for frameData in frames:
            tlvDecoded.append(parseStandardFrame(UART_MAGIC_WORD + frameData)) # magic word needs to be added back for parseStandardFrame to work
    return tlvDecoded

def main():
    print("Parsing binary data . . . ")
    # parse through TLV binary file
    tlvDecoded = parseBin(filepath)
    # use decoded TLV data for application

if __name__ == "__main__":
    main()