• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 304 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.

IWRL6432: Resetting the sensor when resending commands in the SDK5.2 visualizer

Masaya Yamagishi
Prodigy 130 points
Part Number: IWRL6432

Hi team,

How does SDK5.2 reset the baud rate when using the visualizer demo?
From the prompt below, it looks like the sensor is rebooting at the prompt, but how does it do that?

mmwDemo:/>baudRate 1250000
8
127.0.0.1 - - [25/May/2023 10:04:15] "POST /visualizer/api/vs-core/setup-device HTTP/1.1" 200 -
Join
Device reset successful and ready for reconfig!! ←here
127.0.0.1 - - [25/May/2023 10:04:19] "GET /visualizer/api/reset HTTP/1.1" 200 -
<VisualizerCore(Thread-64, started daemon 16248)>
Stopping Serial thread
Stopping Frame Parser thread
Visualizer Core Stopped

Best Regards,

Masaya Yamagishi

  • 0
    TI__Expert 8802 points

    Hi Masaya,

    Here is the function that is being called when we send baudRate 1250000

    There is no evidence of the device being reset. The UART driver is being reset to change the baudrate. I believe that message you see in the console of the visualizer may be wrong, as I see no evidence of the entire device being reset here.

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Prodigy 130 points

    Hi Tim-san,

    Thank you for your confirmation.

    What does the process look like before the config file is sent?
    It looks like the baudRate of the sensor has been changed to 115200.
    Also, I think something is going on because the reset_LED flashes.

    Best Regards,

    Masaya Yamagishi

  • 0 in reply to Masaya Yamagishi
    TI__Expert 8802 points

    Hi Masaya,

    Essentially, the program waits for a config file to be sent. You can take a look at the motion and presence detection source code in the 5.2 SDK to dig deeper and see specifics.

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Prodigy 130 points

    Hi Tim-san,

    Thank you for your answer.

    I don't think I explained myself very well.
    I would like to know about the red part of the flowchart about visualizer below.

    ・Send a cfg file
    ・Change the baud rate from 115200 to 1250000 while sending a config
    ・The demo started
    ↓
    ・Select a cfg file
    ↓
    ・I would like to know what is being done here.
    ・Is visualizer changing the baud rate from 1250000 to 115200?
    ・Is visualizer resetting the sensor?
    ↓
    ・Send a cfg file
    ・Change the baud rate from 115200 to 1250000 while sending a config
    ・The demo started

    Best Regards,

    Masaya Yamagishi

  • +1 in reply to Masaya Yamagishi
    TI__Expert 8802 points

    Hi, the flow looks like this:

    ・Send a cfg file
    ・The device change the baud rate from 115200 to 1250000 while sending a config
    ・The demo starts

    There is no resetting of the sensor, and you do not need to send a config file twice.

    Regards,

    Tim