This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWRL6432BOOST: IWRL6432BOOST

Part Number: IWRL6432BOOST

Tool/software:

Hello,

I am trying to get raw data using the IWRL6432ISK board with TI tools without requiring mmWave Studio. The TI team suggests using the “Adc_Data_Capture_Tool_DCA1000_CLI” as an alternative to mmWave Studio. However, when I use this tool, it occasionally works fine, but most of the time, I encounter errors. One particularly strange error seems to originate from the radar during CLI configuration. For example, when using the “adcLogging” command, the radar responds with “dcLogging” is not recognized, indicating that the first word of the command is missing. This issue can occur with other commands as well. Attached are some examples of the errors encountered.

Could you please guide me to resolve these issues?

  • Hello,

    This is a particularly strange issue. Does it always happen to the adcLogging cfg line? What if you were to move adcLogging down in the cfg two or three lines. Does it still mess up on this line or is it whatever parameter that is now in place of where adcLogging was?

    Best Regards,

    Pedrhom

  • Hello,

    This issue can also occur with other configuration file lines, such as 'rangeSelCfg'. Sometimes, it does not happen for any of the commands, but other issues, shown in the attached screenshots, will occur. While there are instances when the tool works correctly, it should be noted that this is not the case most of the time.

  • Hello,

    I am not certain this is a software issue. Do you ever see this behavior when running demos in other ways? Such as the Applications Visualizer demos? Also do you see this same behavior with a different USB cable and/or different USB port?

    Best Regards,

    Pedrhom

  • Hello, 

    I have run other demos with CLI and have never encountered this issue. I also checked the cables and tried using different cables and PCs, but I still don't know how to solve it.

  • Hello,

    Very strange. I am unable to recreate it, nor have we gotten any other feedback of this occurring. Do you own MATLAB? If so are you able to run the tool from source? I would try it that way, and in the case the issue still occurs to add a small "sleep" command inbetween every cfg line sent.

    Best Regards,

    Pedrhom