• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 107 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWRL6432: Can not work when lowPowerCfg 1

chianan chang
Intellectual 810 points
Part Number: AWRL6432

Hi

We had developed the AWRL6432 that can use lowPowerCfg 1 for IO port using UART or SPI interface. But if the IO port use I2C Target mode, the Radar can only output one frame informaion than hangup. I try to use lowPowerCfg 2 for testing and it work very well. Can anyone let me know how to solve this issue. For this project, customer need to use I2C for the only one IO port and need to support deep sleep mode.

  • 0
    TI__Expert 8092 points

    Hi,

    If it is working with lowPowerCfg 2, then it is likely an issue with I2C peripheral not getting shutdown/reinitialized correctly when entering deep sleep mode. 

    Is the customer building the application off of one of our existing demos/examples? If so, can they share where in the code they are making the I2C transactions? Additionally, can you provide some more details on what information they are trying to send? I would ask the customer to make sure they are not putting the I2C commands in a portion of the code that is not executed while in deep sleep mode.

    Additionally, we perform clock-gating for various peripherals to save power while in deep sleep. In power_xwrLx4xx.c, you can see us gating/ungating these peripherals based on whether or not we are going into or coming out of deep sleep mode. Can you ask if they can comment out the "Gate I2C clock" section as well as the "Ungate I2C clock" and see if this changes any of the behavior?

    Regards,
    Tim

  • 0 in reply to Tim Henderson
    Intellectual 810 points

    Hi Tim

                 I find the reason, the I2C transmit speed is slower than UART , so there is no enough time to let Radar enter deep sleep mode. After I reduce the data length and I2C baud rate than it can work well. Thanks.