• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 647 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: Bpm-MIMO config and chirp configurations Questions

Wajih Youssef
Intellectual 535 points
Part Number: AWR1843BOOST

Hi, so I am working on lab4 obstacle detection and I want to know whether in this lab we are using MIMO configuration and if so which one, BPM or TDM ( I think it's Bpm but im not quite sure ) ? 

and Q2 : I want to replace the GUI of Matlab which i use to send chirp configuration file so when I debug the lab4 on code composer it sends automatically the chirp configuration, I asked such a question before and I was shown the example of lab5 but I did not quite know what should I modify in the code and whether it should be in the MSS project or the DSS or elsewhere.

Thanks 

  • 0
    TI__Genius 15046 points

    Hi,

    As far as I can tell, lab 4 uses TDM MIMO. While it seems that there is some code for bpm copied over from the OOB demo, it has all been commented out.

    For lab 4, the CLI is configured to have some mmwavelink specific commands (handled by CLI extension provided with the CLI utility) and a few commands on top of that (sensorStart, sensorStop, etc).

    The gist is that to bypass the CLI, you need to call all the functions that get called via these commands with the appropriate parameters. Some of these functions are in the MSS cli.c implementation of the lab, and some are in the CLI MmWave extension. For example, the "sensorStart" command has a corresponding function MmwDemo_CLISensorStart that gets called upon receiving the command in cli.c. The "profileCfg" command has a corresponding function CLI_MMWaveProfileCfg in <SDK_LOC>\packages\ti\utils\cli\src\cli_mmwave.c.

    If you call all of these functions appropriately in the lab, the data should start streaming out of the device. You could comment out the CLI_open call and call all of these functions directly in the code instead.

    I would suggest having a look at the source code of the CLI utility. It is a relatively simple application, and would make what I said above clearer.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Intellectual 535 points

    Thanks Aayush for your reply though I need to ask you about few more details like why is there code for bpm copied but it's commented out ? is it in case someone wants to utilize the bpm-MIMO in this lab so he can find that code ? 

    One more thing where Can I find the source code of the CLI utility please ? and for what you said to work you meant that I should call all the functions of the cli in the code lines in code composer with the appropriate parameters is that right ? 

  • +1 in reply to Wajih Youssef
    TI__Genius 15046 points

    Hi,

    Wajih Youssef said:
    why is there code for bpm copied but it's commented out ?

    The code for this lab seems to be a modification on the OOB demo from SDK2. It seems that the code for BPM was copied over and commented out. I can't be sure if it was intended for the user to be able to configure BPM mode.

    Wajih Youssef said:
    where Can I find the source code of the CLI utility please ?

    You can find the source code for the CLI utility at: <SDK_INSTALL_LOC>\packages\ti\utils\cli. The SDK location is C:/ti/mmwave_sdk_<ver> by default.

    Wajih Youssef said:
    and for what you said to work you meant that I should call all the functions of the cli in the code lines in code composer with the appropriate parameters is that right ? 

    That's correct. The CLI utility essentially does the same. Whenever it receives a command over UART, it finds the corresponding registered function for it and passes the CLI arguments to it. If you do the same in your code, the lab should work without the CLI.

    Regards,

    Aayush