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

AWRL6432: How to get the wakup source

chianan chang
Intellectual 810 points
Part Number: AWRL6432

Hi

  We would like to get the Radar wakup source to check is Radar deep sleep wakeup from the sleep counter or UART RX. The result is very strange:

(1) If we only choose Enable Sleep Counter Wakeup LPDS @ .syscfg  , than the Radar sleep and wakeup with right Frame period setting ( for example 200ms)

(2) If we choose both Enable Sleep Counter Wakeup LPDS & Enable UART Wakeup LPDS, than even though we do not send any UART data to Radar,but most of the Frame the Radar send out the UART result and   sleep but wakeup immedaitely, sometimes the frame period will be the same with the setting value ( for example 200ms) . Why? 

(3) We want to know the wakup source is Sleep counter or UART wakeup , we try to use PRCMLPDSWakeupCauseGet() ( from prcm.c) to get the wakeup source and wakeup status @ power_LPDSresumehook(), but the result always zero. We do not know why, maybe the status and source had been cleared beforepower_LPDSresumehook(), so would you please let us know how to get the wakeup status and source? without it, it is hard to let Radar can be communicated when the low power is enable.

  • 0
    Intellectual 810 points

    Hi We had use bootInfoReg0 = HW_RD_REG32(CSL_APP_CTRL_U_BASE + CSL_APP_CTRL_APPSS_BOOT_INFO_REG0) to get the wakeup source, and the result wakeup source is 0x01 ( means wakeup from sleep counter).  The result is right.

    but when we enable the Enable UART Wakeup LPDS from syscfg , and try to communicate with Radar, the Radar still keep its original frame period and the wakeup source sill always 0x01 and can not get 0x02. It is very strange, excep to enable UART Wakeup LPDS from syscfg, is there any other thing we need to modify?

  • 0 in reply to chianan chang
    TI__Genius 10730 points

    Hi Chian,

    We are looking into this and will be getting back to you in the next week.

    Thanks,

    Angie

  • 0
    TI__Expert 3525 points

    Hi,

    The wakeup source can be read directly from the boot registers. Specifically, those shown in the table below. 

    Best Regards,

    Kevin 

  • 0 in reply to Kevin Ortiz
    Intellectual 810 points

    Hi Kevin

        You did not answer my question about "but when we enable the Enable UART Wakeup LPDS from syscfg , and try to communicate with Radar, the Radar still keep its original frame period and the wakeup source sill always 0x01 and can not get 0x02. It is very strange, excep to enable UART Wakeup LPDS from syscfg, is there any other thing we need to modify?"

       I try couple method to wakeup the radar from deep sleep and check the wakeup source. It is very strange:

    (1) If We only enable sleep counter to wakeup, the wakeup source always get 0x01 , means wakeup from sleep counter, the result is right and the frame period is the same that we set.

    (2) If we enable UART RX for wakeup source ( From document We do not know UART RX means UART0 RX, or UART1 RX or RS232 RX), and we only open the port for RS232  to let Radar output the TLV packet to PC and let the PAD AM iomux set to 0 meanse UART0_RX. And than it is very strange, even though we let the UART0_RX always be high, but the wakeup source sometimes 0x01 sometimes 0x02 ( if it is 0x02, the frame period will be shorter, seems be wakeup by something, but I'm sure all of the signals of UART0_RX, RS232_RX are all keep high). So I do not know why it is wakeup with radom and wakeup from what signal.   

    (3) I try to use GPIO pin wakeup, but it never work. Do not know what is the right method to setup the GPIO wakeup.