• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 721 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.

IWR6843AOPEVM: Hard-code configuration commands in the mmwave demo code without using demo visualizer for IWR6843AOPEVM

Matvei Klimov
Prodigy 60 points
Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: IWR6843ISK

Hello,

I am trying to hard-code all the configuration commands in the code needed to run mmwave-demo project using IWR6843AOPEVM board. The idea is to make board start working with static config, which i could change , when i power up it. Can you please guide me how to do it?

Best regards,

Matvei

  • 0
    TI__Genius 17481 points

    Hi Matvei,

     

    Please refer to the mmWave Doxygen document that details how to accomplish the CLI bypass with hard-coded configuration. I have pasted the details below.

     

    Re-implement the file mmw_cli.c as follows:

    1. MmwDemo_CLIInit should just create a task with input taskPriority. Lets say the task is called "MmwDemo_sensorConfig_task".
    2. All other functions are not needed
    3. Implement the MmwDemo_sensorConfig_task as follows:
      1. Fill gMmwMssMCB.cfg.openCfg
      2. Fill gMmwMssMCB.cfg.ctrlCfg
      3. Add profiles and chirps using MMWave_addProfile and MMWave_addChirp functions
      4. Call MmwDemo_CfgUpdate for every offset in Offsets for storing CLI configuration (MMWDEMO_xxx_OFFSET in mmw_mss.h)
      5. Fill gMmwMssMCB.objDetCommonCfg.preStartCommonCfg
      6. Call MmwDemo_openSensor
      7. Call MmwDemo_configSensor
      8. Call MmwDemo_startSensor (One can use helper function MmwDemo_isAllCfgInPendingState to know if all dynamic config was provided)

     

    We are actually releasing a new OOB demo within the next 2 weeks which uses hard-coded configuration and CLI bypass. This new lab is for the IWR6843ISK EVM, but you should easily be able to replicate the same methods for the AOP version. For the time being, though, please follow along with the method above and let me know if there are any other questions you have.

     

    Regards,

    Peter