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: HOW TO CONFIG THE DEVICE WITHOUT ANY MM-WAVE DEMO VISUALIZER AFTER EVERY POWER-UP

Part Number: AWR1642

Hi.Team,

      We are using AWR1642 device for ADAS application but  after every power-up we need to config the device using mm-wave demo visualizer but it  is difficult  to config the device every time during the field trial.

      Is there any possibility to config the device without any visualizer after every power up, the device should be configured automatically once the device is powered on.

 Hope i can get solution for  this problem. thank you.

Thanks&Regards

Akhil

  • Hi,

    It is possible to hard code the configuration and execute it at power up without demo visualizer.

    This topic has been called "bypass CLI" and has been discussed many times on this forum.

    I have tested the information in this thread and it works for mmWave SDK 3.5

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/899453/ccs-iwr6843isk-bypass-cli-in-mmwave-demo

    Example of hard-coded sensor config for 14xx using mmWave SDK 2.1 mmw demo

     

    Steps to update mmWave SDK 3.5 18xx demo to use example hard-coded config:

    1. Rename/backup existing cli.c source file in mmwave_sdk_03_05_00_04\packages\ti\utils\cli\src directory
    2. Place new cli.c file in directory
    3. Re-build cli library using gmake as described in mmWave SDK user guide
    4. Make sure to update setenv.bat with correct device (i.e. awr18xx) before executing it
    5. Make sure to run 'gmake clean' and then 'gmake all' in the mmwave_sdk_03_05_00_04\packages\ti\utils\cli directory
    6. Re-build 18xx mmw project with make file or CCS project by right-clicking on project in CCS and

    performing "Re-build" as described in the user guide on the TI Resource Explorer

     

    NOTE: If replacing/updating the example sensor config given in the cli.c file,

    make sure to use a config that was generated for the desired device and mmWave

    SDK version.

    There are other ways to implement this

    Please use google site search as follows to find information about this topic.

    site e2e.ti.com bypass CLI

  • Hi Cesar,

    Thank you for the reply. It's working now.

    Best Regards,

    Akhil