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: Out of box demo example code in Radar tool box 1.0026 is not available ?

Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432,

Hi,

   I wanted to build the source code of Out of Box demo code written IWR6432Boost, which has Cortex-M4F processor.

But i am unable to find the code for IWRL6432.

Screenshot attached as below : 

Please let me know how can i get OOB code for IWRL6432BOOST.

  • Hello, 

    For the IWRL6432, the Out of Box demo code and .projectspec file (used for importing CCS projects) are both located in the mmWave SDK v5.x this is different from our previous generation devices where the .projectspec file is stored in the Radar Toolbox. Sorry for the confusion here. 

    Best Regards,

    Josh 

  • Thanks Josh.

    When i downloaded mmwavesdk-L , and went through user guide.

    The listed steps are : 

    1. Step 1 : Connect the EVM to the PC via USB

    2. Step 2 : Select the Device on the Visualizer. Check the SOP settings for “Functional mode”

    3. Step 3 : “AUTO Detect” COM ports

    4. Step 4 : In “System Config” tab of the visualizer perform “Scene Selection”

    5. Step 5 : “Send Config to Device” 6. Step 6 : “Plots” tab should display point cloud information

    But when i went to demovisualizer, i dont see the demo visualizer supporting IWRL6432BOOST device, as shown below : 

    SHould we use XWR64 series one ?

  • Even XWR64 series  seem to have trouble connecting to XWRL6432BOOST.

    Can you please help me to run sample code and visualize Radar RD-map, profiles etc.

  • Hi, 

    The mmWave Demo Visualizer on dev.ti.com does not currently support the xWRL6432. You can run sample code and visualize the radar data with the visualizer provided in the mmWave SDK 5.x ({SDK_INSTALL}/tools/visualizer).

    Best Regards,

    Josh

  • Hi Josh,

       Got the visualizer from tools folder. But now the format in which the config file is sent and reading something like Rangeprofile from UART seem to be different from other TI Radar series. I mean such as magic words and sending config from chirp cfg etc ....

    Do you have any documentation that i can refer to tap Range profile data from UART port ? And also here , seem like one port is used unlike in other where cfg Port and Data port are used for sending config and data respectively. Can you please guide me how i can send a config file of my own and receive Range profile data from this device.

  • Hello, 

    The configuration file format should be quite similar to the previous generation devices (which use SDK 3.x). Some of the individual commands have changed a bit but the general structure and process to configure the device is the same. You can find more information on each of the CLI commands used in this demo in the tuning guide ({SDK_INSTALL}/docs/MotionPresenceDetectionDemo_TuningGuide.pdf). Configuration Parameters (section 3) has this info.

    Are you successfully able to run the demo with the default configuration in the visualizer and see the range profile on the plots tab?

    Do you have any documentation that i can refer to tap Range profile data from UART port ?

    Documentation on demo output data format can be found in the implementation guide ({SDK_INSTALL}/docs/MotionPresenceDetectionDemo_documentation.pdf), Range Profile TLV is documented in section 12.1.4. The only difference on the Range Profile TLV for this SDK compared to SDK 3.x is that the size is doubled. Each value being a uint32 compared to uint16 before. 

    seem like one port is used unlike in other where cfg Port and Data port are used for sending config and data respectively.

    You are correct. In the out of box demo (Presence and motion detection), only a single com port is used for both control and data. 

    Can you please guide me how i can send a config file of my own

    You are able to send a custom configuration file using the SDK visualizer. You can start by selecting one of the default configurations (Presence Detect or Motion Detect) on the Device Configuration tab, then at the bottom select Save Config to PC. You can then make modifications to the downloaded configuration file (.cfg) referencing the documentation mentioned above. Once you have a configuration you'd like to try you can return to the Device Configuration tab of the visualizer and select Browse under the Add cfg section to browse for and send the custom configuration file to the device. 

    Best Regards,

    Josh

  • Sorry Josh my later reply.

    From the visualizer i am able to see plots. But i want to write my own python script which can send cfg file and read Range profile data from UART port.

    How to do this ? Can you please share some pointers. 

    Since we use same COM port for sending cfg file and then reading data from same port , how and when we have to send and wait for data to come . Any document which can give these details ? or any script of your visualizer code, which we can see and modify as per our need.?

  • Hi, 

    Understood. We don't have any documentation which describes this process directly but I can point you to our Industrial Visualizer which, as of the latest Radar Toolbox release, now supports IWRL6432 Out-of-Box Demo (Presence and Motion detection). You can download the latest Radar Toolbox from dev.ti.com and view the source code for this visualizer at {TOOLBOX_INSTALL}\tools\visualizers\Industrial_Visualizer\. You can reference this code in developing your own application or you can use this code as a starting point and modify for your needs, 

    Best Regards,

    Josh

  • Thanks Josh.

    But the prerequisite that it is asking for SDK version is not available at your site.

    i.e : MCU_PLUS_SDK_XWRL64XX with version number 5.00.00 , whereas at TI site, we have version starting from 5.01.

    I have installed 5.01 , but this version difference would be good to check.

  • Hello, 

    That appears to be a mistake. Radar Toolbox 1.0.1 is supporting mmWave SDK 5.1. Sorry for any confusion and thanks for bringing this mistake to our attention. 

    Best Regards, 

    Josh