• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 501 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.

Original question:

IWR6843: Chirp configuration for 68xx low power demo in industrial toolbox 4.8

IWR6843: About CLI command idlePowerCycle

Kei
Intellectual 750 points
Part Number: IWR6843

Hello,

I have a question about 68xx low power demo.
Regarding CLI command idlePowerCycle, is the purpose of this command simply to power domain off and clock gating permanently?
I tried executing the command. After executing the command, the power consumption reduced, and after user specified delay, 6843 could accept CLI command,
but there are no RF output and no data flow on UART ever since.
Is the result correct?

  • 0
    TI__Mastermind 18980 points

    Hello.

    The idlePowerCycle command does indeed enable a low power mode for a specified amount of time while executing idle mode functions.  If you could provide the exact command and arguments you passed, I can confirm the behavior for the RF and UART output.  I have also linked the app note with the information on the cli command for your future reference.  Look at page 10.

    App Note:  https://www.ti.com/lit/an/swra689/swra689.pdf?ts=1659116550453&ref_url=https%253A%252F%252Fwww.google.com%252F

    Hope this helps,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 750 points

    Santosh,

    Demo binary file that I used is located at C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\demo\xwr68xx\mmw\xwr68xx_mmw_demo.bin and CLI command is idlePowerCycle -1 0 1 1 1 0 0 0 0 1, which is example written in p.11 of swra689.pdf.
    Could you the behavior for the RF and UART output?

    Regards,
    Kei 

  • 0 in reply to Kei
    TI__Mastermind 18980 points

    This behavior is correct.  Essentially the device is being slept as the sensor is stopped once this command is sent.  It is now ready to take in a new configuration.  As a result, no data comes out of the data port.  For more information, take a look at the low power demo in the labs/fundamentals folder in the toolbox.  In the cli.c file for this demo, you can find the full functionality for this command.

    Hope this helps,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 750 points

    Thank you for your reply.
    In what way can this command be leveraged?
    Is the intended use of this command only to confirm power consumption after the command executed?
    Is it possible to achieve like the below drawing of the fig below, which is supporting radar operation and reducing power consumption at the same time.

    Regards,
    Kei

  • +1 in reply to Kei
    TI__Genius 17265 points

    Hi,

    Yes, that is certainly possible. The goal of the lab was to show how it could be done, using CLI as just as an example to make it easy for users to control. There would be 2 methods to achieve what is shown in the picture

    1. 
    At the application level, you could control this all by configuring the device to chirp for X amount of frames, then calling the same sleep functions which are called by the idlePowerCycle  CLI command, and then upon wakeup configuring the device to chirp again for X frames. 

    2. 
    Use an external MCU to control this same methodology, but using the CLI interface to do so. Meaning you would send commands to configure the device to chirp for X frames, and then upon receiving all the output data, you could put the device into idle mode, and then when ready you could re-enable the device and send over the cfg for X frames again.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 750 points

    Hi,

    Thank you for your reply. I understand clearly.

    Regards,
    Kei