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.

AWR1642BOOST-ODS: Error Incorrect config reported by target.

Part Number: AWR1642BOOST-ODS
Other Parts Discussed in Thread: AWR1642BOOST, UNIFLASH

I am using the AWR1642BOOST-ODS with mmwave demo visualizer 2.1.0.

Writing default config results in Error Incorrect config reported by target.

Kindly advise. The sdk on the ODS seems to be 2.0 


  • On using the ODS Demo Visualizer it results in Error Invalid configuration

  • The browser message indicates, "Missing command Low power"

  • Hi,

    Sorry, for AWR1642BOOST-ODS it is a little bit challenging to understand SW support.

    The AWR1642BOOST-ODS is not supported by the mmWave SDK Demo which supports only the AWR1642BOOST.

    The release notes of the mmWave SDK mention this. The difference is in the antenna.

    The only demo that supports AWR1642BOOST-ODS is provided in the Automotive Toolbox


    Thank you


  • Hi Cesar,

    I realize the above and am only trying to do what is obvious. I am not looking at the mmWave SDK Demo support for the ODS. I am using the OOB demo binary i.e. what came with the ODS and using the ODS Demo Visualizer to visualize. Here is where I am having the issue. i.e. Invalid Configuration in my second post above. The first one was with the regular Demo Visualizer, then I realized the issue and reverted to the ODS Demo Visualizer using the OOB ODS demo binary. 

  • The error is 'Invalid configuratin Missing command low power' If that helps.



  • Thank you

    We are on the same page.

    • Using ODS demo binary: labs\lab0004_obstacle_detection\prebuilt_binaries\
    • Using ODS visualizer: lab0004_obstacle_detection\gui\ods_3d_visualizer.exe
    • Using ODS chirp profile: labs\lab0004_obstacle_detection\chirp_configs\ods_default_config.cfg

    The "low power" error is related to Automotive Toolbox/SDK version mismatch

    The oldest Toolbox I have installed is 2.7.1 and I can see that I have the low power command in the chirp profile file.

    What is the version of the Toolbox and SDK being used?

    Thank you


  • Hi Cesar,

    Please direct me to downloading the appropriate toolbox. I have not reprogrammed the binary in the ODD BOOST board. The ODS demo visualizer detects the SDK to 2.0.

    Please provide links and instructions to get the ODS going with the appropriate binary. 



  • Please download the latest Automotive Toolbox.

    I think you are already familiar with the procedure to flash a binary on an EVM using uniflash. This procedure is the same for the BOOST and BOOST-ODS board.

    If you are not familiar, please review the mmWave SDK User guide.

    The "labs\lab0004_obstacle_detection" demo uses the SDK I think you already have that installed.

    Thank you