• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 94 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: IWRL6432BOOST

Aditya Shah
Intellectual 390 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: UNIFLASH, MMWAVE-L-SDK

Tool/software:

Hi, 
I am facing an issue with the IWRL6432BOOST ES2.0 board when using the Uniflash tool.

The uniflash tool provides two ways to fetch the board information - auto and manual
Using the above workflow results in two different CCXML files. 

Query:

1. Why is it different?

2. When following the auto-detection workflow, it is not working when trying to flash.

Also, I would like to know how the mmWave Radar Visualizer tool under C:\ti\MMWAVE_L_SDK_05_05_03_00\tools\visualizer, is getting the ccxml file information while flashing using dslite tool?


  • 0
    TI__Mastermind 19470 points

    Hello.

    We don't usually recommend the auto-detect feature as it detects devices based on the XDS on the EVM, which can be common across devices.  It is better the manually search for the device in UniFlash and then flash.  I believe the visualizer in the SDK is using the arprogrammer python script, which can be found here: 

    <MMWAVE-L-SDK>\tools\boot

    Sincerely,

    Santosh