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.

AWR1642: ODS Demo Visualizer Version Mismatch

Part Number: AWR1642
Other Parts Discussed in Thread: UNIFLASH,

Hi All,

I have followed the instructions pretty closely in the ODS guide.  When I run demo ODS_Demo_Visualizer 1.0.0 the visualizer can talk to my board, and I can send the configuration.

But I get the message "SDK Input version [major,minor] = [1,2] not matching [2,0] reported by target.  Hint: change input version/target and try again.

Thanks to Dave I am able to program the binaries using Uniflash.  And I am able to send the configuration to the AWR1642, "C:<install_dir>\lab0002_obstacle_detection\chirp_configs\mmwave_ods_demo.cfg"

I've changed to SDK 1.2 in the visualizer, to no effect.

I notice that the ODS SDK User Guide refers to labs by number, and the lab numbers of the Automotive Toolbox don't match the user guide, so something has changed and is the wrong version:

ODS Demo VIsualizer 1.0.0 (I don't see a newer version)

My chip (I am using production silicon, I believe it is ES 2.0)

The binary file I am flashing to SPI is C:<install_dir>\lab0004_obstacle_detection\prebuilt_binaries\xwr16xx_ods_ti_design_lab.bin - however, it is lab0002 in the ODS User Guide)

the Chirp Configuration file mmwave_ods_demo.cfg

I wonder if the binary I have is not matching the Demo Visualizer, something has been revised and that is why the message says 'version mismatch'

  • Hello John,
    ODS_Demo_Visualizer version 1.0.0 is independent of SDK/application version. This is the newest version which will support SDK2.0 ODS application.

    And all of the ODS-EVM available on ti.com is based on ES2.0 only. So you need to choose SDK version as 2.0 only in the Visualizer with the ODS application.

    We confirm lab number mismatch in the user guide, it should be lab0004 for obstacle detection demo. We'll rectify the doc in the next revision of release.

    Regards,
    Jitendra
  • Jitendra,

    Thank you so much, now I understand.