AWR6843AOP: AWR6843AOPEVM

Hey Jacques,

Thanks for reaching out over E2E regarding your integration question. I would recommend sending the sensorStop CLI command to the AWR6843AOP before rebooting the Nano. This will halt the RF chirping, data processing chain, and data output until you resend the sensorStart command. This should give you time to reconnect the Nano to the AWR6843AOP before attempting to restart it.

Hopefully this resolves the issue, but let me know if you have any other questions or run into further problems.

Regards,

Kristien

Hey Jacques,

After you stop the sensor, ensure you initiate a sensor start without any arguments - i.e., sensorStart rather than sensorStart 0. This should allow the sensor to use any new configuration parameters provided since the sensorStop.

If that isn't working, you may also need to initiate a soft reset after the sensor has been stopped if you would like to change the sensor configuration which will reset the MSS core. This can be done by using the SOC_softReset function in passing in the socHandle. I would recommend modifying the MmwDemo_CLISensorStop function like so:

static int32_t MmwDemo_CLISensorStop (int32_t argc, char* argv[])
{
    int32_t             retVal = 0;

    if ((gMmwMCB.sensorState == MmwDemo_SensorState_STOPPED) ||
        (gMmwMCB.sensorState == MmwDemo_SensorState_INIT) ||
        (gMmwMCB.sensorState == MmwDemo_SensorState_OPENED))
    {
        CLI_write ("Ignored: Sensor is already stopped\n");
        return 0;
    }
    
    MmwDemo_stopSensor();
    
    MmwDemo_resetStaticCfgPendingState();

    gMmwMCB.sensorState = MmwDemo_SensorState_STOPPED;

    SOC_softReset(gMmwMCB.socHandle, &retVal)

    return 0;
}

Also, what demo are you running on the AWR6843AOP?

Regards,

Kristien