• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 423 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: can't seem to get the board to work with the Demo Visualizer.

Marvin Cantos
Expert 6690 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: DCA1000EVM, AWR1642BOOST, IWRL6432

Hi Team, 

Good day. I am posting this inquiry on behalf of the customer.

"I am starting to use the mmWave module IWRL6432BOOST and I'd like to know more about the configuration file parameters and how to set those. The device isn't supported in the Sensing Estimator like with other TI mmWave devices so it is difficult to figure out exactly how to set the chirp parameters and optimize them for my use case.

I sadly do not have access to a DCA1000EVM as they have been out of stock for a long time while I've had this device so I would like to see if I can communicate with it via serial and not have to rely on the data capture board.

The mmWave SDK manual was very helpful in figuring out the components but I can't seem to get the board to work with the Demo Visualizer.
It works with an AWR1642BOOST module which is running on SDK 2.0, but when I set it to 3.x, it is not able to connect to the 6432 board, despite me using the correct UART and Data com ports via USB. Is there any way you could help me resolve that? I have the on-board switches set to functional mode (S1.1 is on).
The error describes itself as the status in the bottom info bar on the Demo Visualizer showing it has managed to connect to one of the COM ports, but is failing to connect to the second and it keeps looping around there without showing any other signs of errors or fault.

Please help to advise. Thank you for extending your support.

Kind regards,

Marvin

  • 0
    TI__Expert 8802 points

    Hi Marvin,

    Here's my response to the customer:

    The Sensing estimator does support the 6432 devices.

    The 6432 device works with SDK 5.x. Please use the presence and motion detection visualizer located in the SDK: MMWAVE_L_SDK_05_xx_xx_xx\tools\visualizer\Low_power_visualizer_5.x.x.x

    Alternatively, they can use the industrial visualizer located in the Radar Toolbox: <radar_toolbox>\tools\visualizers\Industrial_Visualizer

    Regards,
    Tim

  • 0 in reply to Tim Henderson
    TI__Expert 6690 points

    Hi Tim, 

    Thank you for your response. Please see the feedback from our customer.

    "Thanks for that message. I am aware that the normal visualizer works, and am able to get that to work. I am however more interested in getting the Demo Visualizer running as it is the only program TI has released that allows me to output a functional .cfg configuration file. I've tried writing my own configuration files but none seem to work and I have no idea why as there is no debug output for either Visualizer program.

    Secondly, what is the difference between SDK 3 and SDK 5?"

    Please help to advise. Thank you for extending your support.

    Kind regards, 

    Marvin 

  • 0 in reply to Marvin Cantos
    TI__Expert 8802 points

    Hi Marvin,

    Below is my response to the customer:

    If you use the Industrial visualizer located in the Radar Toolbox, you can see output from the device in a terminal window that opens up when you launch the .exe file.

    Your configuration files that you are writing yourself may be invalid. Please see the sensing estimator here: https://dev.ti.com/gallery/view/mmwave/mmWaveSensingEstimator/ to check your values or to generate new configuration files.

    SDK3 is for our earlier generation devices such as 6843. SDK5 is for our new, low power devices (including IWRL6432)

    Hope this helps,

    Tim