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.

IWRL1432BOOST-BSD: Issues running visualizer demos using SDK and radar toolkit

Part Number: IWRL1432BOOST-BSD
Other Parts Discussed in Thread: AWRL1432BOOST-BSD

Tool/software:

MMWAVE_L_SDK_05_05_03_00

radar_toolbox_3_10_00_05

Windows specs below

AWRL1432BOOST-BSD

Hello,


I am having issues getting any of the demos to work - I walk through the instructions to use the SDK visualizer tool, successfully flash the board, and when I try to upload a configuration and one of two things happens:


1.   I am getting an error message saying "Error halting device"

OR

2.   The configuration loads, and I get a plot on screen, but it is frozen.   I try to "restart evaluation", enable/disable data logging and nothing works.   Everything is frozen, tracking is disabled.  

My understanding is that once I upload a configuration, I should be seeing live data.   I have tried the industrial visualizer in radar toolbox as well, and I am not seeing anything happen.   I suspect I am doing something wrong, but need some advice

.   

  • Hi,

    Are you setting the device into functional mode after flashing? Are you pressing the reset switch after changing the modes?

    Regards

  • Hi, 

    yes, I am carefully setting the switches before/after flashing and then hitting reset per the on screen instructions.   Is it possible the -BSD EVM has a different switch config?   In the visualizer, I only see an option for the 1432 (no -BSD extension).   

    also, I am flashing with the doppler-ranging image.  What configuration should I then upload to the device (high peformance, object trackng, etc…)?

  • Also, I have tried running the visualizer in the AWRL1432BOOST-BSD eval user's guide - A photo of the switch configuration is below

    (:Radar_toolbox\tools\visualizers\Applications_Visualizer\Industrial_Visualizer)

    Nothing is happening - I see in the CLI terminal it is not seeing any data from the device

    I am using the config below

    C:/ti/radar_toolbox_3_10_00_05/source/ti/examples/Industrial_and_Personal_Electronics/Bike_Radar/profiles/profile_120m_40mpsec_bsdevm_16tracks.cfg

    I have tried every SOP configuration I can think of (but mainly the one shown below), and I can't get this thing to work.   Depending on when I run it, I get two issues shown below in the CLI terminal:

    Error 1

    Error 2

    Switch settings

    Config screen

  • Any updates on this one?   Hoping to resolve ASAP so I can get a demo running.   I am fairly confident that I am either doing something wrong that is quite simple, or there is an SDK issue for this board variant.   Please advise - I also have a request into my local sales rep, and will post the solution if it resolves through his team.   Thanks

  • Hi,

    Can you try this flashing this binary?

    MMWAVE_L_SDK_05_05_03_00\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL14xx-evm

    Config: MMWAVE_L_SDK_05_05_03_00\examples\mmw_demo\motion_and_presence_detection\profiles\xwrL14xx-evm\MotionDetect.cfg

  • Yeah, this does not work.   I have tried this already, but just to be sure I did it again and documented every step.    See attached.    I have tried two EVMS on 2 laptops.   I have tried the industrial visualizer in the radar toolbox as well with no luck.

    Can you please replicate this setup at TI and let me know if you have the same issue?   Is it possible to post a video of the steps you walk through to configure the board and get data? 

     

    AWRL1432BOOSTBSD issues.pdf

  • Any updates here?   Have you been able to replicate?

  • Hi,

    Are you using an ES2 silicon  ? Can you send the device image so that we'll look at the markings?

    Also, for the switch settings, please try out this way.
    1. Flashing mode - All the switches are down.
    2. Functional mode - S1.1 only up.

    If it doesn't work with this settings and the binary, then possibly you are using an ES1 silicon. We can check once you share the device image.

    Regards

  • The 1432 chip markings are shown here: