• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 468 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.

AWR1843BOOST: Out of Box demo_1843

Rehman
Intellectual 265 points
Part Number: AWR1843BOOST

Tool/software:

Haii...,

Our project requires out_of_box_1843 demo which has CLI commands option. 

In it we need to modify the demo accordingly to our needs. But when I made the changes and build it ,the bin file was not generated and the option to rebuild it was also not there.

So there any way that we can modify the OOB demo.

Thanks,

Rehman

  • 0
    TI__Expert 4480 points

    Hi Rehman,

    What modification you made and in which file? Can you elaborate the same?

    BR,

    Animesh Anand

  • 0 in reply to Animesh Anand
    Intellectual 265 points

    I need to modify in mmw_cli.c file. The modification i need is :- after "sensorStop" command I need to upload new chirp configs without rebooting the board.

    so in mmwave demovisualiser when I did sensorStop and uploaded new chirp config it throwed an error. When I went through the code I found this :- 

    else
    {
    /* openCfg related configurations like chCfg, lowPowerMode, adcCfg
    * are only used on the first sensor start. If they are different
    * on a subsequent sensor start, then generate a fatal error
    * so the user does not think that the new (changed) configuration
    * takes effect, the board needs to be reboot for the new
    * configuration to be applied.
    */
    MMWave_OpenCfg openCfg;
    CLI_getMMWaveExtensionOpenConfig (&openCfg);
    /* Compare openCfg->chCfg*/
    if(memcmp((void *)&gMmwMssMCB.cfg.openCfg.chCfg, (void *)&openCfg.chCfg,
    sizeof(rlChanCfg_t)) != 0)
    {
    MmwDemo_debugAssert(0);
    }

    /* Compare openCfg->lowPowerMode*/
    if(memcmp((void *)&gMmwMssMCB.cfg.openCfg.lowPowerMode, (void *)&openCfg.lowPowerMode,
    sizeof(rlLowPowerModeCfg_t)) != 0)
    {
    MmwDemo_debugAssert(0);
    }
    /* Compare openCfg->adcOutCfg*/
    if(memcmp((void *)&gMmwMssMCB.cfg.openCfg.adcOutCfg, (void *)&openCfg.adcOutCfg,
    sizeof(rlAdcOutCfg_t)) != 0)
    {
    MmwDemo_debugAssert(0);
    }
    }

    So I am now thinking to make some changes in the sensorStop function such that after  SensorStop command I can load a differnt type of chirp config.

  • 0 in reply to Rehman
    TI__Expert 4480 points

    Hi Rehman,

    Can you provide SDK version you are using, or you are using the demo from toolbox?

    BR,

    Animesh Anand

  • 0 in reply to Animesh Anand
    Intellectual 265 points

    Hai Animesh..., The SDK version is 3.6 and we are taking the demo from Radar Toolbox-2.10.00.04. 

  • 0 in reply to Rehman
    TI__Expert 4480 points

    Hi Rehman,

    You need to reset the device for giving new configuration as the device is already calibrated for some config and then you cannot modify it. We recommend you use it one config at a time.

    BR,

    Animesh Anand

  • 0 in reply to Animesh Anand
    Intellectual 265 points

    Ya this we know...., but we need to modify the firmware such that without restarting the board we can give different chirp configurations. 

    Is this thing possible...If YES....could you guide us.

  • 0 in reply to Rehman
    TI__Expert 4480 points

    Hi Rehman,

    According to design team you can give only one configuration at a time. So, I don't think it is possible.

    BR,

    Animesh Anand

  • 0 in reply to Animesh Anand
    Intellectual 265 points

    Ok got it....., so is there any option to reset the board via the firmware so to upload each new config we can do a software reset.