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.

IWR1843BOOST: MSS SRR/MRR Client function

Part Number: IWR1843BOOST

Hi everyone,

I am working on SRR example and i have some doubts about the MSS Client implementation, I think that this also applies to MRR example.

I am working on a firmware that does not need that Client at all (at least it is what I think) because the program shall auto starts, as it is done in the MRR example:

Ok, by this way I can program an auto start functionality. Therefore, I think that I do not need to use the UART for that purpose and Can I use it for other things, no? However, If I call to "SRR_MSS_CLIAdvancedFrameCfg" and "SRR_MSS_CLISensorStart" without calling to "SRR_MSS_CLIInit" and consequently without opening the Client using "CLI_open", the program fails when it tries to open the mmWave module through "MMWave_open".

Therefore, what is really doing the Client? Why it needs to control the mmWave module? I am not understanding it well and I thought that the Client was only a kind of Client UART manager which process the commands. Can I remove all the UART implementation and only keep the mmWave module configuration? Something like this:

Many thanks for the support and best regards,

Javier

  • Hi,

    I am a little bit confused about the terminology.

    If I understand correctly you don't need to send commands through the user CLI to start the demo. Is this correct?

    If this is what you need you should use the code provided in

    mmwave_automotive_toolbox_#_#_#\labs\lab0007_medium_range_radar

    This code does not require the User Uart fo start the demo.

    So, yes you could use this UART for another purpose

    thank you

    Cesar

  • Hi Cesar,

    You understood it well but some doubts remain open.

    You answered me to the first part of the post but not to the second, I do not understand well what is doing the client, and I would like to ask you if you can provide me more information. Mainly, Why the client controls the mmWave module? 

    As you said and as I said in the first post, the MRR (Medium Range Radar demo) does not need the UART for the configuration. However, if you remove all the code related to the UART in the SRR example and you keep the CLI_init function like this:

    You will receive the following error:

    However, if you transform SRR_MSS_CLIAdvancedFrameCfg and SRR_MSS_CLISensorStart to extern functions like this:

    It works!! Therefore, there is some dependency that I do not really understand. Could you explain me why is working if you make that functions extern?

    I only want to understand better how works the SRR demo.

    Thanks for the support,

    Javier

  • Hi,

    Most of our demos are based on the mmWave SDK demo. This demo uses the CLI commands infrastructure to provide flexibility for configuring the demo. This feature is desirable for a general purpose demo.

    The srr/mrr demo was based on an early version of the mmWave SDK demo. In the srr/mrr demo in order to reduce program memory consumption, the configuration was hard coded. However the cli infrastructure is still present in the code.

    If you need a more detailed understanding, I recommend you re-build the src files of interest with no Compiler Optimization and step through the code. This can be performed as described in the demo user guide by importing in CCS the projectspecs provided.

    After importing the projectspecs, right click on the file that contains the src code that you would like to step through, open the Compiler options and set the Optimization level to "No optimization"

    Thank you

    Cesar

  • Hi,

    Many thanks for explaining me something that I did not ask. Now I know how to change the optimization level.

    Thank you,

    Javier

  • Thank you

    Cesar