• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 4 answers
  • Subscribers 30 subscribers
  • Views 257 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.

IWRL6432AOPEVM: IWRL6432AOPEVM

Rampratap Chauhan
Prodigy 80 points
Part Number: IWRL6432AOPEVM
Other Parts Discussed in Thread: SYSCONFIG, IWRL6432AOP

Tool/software:

Hi friends I am working on low power radar sensor and I am using the board IWRL6432AOPEVM. We will later move on to design our custom board with the same hardware. For the purpose of saving power I want to keep the board in deep sleep/ low power mode and wake up it with GPIO interrupt with a host MCU to read the data of distance in front of it every 5 minutes. What are the steps to achieve this , I am using MMWAVE_L_SDK_05_05_03_00. Is there any pin accessible on the board IWRL6432AOPEVM to test this feature?

Thank You.

  • 0
    TI__Mastermind 18980 points

    Hello.

    Please refer to the power driver example in the SDK to see how to set this up.  You can configure LPDS in SysConfig to set a GPIO pin as a wakeup source and you can set this pin in SysConfig as well.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 80 points

    Hi Santosh, thanks for your response I will check the mentioned example. 

    Is there any GPIO pin available on the MCU of the IWRL6432AOPEVM board which I can drive with the host MCU to test this feature?

    Thank You.

  • 0 in reply to Rampratap Chauhan
    TI__Mastermind 18980 points

    Yes.  SysConfig will automatically select an available pin to use, and will tell you which pin it is using.  You can also select whichever pin you want if you don't want the assignment done by SysConfig itself.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 80 points

    Hi Santosh, thanks for this information, Below I have few queries that might aid in our custom board design. Basically we want to keep the power consumption minimum and we want to read the TLV Point Cloud data and to keep the size small we want to remove the component which will not be required as per our use case.

    1. What is the use of QSPI flash memory?

    2. As Per my understanding the M4F MCU is used to process the raw data from the 6432AOP module and send it in TLV packet on UART which is understandable by visualizer/host MCU. So this MCU should also be the part of our custom board along with the Host MCU right? I am asking this because I saw in the schematic that XDS_DCA_RS_232_TX(carries processed data in TLV format) and XDS_DCA_RS_232_RX both signals are coming from the XI6432BRQAAMY chip so if we are getting the TLV data direct from the 6432AOP what is the use of M4F MCU?

    3. What is the use of EEPROM connected on I2C?

    I would be really grateful for your Additional suggestions as per above mentioned our design requirements.

    Thank You.

  • 0 in reply to Rampratap Chauhan
    TI__Mastermind 18980 points

    Hello.

    Rampratap Chauhan said:
    1. What is the use of QSPI flash memory?

    This is used to store the application image you want to boot; it is not required but is a frequent method to boot up an application on the device.  If QSPI flash is connected to the chip, it will look through the QSPI flash for a valid application and then boot; if not, it will wait for the boot commands via SPI or UART.

    Rampratap Chauhan said:
    2. As Per my understanding the M4F MCU is used to process the raw data from the 6432AOP module and send it in TLV packet on UART which is understandable by visualizer/host MCU. So this MCU should also be the part of our custom board along with the Host MCU right? I am asking this because I saw in the schematic that XDS_DCA_RS_232_TX(carries processed data in TLV format) and XDS_DCA_RS_232_RX both signals are coming from the XI6432BRQAAMY chip so if we are getting the TLV data direct from the 6432AOP what is the use of M4F MCU?

    The MCU is integrated into the device so as long as you are designing with the IWRL6432AOP, you are already integrating the MCU into your design.

    Rampratap Chauhan said:
    3. What is the use of EEPROM connected on I2C?

    I believe there is XDS information stored in the EEPROM connected to the I2C.

    For any new questions, please create a new thread as these questions have deviated from the original question of the post.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 80 points

    Hi, The power driver example you mentioned is the example stored at this location - C:\ti\MMWAVE_L_SDK_05_05_03_00\examples\drivers\power\power_modes\xwrL64xx-aop\m4fss0-0_freertos\ti-arm-clang ?

    Currently I am using the Application code motion and presence detection and using sysconfig I added the  GPIO/SYNC_IN as wake up source but I want to enter the deep sleep again after receiving one frame data . I want this same process to repeat, how can I manage that?

    After changing the value in Sysconfig POWER section how to generate the corresponding code?

    After selecting the wake up source  GPIO/SYNC_IN, in GPIO Configuration there was option of multiple pins to chose but I could not find which pin is relate to either user switch S3 or any exposed pin out on the IWRL6432AOPEVM board. I won't be able to find out that wake up and sleep is working or not, Please help.

    Thank You.

  • 0 in reply to Rampratap Chauhan
    TI__Mastermind 18980 points

    Hello.

    Rampratap Chauhan said:
    The power driver example you mentioned is the example stored at this location - C:\ti\MMWAVE_L_SDK_05_05_03_00\examples\drivers\power\power_modes\xwrL64xx-aop\m4fss0-0_freertos\ti-arm-clang ?

    Yes.

    Rampratap Chauhan said:
    Currently I am using the Application code motion and presence detection and using sysconfig I added the  GPIO/SYNC_IN as wake up source but I want to enter the deep sleep again after receiving one frame data . I want this same process to repeat, how can I manage that?

    When you send the frameCfg configuration command, make sure that the last parameter is 0 so that it runs for infinite frames.  You can refer to any of the existing configurations within the SDK for reference on how to do this.

    Rampratap Chauhan said:
    After selecting the wake up source  GPIO/SYNC_IN, in GPIO Configuration there was option of multiple pins to chose but I could not find which pin is relate to either user switch S3 or any exposed pin out on the IWRL6432AOPEVM board. I won't be able to find out that wake up and sleep is working or not, Please help.

    Did you check the schematic to make sure you could map the specific pin to a pin on the EVM?  Please make sure you look for it in the schematic and let me know if you cannot find it there.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 80 points

    Hi Santosh, Yes I looked for the pins in the schematic but there is cross mark in front of the those MCU pins, and signals coming from radar chip pins, I am not able to see them directly connected to an MCU pin.

    Thank You.

  • 0 in reply to Rampratap Chauhan
    TI__Mastermind 18980 points

    Hello Ram.

    J2 should be available on the AOP schematic.  Have you tried this pin?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 80 points

    Hi Santosh, thanks for the suggestion, I have tried J2 Pin as SYNCIN_IO and it works as expected. I am pulling this pin high from my host MCU with a scheduler at every 5 min and after receiving the frame data within 2-3 seconds, I pull it back to low. 

    So using this approach the radar sensor and MCU will be in deep sleep mode for most of the time(4 min 55-57 sec precisely) for each 5 minute period right ?  If yes then it would save a lot of power.

    Thank You.

  • +1 in reply to Rampratap Chauhan
    TI__Mastermind 18980 points

    Hello Ram,

    The device will be in deep sleep once all the processing is complete on the device.  The GPIO is just the wakeup source, so until this source is active it will remain in deep sleep, and once it gets out of deep sleep it will start the next frame.

    Sincerely,

    Santosh