• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 287 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.

IWRL6432BOOST: Is BPM MIMO the only option?

Alex Byrley
Intellectual 465 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432

In the MMWAVE L SDK 5.04.00.01, we see:

static int32_t CLI_MMWaveChirpCommonCfg (int32_t argc, char* argv[])
{
    ...
    if (gMmwMssMCB.profileComCfg.c_ChirpTxMimoPatSel == 4)
    {
        /* BPM-MIMO*/
        gMmwMssMCB.isBpmEnabled = 1;
    }
    else
    {
        CLI_write ("Error: c_ChirpTxMimoPatSel must have value 4 (BPM-MIMO)\n");
        return -1;
    }

    return 0;
}

Does this mean the IWRL6432 cannot do TDM? Or can we safely remove the error throw?

  • 0
    TI__Mastermind 20351 points

    Hello, 

    I think the snippet of code you have shared is from an older version of the SDK. In SDK 5.4, both BPM-MIMO and TDM-MIMO are supported. 

    static int32_t CLI_MMWaveChirpCommonCfg (int32_t argc, char* argv[])
{
    ...

    if ((gMmwMssMCB.profileComCfg.c_ChirpTxMimoPatSel == 1) || (gMmwMssMCB.profileComCfg.c_ChirpTxMimoPatSel == 0))
    {
        /* TDM-MIMO*/
        gMmwMssMCB.isBpmEnabled = 0;
    }
    else if (gMmwMssMCB.profileComCfg.c_ChirpTxMimoPatSel == 4)
    {
        /* BPM-MIMO*/
        gMmwMssMCB.isBpmEnabled = 1;
    }
    else
    {
        CLI_write ("Error: c_ChirpTxMimoPatSel must have value either 1 (TDM-MIMO) or 4 (BPM-MIMO)\n");
        return -1;
    }

    return 0;
}

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Intellectual 465 points



    It appears I am using version 5.4....

  • 0 in reply to Alex Byrley
    TI__Mastermind 20351 points

    Hi, 

    I apologize for my misunderstanding. I see now that you are using the mmWave Demo example from SDK 5.4. This demo indeed only supports BPM-MIMO mode and removing the code which throws an error upon parsing the CLI command may allow the demo to run but the decoding scheme still assumes BPM so the processing down the line will be messed up. 

    The snippet of code which I have shared comes from the motion and presence detection example which does indeed support both TDM and BPM. The processing chain is slightly different between the two but the outputs are generally similar. Please check if this example suits your needs. 

    Best Regards,

    Josh