• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 477 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.

CCS/AWR1642BOOST: AWR1642 CLI remain enabled ?

Rushikesh Munde
Prodigy 30 points
Part Number: AWR1642BOOST

Tool/software: Code Composer Studio

Can we keep CLI remain enable even after sensor is started ?

I noticed that when “sensorStart ” command is entered, sensor starts and CLI is disabled. 

I am planning to receive data on CLI(UART) via python code where CLI will  remain enabled and wait for data to come.

When data will come, I will process it same as CLI configuration is done.

But I am facing a difficulty here, I am not able to keep CLI enabled after sensor is started, I could keep it enabled only for once when sensor is started .

But I want to keep it remain enabled same as you keep it when we enter “sensorstop” command.

Could you help me with this?

  • 0
    TI__Guru 69960 points

    Hi Rushikesh,

    Which application you are using here?

    mmw demo application doesn't block the CLI input even after sensorStart, the application should able to receive next CLI command.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 30 points

    Hello Jitendra,

    I am using Non_OS demo for our application. 

    In Non_OS demo I have to enter CLI commands manually, and when I enter "sensorStart" command following function gets called,

    In that "notifySensorStart" function gets called where CLI is disabled, please refer to the following function. 

    After this,the control goes to following, where Rf-init is sent on UART and it stops working. 

    I tried enabling the CLI after sensorStart, But I am unable to keep it remain enabled ?

    How do I do that ? Where in the function I can re enable that?

  • 0 in reply to Rushikesh Munde
    TI__Guru 69960 points

    Hi,

    In nonOS it will be difficult to enable this feature to accept any command after sensorStart CLI command.

    As it is non OS environment and there is no way to have context switching or multi-thread. As you send the sensorStart command, MSS will start getting the object result from the DSS which is further sent over UART. Due to lack of thread/context switching, it can't jump to CLI command listening function (if at the same time you send any CLI command).

    If you really need to have this feature then better to switch to OS based application (mmw demo).

    Regards,

    Jitendra

  • 0 in reply to Rushikesh Munde
    TI__Mastermind 21025 points

    Anything else on this thread?

    I took a quick look at the non-OS demo, and while I haven't tried it, seems like it should be possible to check for CLI input inside the function MmwDemo_nonOsLoop, which loops forever once chirping has started.  Note that if you are trying to reconfigure the chirp, this won't help because you will first need to stop the front end.  But a software-only reconfiguration such as CFAR or some other parametric change it should be okay.

     -dave